Sunturn Presentationfor

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 oneX® Portal

Extension to CellularExtension to Cellular

VPNremote

Extensionto Cellular

Avaya one-X®Mobile

Avaya one-X®Portal

CommunicationManager

Avaya one-X®Communicator

Microsoft OCS &Lotus Sametime

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)

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 QoS is so Important

The Evolution of Telephony

“HelloCentral”

Analog KeySystem

Digital(DCP)

EarlyIP

ApplicationBased 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 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)

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 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)

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 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)

Model 3 – Converge at the Desktop

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

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

Why QoS is so Important

• What could happen if packets are simply played as they arrived—out of order?

I wish you were here, the isweather beautiful.Transmitted:

Received: I wish you werehere,The isweather beautiful.

Why QoS is so Important

• The problem with excessive packet loss for real time protocols—dropped packets.

I think, therefore I am.

I think I am.

Transmitted:

Received:

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

Thank You!

Backup Slides

Avaya Aura Architecture

3rd PartyendpointsAvaya

CM Branch

MX

Application Platform

App

o o o

AvayaCM Standalone

o o o

Application Platform

G860

3rd Party PBXs

SBC

App

ServiceProviders

SystemManager

App MMVP

CM

SessionManager

Avaya Aura Core

SIPTrunks

MediaServers

TDMTrunks

Access

Connection

Application

SIPPresence

SessionManager

SessionManager

Avaya one-X®

endpoints

Avaya Aura Session Manager

o o o

SMSM

SM

FeatureServer

FeatureServer

FeatureServer

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 recoveryApplications 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