© 2009 Avaya Inc. All rights reserved. Introduction to SIP Trunking Alan Klein Consulting Systems...

© 2009 Avaya Inc. All rights reserved.

Introduction to SIP TrunkingIntroduction to SIP TrunkingAlan KleinConsulting Systems [email protected] February 2009


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.


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


Building a SIP Trunk (Drag & Drop)

Service Provider

Avaya Communication Manager (IP-PBX)

Avaya SIP Enablement Server (SIP Proxy)

Session Border ControllerApplication Notes for Configuring Avaya Communication Manager SIP Trunking to

a Typical SIP Service Provider – Issue 1.1

http://www.avaya.com/master-usa/en-us/resource/assets/applicationnotes/

genspsiptrk-v1-1.pdf


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


CM to ITSP (Outbound call)

• If the Far-end Domain is filled out then the “Request URI” and the “To” headers will reflect the information.

• The Public-unknown numbering plan inserts the From extension.

• The Near-end Clan for the signaling group has an ip-network-region authoritative domain that will appear in the “From” header.


The Enterprise InfrastructureThe Enterprise InfrastructureAlan KleinConsulting Systems [email protected] February 2009


LAN

Avaya Communication Manager G650 Gateways

Digital/Analog

IP Phone

IP WAN

A

E

B

D

C

The Enterprise Infrastructure

Micro SitesG250

S8300 LSP or basic survivability

Small Sites G350 S8300 LSP or basic

survivability

Medium SitesG450’s

S8300 LSP

Large and/or Backup SitesG650, ESS


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


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


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

© 2009 Avaya Inc. All rights reserved. Introduction to SIP Trunking Alan Klein Consulting Systems...

Documents

Transcript of © 2009 Avaya Inc. All rights reserved. Introduction to SIP Trunking Alan Klein Consulting Systems...