Sunturn Presentation for Rocky Mountain Avaya User Group

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

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

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

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, EC 500, Browser-based Communications Portal) • Microsoft Integration – (Office Communicator)

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

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 Qo. S is so Important

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

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

Model 0 – No Convergence

Model 0 – No Convergence • Plus – Most Secure, Highest Reliability. Events and Configuration Changes in the Data Network are isolated from the Vo. IP network, Including the WAN – Lower requirements for Po. E ports. Most Data switches can be 10/1000 without Po. E while voice switches can be 10/100 with Po. E – 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)

Model 1 – Converge at the Core

Model 1 – Converge at the Core • Plus – Most Secure, Highest Reliability. Events and Configuration Changes in the Data Network are isolated from the Vo. IP network – Lower requirements for Po. E ports. Most Data switches can be 10/1000 without Po. E while voice switches can be 10/100 with Po. E – 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)

Model 2 – Converge at the Edge

Model 2 – Converge at the Edge • Plus – Equipment requirements may be less than Model 1. Edge switch port utilization is better as Vo. IP 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 Vo. IP and Data Switches • Minus – More Switch Administration Required than Model 1 – All Edge Switches are typically 10/1000 with Po. E although IP Phones only require 10/100 ports with Po. E – All Equipment must support Qo. S – 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)

Model 3 – Converge at the Desktop

Model 3 –Converge at Desktop • Plus – Less Equipment is Required for this model as Vo. IP 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 Po. E and 10/1000 to support a mix with Gig Ethernet Devices – All Equipment must support Qo. S – 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

Importance of a Sound Qo. S Design and Implementation • Prioritization of real time protocols – Regardless of available bandwidth • Low Latency – < 150 ms 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

Why Qo. S is so Important • What could happen if packets are simply played as they arrived—out of order? Transmitted: I wish you were here, the weather is beautiful. Received: The weather is here, I wish you were beautiful.

Why Qo. S is so Important • The problem with excessive packet loss for real time protocols—dropped packets. Transmitted: Received: I think, therefore I am. I think I am.

On what manufacturer’s Ethernet switches does Avaya Vo. IP operate?

Thank You!

Backup Slides

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

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