1. Sunturn Presentation for Rocky Mountain Avaya User Group May 13, 2009

5. Introductions & Agenda Team Introductions Session 1 –Enhancing Employee Productivity through Unified Communications – Brian Karch & Rob Nixon Session 2 –Four Levels of Convergence – Rusty Holland

6. Session 1 – Enhancing Employee Productivity Avaya one X® Portal Extension to Cellular VPN remote Extension to Cellular Avaya one-X® Mobile Avaya one-X® Portal Communication Manager Avaya one-X® Communicator Microsoft OCS & Lotus Sametime

7. Session 1 – Enhancing Employee Productivity Conferencing –(Audio Bridge, Web Collaboration, Video) Messaging –(Find Me ~ Follow Me ~ Notify Me, Speech Access, Outlook Client for Voice Mail and Fax) Telephony –(Touch Screen Phone, IP Phone Applications, Microsoft Outlook Access, Broadcast Feature) Mobility –(Softphone - Desktop & Cell Phone Client, EC500, Browser-based Communications Portal) Microsoft Integration –(Office Communicator)

8. How many DCP phones has Avaya introduced in the last 3 years?

9. Session 2 – Four Levels of Convergence Why are we still talking about Convergence? The Four Levels –Model 0 – No Convergence –Model 1 – Converge at the Core –Model 2 – Converge at the Edge –Model 3 – Converge at the Desktop Why QoS is so Important

10. The Evolution of Telephony “Hello Central” Analog Key System Digital (DCP) Early IP Application Based IP Telephony

11. Why are we still talking about Convergence? Move from Network-Centric ~ Organization- Centric ~ User-Centric Communications Avaya’s SIP e-IMS Architecture Expanded Integrations/Interactions - Presence Enablement to Enterprise Applications Massive Scalability Application Sequencing

12. Model 0 – No Convergence

13. Plus –Most Secure, Highest Reliability. Events and Configuration Changes in the Data Network are isolated from the VoIP network, Including the WAN –Lower requirements for PoE ports. Most Data switches can be 10/100/1000 without PoE while voice switches can be 10/100 with PoE –Gig IP Phones are not required to support Data Devices –Administration is easier with this model –Easiest model to trouble shoot voice problems Minus –Higher Edge Switch Cost, more Equipment required to support Switches dedicated to Voice and to Data –Dual Wiring runs required to each desktop (one for voice, one for data) –Higher WAN cost (requires 2 Networks)

14. Model 1 – Converge at the Core

15. Plus –Most Secure, Highest Reliability. Events and Configuration Changes in the Data Network are isolated from the VoIP network –Lower requirements for PoE ports. Most Data switches can be 10/100/1000 without PoE while voice switches can be 10/100 with PoE – Gig IP Phones are not required to support Data Devices –Administration is easier with this model –Easiest model to trouble shoot voice problems Minus –Higher Edge Switch Cost, more Equipment required to support Switches dedicated to Voice and to Data – Dual Wiring runs required to each desktop (one for voice, one for data)

16. Model 2 – Converge at the Edge

17. Plus –Equipment requirements may be less than Model 1. Edge switch port utilization is better as VoIP and Data Devices may be mixed on the same switch –Gig IP Phones are not required to support Gig Data Devices because Data Devices are directly connected to switch ports –A good model for offices not large enough to justify dedicated VoIP and Data Switches Minus –More Switch Administration Required than Model 1 –All Edge Switches are typically 10/100/1000 with PoE although IP Phones only require 10/100 ports with PoE –All Equipment must support QoS –A Switch failure or mis-configuration effects both voice and data –Trouble Shooting voice problems - more difficult –Dual Wiring runs required to each desktop (one for voice, one for data)

18. Model 3 – Converge at the Desktop

19. Model 3 –Converge at Desktop Plus –Less Equipment is Required for this model as VoIP and Data may share a switch port, maximizing port utilization –Less Wiring Required as a single wiring run to each desktop can be used for Voice and Data Minus –Higher Administration Requirement –Gig IP Phones (higher cost) are required to support Gig Data Devices connected to phones –All Edge Switch ports must be PoE and 10/100/1000 to support a mix with Gig Ethernet Devices –All Equipment must support QoS –A Switch failure or mis-configuration affects both voice and data –A IP Phone problem could affect the attached PC –Trouble Shooting voice problems - most difficult

20. Importance of a Sound QoS Design and Implementation Prioritization of real time protocols –Regardless of available bandwidth Low Latency –< 150ms one way (ITU-T Recommendation) Low Jitter –Variance between packets –Dynamic Jitter Buffers can help Low Packet Loss –< 1% to 3% - It is Subjective to the application

21. Why QoS is so Important What could happen if packets are simply played as they arrived—out of order? Iwishyouwerehere,theisweatherbeautiful.Transmitted: Received:Iwishyouwerehere,Theisweatherbeautiful.

22. Why QoS is so Important The problem with excessive packet loss for real time protocols—dropped packets. Ithink,thereforeIam. IthinkIam. Transmitted: Received:

23. On what manufacturer’s Ethernet switches does Avaya VoIP operate?

24. Thank You!

25. Backup Slides

26. Avaya Aura Architecture 3 rd Party endpoints Avaya CM Branch MX Application Platform App o o o Avaya CM Standalone o o o Application Platform G860 3 rd Party PBXs SBC App Service Providers System Manager App MM VP CM Session Manager Avaya Aura Core SIP Trunks Media Servers TDM Trunks Access Connection Application SIP Presence Session Manager Avaya one-X ® endpoints

27. Avaya Aura Session Manager o o o SM Feature Server Feature Server Feature Server SP Reliability and Scale  Massive scale, global SIP connectivity  25,000 locations, 250,000+ users  Active/active N+1 geo-redundancy  Distributed “instances”, multiple active connections, very fast recovery Applications  Avaya SIP-ready communications  Modular Messaging, Meeting Exchange, Voice Portal, Interaction Center, etc.  Agile “feature server” integration  SIP-ISC standard (3GPP), “sequencing”  Open to third-party feature innovations  DevConnect ecosystem expanding  Service Provider value-add over time Security  Secure, TLS encrypted, SIP firewall, SIP packet inspection, hardware accelerated  Session Border Controllers for boundary Multivendor Interoperability  Cisco UCM, Nortel CS1000 adaption modules, more IP-PBX testing to follow  Avaya Gxxx or AudioCodes SIP gateways for legacy PBX integration  Acme Packet SBCs and others  Further DevConnect testing starting May  SIP Trunks: AT&T, Verizon, Orange, … Evolution  Easily add SM to multivendor networks  A “CM upgrade” for existing customers  Control access/bandwidth for new apps