Delivery to VoIP QoS Tools

1. Delivery to VoIP QoS Tools

2. Business Model Business as usual - what we do today; just a new market Deliver call details to Companies that build Call Recorders Deliver call details to Companies that build VoIP QoS Tools Internal use only

3. What is VoIP QoS? QoS = Quality of Service Monitors the health of VoIP Networks • MOS scores/R factor (voice quality) • Jitter • Call set up analysis; delays • Packet Loss, corrupt packets • Network bandwidth statistics Internal use only

4. Our Product Proposal • We decode the signaling and pass up call information • Our customers interpret information and build full application with user interface and analytics Internal use only Intertel Avaya H.323 Nortel SIP Ericsson Siemens

5. Understanding the VoIP QoS Market It is really the Network Management Market (IT) • Add tools that monitor VoIP 12 billion dollar market world-wide (Frost & Sullivan) Internal use only

6. VoIP QoS Market – Type 1 • Service-level management (SLM) • Business service management (BSM) • Service Level Agreement (SLA) Comprises 37% of network monitoring sales (3.5 billion) The ability to monitor VoIP QoS relative to what the carrier promised. Carriers – track their own records to monitor the service they deliver Vonage, Verizon, Comcast, at&t etc…. Enterprise – monitor their SIP trunks making sure carriers deliver what they promised Internal use only

7. VoIP QoS Market – Type 2 End User Experience Management • Expects a 72% growth from 2007 to 2008 with total expected sales of $300,000 million (Frost and Sullivan) Monitor VoIP QoS relative to the caller experience from “cradle to grave” Ability to monitor QoS on the local network; “The Proprietary PBX” Internal use only

8. Target Market Generally speaking; • Most companies first created network monitoring tools • Packet loss • Switch health • Network collisions • Network bandwidth • Now include VoIP analysis Internal use only

9. Our Target Market Companies that develop VoIP QoS tools with product offerings for the enterprise market • Why not carrier market? Or SLA/BSM? • These are typically standard VoIP protocols such as SIP/H.323/MGCP – which they already support Our value is our ability to decode proprietary protocols Internal use only

10. Our vision is to enable VoIP QoS applications monitor proprietary telephone networks Internal use only

11. Our Value • We decode proprietary telephone signaling so they don’t have to • Get call information directly from the network; not the PBX • No CTI link required • Monitor actual calls; not artificially generated calls (more later) • No equipment costs • No specialized application development or engineers Internal use only

12. Our Current HPX Product Offering • SmartWORKS API • Consistent development across multiple PBX vendors • Changes to call state (alerting/connected); time stamp • Call Meta data • Caller/Called numbers, extension (when avail), call duration, IP addresses/ports of all endpoints (signaling/media) • Forwarding of RTP • To their services for voice quality analysis (we can add later) • Our Call recording/playback services • RTCP analysis Internal use only

13. Statistics - Today • VoIP Protocol • Packets out of order • Checksum error • Total packet count • Dropped segment • UDP checksum • Station (Phone) Statistics • Total count of inbound & outbound calls • Call duration; avg • Total calls rejected, abandoned, connected Internal use only

14. Potential Customers • NetQoS – VoIP Monitoring Tool (private company - increased revenues by 671 percent from 2003 to 2007, $30-50m sales; 2,744 hits/day) • Cisco Unified CallManager 4.2 or later • Gateways running SIP, MGCP, and H.323 • NetIQ – AppManager for VoIP (NTIQ ~ $200m sales, 3,000 hits per day) • Avaya, Cisco, Nortel, Microsoft OCS • Network Instruments (private company, saw five years of 25% growth, 07-08 saw 47% growth; also manufactures hardware taps; 1,700/day) • Cisco, Avaya, Nortel, Mitel • Gateways running SIP, MGCP, and H.323 • SolarWinds – Orion VoIP Monitoring (private company, 10 years old, over 1,000,000 customers; 9,600 hits/day) • Any PBX vendor; however limited to Cisco SLA knowledge Internal use only

15. Moving Forward • I have a list of 75+ companies • All are qualified leads – offer enterprise QoS solution Internal use only

16. Everything you need know about VoIP QoS in order to get the job done Internal use only

17. Current Technology While 45% of organizations surveyed had already implemented VoIP, only 32% felt that they could properly monitor VoIP performance (Network Instruments) Agenda: • Overview of technology available today • Understand limitations • Value Added Services Internal use only

18. Typical Business To carrier; SIP Trunk VPN - Tunnel Internal use only SIP Proprietary Signaling between PBX and phone

19. What can most tools see? (type 1) To carrier SIP Trunk VPN - Tunnel Internal use only VoIP QoS Monitoring SIP Terminal/Edge Devices

20. Penetrating the Enterprise (Type 2) • Monitor SNMP / MIBs • Use SLA enabled devices • Passive • PBX Integration • Decode VoIP Packets (SIP/H.323/MGCP) Internal use only Emerging Trend – decode proprietary

21. SNMP/MIBs • Resulting Metrics • Monitor health of network equipment (servers) • CPU • Disk space Internal use only

22. SNMP/MIBs • Resulting Metrics • Monitor health of network equipment (servers) • CPU • Disk space • Limitations • Nothing about call signaling path • No call detail (CDR) information • Each vendor enables different SNMP messages, proprietary messages • Useful for monitoring health of network equipment, but not actual call Internal use only

23. SLA Enabled Devices SLA “Calls” SLA – Service Level Agreements Network switches; generates artificial calls • Resulting Metrics • Transport delays across network - jitter • RTP Packet loss; MOS scores • Call Setup delay Actual customer calls Internal use only SLA enabled Switch PBX SLA enabled Switch SLA enabled Switch

24. SLA Enabled Devices SLA – Service Level Agreements Network switches; generates simulated calls • Limitations • Requires support of SLA enabled devices (Cisco) • Strains network bandwidth • Selective information – miss peak call analysis • Artificially generated, no data analysis of actual calls • No view of PBX (not an SLA enabled device) • No view of real protocol – different call setup procedures Internal use only

25. Unanswered Questions Is poor call quality impacting the customer experience? Are abandoned calls the direct result of network problems? Why do calls from a specific area code or agent sound choppy? Why doesn’t my agent get a dial tone? How can I replay or regenerate a specific call to resolve a complaint? Internal use only

26. Unanswered Questions Is poor call quality impacting the customer experience? Are abandoned calls the direct result of network problems? Why do calls from a specific area code sound choppy? Why doesn’t my agent get a dial tone? How can I replay or regenerate a specific call to resolve a complaint? • Customer Experience Analytics • -OR- • Measuring the ROI of the VoIP Installation Internal use only

27. Real Feature Requests “I have not been able to find anything that will monitor Avaya in real time, hopefully the VOIP Module will do this in a future release. – posted 11/07” “In 2008, our goal is to collect Avaya specific phone/VoIP data that is available via SNMP.  All IP SLA data will still be collected by the Cisco routers. “There are times where we have a customer who can’t dial a certain number, or has call quality issues to a certain area code, and it would be nice to just grab that information ….” Internal use only

28. Emerging PBX Integration • Limited view of entire network • Only receive information about “bad” calls • Limited by what PBX vendor exposes via API • Difficult installation • Troubleshooting headache • Cost • API is free • Certification is expensive, time consuming

29. Emerging Decoding Protocols • Resulting Metrics Of actual customer calls • Call set up delay; delay to hear dial-tone or connect • Call re-creation • Call playback • Voice quality; tag problems in real time • Packet priority errors (network configuration problems) • Visibility of actual VoIP endpoints (PBX, phone, and Caller ID) • Phone re-setting • PBX not sending ACKs • Monitor burst activity Internal use only

30. Analysis Many advertise proprietary PBX support: Actually they; • Monitor MIBs/SNMP of proprietary hardware which allow insight to health of server • Show call flow of calls generated by SLA tools A few actually decode proprietary protocols I have seen; Cisco, Avaya, Nortel, Mitel – (Network Instruments) But nothing else; Siemens, Alcatel, Aastra-Matra….. Internal use only

31. Product Proposal Using HPX decode proprietary call information and deliver essential data to VoIP QoS monitoring tools: Here is what we can deliver via HPX: • Call Set Up analysis; time to call setup (lag to dial tone) • Playback of audio/video (NGP) • Call detail records; so QoS tool can build historical information • Ability to re-create call scenario • Call identifiers; network call ref, extension, DNIS, CallerID, area code, agent ID, etc • Call failures and cause • Total VoIP packets TCP/IP and UDP • Re-transmitted packets Internal use only

32. Like this… Internal use only