Introduction to SIP Trunking in the Enterprise

Henry Pinera
Systems Engineer hpinera@avaya.com February 2009

2009 Avaya Inc. All rights reserved.

Why SIP? A great pedigree

2009 Avaya Inc. All rights reserved.

Why SIP Trunking?

Limitation & Challenges of Private IP (H.323/SIP) Trunking
Private IP (H.323/SIP) trunks are limited to VoIP communications between internal systems/sites Separate TDM interfaces are required for external communication (partners/suppliers/customers) Extra cost, extra hardware, extra complexity

PSTN
Local & Long Distance
Customers/ Partners/ Suppliers

IP WAN

IP Data &Telephony
LAN LAN
Internal Communications

IP Phone

IP Phone

IP Phone

IP Phone

2009 Avaya Inc. All rights reserved.

SIP Trunking
A Single Pipe to the Cloud
Single IP link for voice/data Optimize use of WAN access by consolidating voice and data services Reduce PSTN interfaces for long-distance and local access Assign local telephone numbers to any virtual location, independent of physical location Prepares for future SIP solutions

PSTN
Local & Long Distance
Customers/ Partners/ Suppliers

WAN

H.323
LAN LAN

IP Phone

IP Phone

IP Phone

IP Phone

2009 Avaya Inc. All rights reserved.

Flavors of SIP Trunking

Service Provider Service Provider Service Provider

Enterprise / Contact Center

(one or multiple locations)

Enterprise / Contact Center

Enterprise / Contact Center

Enterprise / Contact Center

Application Servers

SIP trunking can be over the LAN, WAN or dedicated circuits.

2009 Avaya Inc. All rights reserved.

Building Blocks of SIP Trunking

SBC Server / Gtwy

Service Provider
Service

Service Provider

Session Border Controller (SBC)

or direct connection

Customer Premise
Edge security device: SBC, Firewall, etc Communication Platform: Server(s), Gateway(s), SIP Proxies, etc Application Servers: messaging, video & audio conferencing, collaboration tools, IM, Presence, and more Endpoints: hardphones, softphones, mobile devices, application integration
2009 Avaya Inc. All rights reserved.

Components of SIP Trunking Solution

Customers Partners Suppliers Customers Partners Suppliers IP Office

ITSP
G860 PSTN DS3/ISDN Communication Manager

CM Branch Edition

SBC Meeting Exchange SES Modular Messaging SIP

SIP

SIP

Avaya one-X Communicator

Voice Portal

2009 Avaya Inc. All rights reserved.

SIP Trunking - Overview

SIP phone (future)

SIP Provider(s)
T1/E1/ ISDN Provider(s)
IP Office acts as a SIP gateway

IP DECT

IP phone (46xx/56xx/T3 IP)

Digital phone (24xx/54xx/T3)

Analog phone

Analog Provider(s)

No need for a SIP phone to make/receive a SIP call SIP Trunks are licensed in increments of 1, 5, 10 and 20 (up to 128 channels) Benefits Lower operational costs
Lower cost/flat rate calls with Internet Telephony SPs Offers back-up to Analog/Digital Trunks + Number Portability
2009 Avaya Inc. All rights reserved.

Future-proof your investment

Will CM Support SIP Trunks from XYZ SP?

1.

DevConnect compliance testing

For U.S. SIP SPs, no longer a requirement but still HIGHLY RECOMMENDED No change to non-U.S. Service Providers; DevConnect compliance testing required Contact: http://www.avaya.com/devconnect
http://www.avaya.com/master-usa/en-us/resource/assets/applicationnotes/genspsiptrk-v1-1.pdf

2.

3.

Professional Services engagement for enterprise customers In-region R&D

Contact: In-region Product Manager

2009 Avaya Inc. All rights reserved.

SIP SP DevConnect Members

United States
AT&T BandTel Bandwidth.com Clear Channel Satellite ConneXon Telecom (911 Enable) Cox Communications Global Crossing Nectar (AGN Network) PAETEC (McLeodUSA) Telcordia Telepacific Verizon Business XO Communications

EMEA
BT [Germany and Spain] Club Communications [UK] COLT [UK and Germany] KPN [Netherlands]

APAC
Singtel [Singapore] Telstra [Australia] TFN [Taiwan]

2009 Avaya Inc. All rights reserved.

Architecture
High Density Gateways (Avaya G860) Service Provider 3rd party systems

Voice Portal
Outsourcer Branch Agents

SIP Proxy
Business Applications

Remote Agents
Conferencing Unified Messaging

Communication Manager systems

2009 Avaya Inc. All rights reserved.

Peering Enterprise Contact Centers

Notes: 1) Will use standard US centric 10 digit dialing for now. International configurations are out side of the scope of this phase of the project.

Primary Contact Center

2) Server configurations should be done based on the IP addresses NOT DNS. 3) Call Routing will be based on DIDs. Nuance will ensure that transfers will be to the contact center the sent the call to them

COMPACT

COMPACT

Nuance Proxy Server

Virtual (shared) Server

Nuance Media Servers (100s)

Sig n

alin

Avaya DSP Resources

RTP Traffic (G711, 20ms, no encryption, RFC 2833) Note: 80kbps without L2 encapsulation

MPLS Network

Secondary Contact Center

Si gn
na Sig
COMPACT

COMPACT

ling

Pr od uc ali Tes tion ng t : : an T 1 T 3 d Be ar er

T3 n: r tio T1 are Primary Site c e u o d e st : d B r n P T (Houston, TX) a g lin na g i Call Flow S 1) Call will come in on T1s located in Communication Manager controlled Gateways at each location. 2) Calls will be routed via SIP Trunks to Primary or Secondary site (depending on availability). Only Delivery requirement is correct ANI and DNIS. 3) The calls will be answered by specific Voice Recognition Applications. 4) Once the call has been processed by the application it will be transferred back to the originating Communication Manager via the SIP REFER method.

Virtual Shared Server

Nuance Proxy Server Note: Avaya will only Interface with Public IP Address Interfaces of Nuance. All needed NAT is to be performed on the part Nuance presumably by some SBC.

Nuance Media Servers (100s)

Secondary Site (Sunnyvale, CA)

2009 Avaya Inc. All rights reserved.

 2007 2009 Avaya Inc. All rights reserved.

Avaya Proprietary & Confidential. Under NDA

14