+ All Categories
Home > Documents > © 2009 Avaya Inc. All rights reserved. Introduction to SIP Trunking in the Enterprise Henry Pinera...

© 2009 Avaya Inc. All rights reserved. Introduction to SIP Trunking in the Enterprise Henry Pinera...

Date post: 26-Mar-2015
Category:
Upload: austin-mcguire
View: 215 times
Download: 1 times
Share this document with a friend
Popular Tags:
13
2009 Avaya Inc. All rights reserved. Introduction to SIP “Trunking” in the Enterprise Henry Pinera Systems Engineer [email protected] February 2009
Transcript
Page 1: © 2009 Avaya Inc. All rights reserved. Introduction to SIP Trunking in the Enterprise Henry Pinera Systems Engineer hpinera@avaya.com February 2009.

© 2009 Avaya Inc. All rights reserved.

Introduction to SIP “Trunking” in the EnterpriseIntroduction to SIP “Trunking” in the EnterpriseHenry PineraSystems [email protected] February 2009

Page 2: © 2009 Avaya Inc. All rights reserved. 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

Page 3: © 2009 Avaya Inc. All rights reserved. Introduction to SIP Trunking in the Enterprise Henry Pinera Systems Engineer hpinera@avaya.com February 2009.

© 2009 Avaya Inc. All rights reserved.

Limitation & Challenges of Private IP (H.323/SIP) Trunking

IP WANIP WAN

PSTNLocal &

Long Distance

PSTNLocal &

Long Distance

IP Data &Telephony

• 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

Customers/ Partners/ Suppliers

LAN LAN

TDM in

terfa

ces TDM

interfaces

Why SIP Trunking?Why SIP Trunking?

IP Phone IP Phone IP Phone IP Phone

Exter

nal C

omm

unicat

ions

External Comm

unications

Internal Communications

Page 4: © 2009 Avaya Inc. All rights reserved. Introduction to SIP Trunking in the Enterprise Henry Pinera Systems Engineer hpinera@avaya.com February 2009.

© 2009 Avaya Inc. All rights reserved.

SIP TrunkingA Single Pipe to the Cloud

WANWAN

PSTNLocal &

Long Distance

PSTNLocal &

Long Distance

H.323

SIPSIP

Customers/ Partners/ Suppliers

LAN LAN

IP Phone IP Phone IP Phone IP Phone

• 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

Page 5: © 2009 Avaya Inc. All rights reserved. Introduction to SIP Trunking in the Enterprise Henry Pinera Systems Engineer hpinera@avaya.com February 2009.

© 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.

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

Page 6: © 2009 Avaya Inc. All rights reserved. Introduction to SIP Trunking in the Enterprise Henry Pinera Systems Engineer hpinera@avaya.com February 2009.

© 2009 Avaya Inc. All rights reserved.

Building Blocks of SIP Trunking

Service Provider

– Service

– Session Border Controller (SBC)

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

Service Provider

SBCServer / Gtwy

… or direct connection

Page 7: © 2009 Avaya Inc. All rights reserved. Introduction to SIP Trunking in the Enterprise Henry Pinera Systems Engineer hpinera@avaya.com February 2009.

© 2009 Avaya Inc. All rights reserved.

Components of SIP Trunking Solution

SIP

Modular Messaging

Voice Portal

CM Branch EditionCommunication Manager

SESMeeting Exchange

SBC

DS3/ISDN

G860

IP Office

CustomersPartnersSuppliers

Avaya one-X©

Communicator

ITSPPSTN

SIP

SIP

CustomersPartnersSuppliers

Page 8: © 2009 Avaya Inc. All rights reserved. Introduction to SIP Trunking in the Enterprise Henry Pinera Systems Engineer hpinera@avaya.com February 2009.

© 2009 Avaya Inc. All rights reserved.

SIP Trunking - Overview

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)

SIP Provider(s)

T1/E1/ISDN

Provider(s)

Analog Provider(s)

SIP phone (future)

Digital phone (24xx/54xx/T3)

Analog phone

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

IP DECT

Benefits – Lower operational costs Lower cost/flat rate calls with Internet Telephony SPs

Offers back-up to Analog/Digital Trunks + Number Portability

Future-proof your investment

IP Office acts as a SIP gateway

Page 9: © 2009 Avaya Inc. All rights reserved. Introduction to SIP Trunking in the Enterprise Henry Pinera Systems Engineer hpinera@avaya.com February 2009.

© 2009 Avaya Inc. All rights reserved.

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

2. Professional Services engagement for enterprise customers

3. In-region R&D Contact: In-region Product Manager

http://www.avaya.com/master-usa/en-us/resource/assets/applicationnotes/genspsiptrk-v1-1.pdf

Page 10: © 2009 Avaya Inc. All rights reserved. Introduction to SIP Trunking in the Enterprise Henry Pinera Systems Engineer hpinera@avaya.com February 2009.

© 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]

Page 11: © 2009 Avaya Inc. All rights reserved. Introduction to SIP Trunking in the Enterprise Henry Pinera Systems Engineer hpinera@avaya.com February 2009.

© 2009 Avaya Inc. All rights reserved.

Service Provider

SIP Proxy

Architecture

3rd partysystems

High Density Gateways (Avaya G860)

VoicePortal

Outsourcer

Communication Manager systems

BranchAgents

Remote Agents

Business Applications

Conferencing Unified Messaging

Page 12: © 2009 Avaya Inc. All rights reserved. Introduction to SIP Trunking in the Enterprise Henry Pinera Systems Engineer hpinera@avaya.com February 2009.

© 2009 Avaya Inc. All rights reserved.

Peering Enterprise Contact Centers

COMPACT

COMPACT

COMPACT

COMPACT

Virtual (shared) Server

Virtual Shared Server

Primary Contact Center

Secondary Contact Center

MPLS Network

Nuance Proxy ServerNuance Media Servers

(100s)

Primary Site (Houston, TX)

Nuance Proxy ServerNuance Media Servers

(100s)

Secondary Site (Sunnyvale, CA)

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.

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

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

Avaya DSP Resources

Signaling

Signaling

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.

Call Flow1) 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.

Production : T

3

Test : T

1

Signaling and Bearer

Production : T3

Test : T1

Signaling and Bearer

Page 13: © 2009 Avaya Inc. All rights reserved. Introduction to SIP Trunking in the Enterprise Henry Pinera Systems Engineer hpinera@avaya.com February 2009.

© 2009 Avaya Inc. All rights reserved. 14© 2007 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA


Recommended