Vatanasov SIP Trunking

SIP Trunking for IP
PSTN Access
Vladislav Atanasov
Presentation_ID
2008 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
2
Presentation_ID
Cisco Confidential
3
Presentation_ID
Cisco Confidential
SIP Trunking for IP

PSTN Access
Vladislav Atanasov
Channel SE
vatanasov@cisco.com
Cisco Public
Session Objectives
At the end of this session, you should:
Understand the reference architecture for enterprise SIP
trunk for PSTN interconnect
Understand the design concepts and trade-offs for different
PSTN SIP trunk deployment scenarios
Be aware of what is available for SIP trunking on Cisco
products both from Enterprise and from SP perspective
Be informed about what resources are available
SIP Trunking for IP

PSTN Access
Cisco Public
Agenda
Solution Overview
What is a SIP Trunk?
Industry Trends
SIP Trunk Considerations
Designing and Configuring a Network for SIP

Trunking
SIP Trunk Deployment Architectures
Cisco Unified Border Element (CUBE) Enterprise Overview
Cisco Unified Border Element (CUBE) SP Overview
Q&A
SIP Trunking for IP

PSTN Access
Cisco Public
Solution Overview
SIP Trunking for IP

PSTN Access
Cisco Public
SIP Trunks Extend the Benefits of Converged

Unified Communications into the WAN
Enterprise UCM Deployment
A
voice
SBC
Class 4/5
Switch
TDM-based PSTN
Branch Office /
Commercial SMB
UCME Deployment
voice
data
data
voice
Telecommuter/SOHO
Deployment
Converged SP
Network
data
V
Residential Administrative Domain
SIP Trunking for IP

PSTN Access
Cisco Public
Migration to End-to-End VoIP

Enabling Business-to-Business Interconnect
Enterprise
DomainA1
Enterprise
Domain 2A
IP
IP
Rich
Media
Changing Landscapes
VoIP Islands to VoIP
Interconnects
Narrowband voice
to Rich-media
Interconnect
Unified communications SIP

Trunks to destinations
beyond the Enterprise
Enterprise
DomainA1
IP
SIP Trunking for IP

PSTN Access
Rich
Media
Extend rich-media
collaboration to vendors,
partners and customers
CUBE provides b2b
interconnectivity for secure
rich-media services
SP VoIP
CUBE
SBC
SBC
Rich
Media
Cisco Public
CUBE
Enterprise
Domain 2A
IP
What is a SIP Trunk?

A sampling of Views/Definitions
Single IP based interconnect for voice & data using SIP
SIP trunking is the IP equivalent of the digital/analog TDM connection that has
traditionally connected a customers PBX and the PSTN
The logical session or channel established between a carrier and customer
(Porting PSTN Phone number to IP Address)
A SIP Trunk service can be either
Managed SP provides CPE equipment to monitor & guarantee SLAs in addition to
basic voice services
unManaged Similar to an analog phone line provides basic voice services
Any SIP-based connection between two applications

Intra-enterprise: Between applications, e.g. MPlace to CUCM, or between different
zones within a company (e.g. Europe and US)
Enterprise to SP: PSTN Access
B2B Inter-Enterprise: Between companies (e.g. Disney and Apple)
SIP Trunking for IP

PSTN Access
Cisco Public
10
SIP Trunks for PSTN Access

Why?
SIP Trunks can be cheaper (sometimes)
SIP Trunks can be more versatile (i.e. deployed over different
physical layer links)
SIP Trunks can offer equipment consolidation
SIP Trunks can be used for many different purposes
Between applications (i.e. conference bridges to IP PBX,
such as MeetingPlace to Cisco Unified Communications Manager)
Between different IP Communication zones within a
company (i.e. Europe and USA) or between companies
(i.e. Disney and Apple)
For PSTN access (centralized or distributed)
NB: This session will focus exclusively on PSTN Access
SIP Trunking for IP

PSTN Access
Cisco Public
11

Why?
Enterprises are motivated by:
Cost savings (but this may not be a reality)
Future new rich-media services that cannot be done on TDM

Equipment consolidation
Peer-, SP, and vendor flexibility; industry trends
SPs are motivated by:

Dwindling, and the expectation of dwindling, TDM revenues
Offer new services to remain profitable
Incumbents need to keep smaller competitors (without TDM services) out of
their customer accounts
To enlarge their geographic and global footprint
Incumbents: Address new markets instead of cannibalizing their TDM base

Greenfields: Address markets outside of their geographic area
SIP Trunking for IP

PSTN Access
Cisco Public
12

Perception vs. Reality
Perception
Reality
SIP Trunks can be

deployed over any
media
SIP Trunks should only be deployed over media that can provided a
guaranteed QoS that is acceptable (i.e. it would not be recommended
to deploy them across Satellite links if Voice quality is important)
SIP Trunks are always

cheaper than PSTN
trunks for PSTN Access
Large Enterprise have such low rates for traditional TDM based
telephony, rates over SIP Trunks may not save much, if anything, in
per minute charges for Local or Long Distance voice calls
SIP trunk are unregulated services and what SP charge vary widely
(unlike TDM offerings)
If cost benefits do accrue for a customer, it is likely operational or
equipment costs, not service costs
SIP Trunks provide the

exact same experience
for the end users
SIP Trunks can provide the same experience in many cases, but some
cases (i.e. Baudot connections for Deaf users or V.92 speed modem
connections) experience is different; fax can be problematic
SIP Trunks are easy to

deploy and just work
SIP is easy to deploy, but interconnection between different vendors

implementations of SIP and different Service Providers offering is not
yet ironed out
Current SP offerings are not mature and every providers offering has
to be carefully evaluated and tested
Number portability can be a significant enabler or drawback
SIP Trunks should

always
be used
SIP Trunking for IP
PSTN Access
Evaluate carefully. In some cases TDM trunks make a better choice. Or

perhaps a better choice for certain traffic types all call patterns.
Cisco Public
13
SIP Trunks
Good Reasons for Implementing Them
SIP Trunks offer a roadmap to Enhanced Services
WideBand Codecs
Calls with SUBJECT lines
Exchange of Calendaring information during a call
Multimodal communications: voice, video, chat, file sharing, over the same
communications pipe
SIP Trunks offer the ability to have a voice call over

disparate physical links
SIP Trunk can be implemented over a wide variety of IP communications
trunks (i.e. Metro Ethernet, WiFi, GSM Cellular)
SIP Trunks offer the ability to have improved redundancy

for communications
IP links can be built with redundancy of communications methods and fast failover
that results in quicker time to repair in case of failure
Lower Costs by consolidating equipment and tariff flexibility
SIP Trunking for IP

PSTN Access
Cisco Public
14
The Line Side Has Flipped to IP

and the Trunks Arent Far Behind
Share of PBX Lines
Shipped
100
2008
IP
TDM
TDM
IP
80
50%
60
40
20
0
Source: Infonetics, 2007
2001 2002 2003 2004 2005 2006 2007 2008 2009

Source: Synergy
How many years

before 50% of UC
Trunks are over IP
?
North American SIP Trunk Forecast
54% CAGR
Two years into 5, 10

year transition ?
SIP Trunking for IP
PSTN Access
Cisco Public
* Frost and Sullivan, July,

2008
Source: Frost&Sullivan
2008
15
Crossing the Chasm SIP Trunks
The SIP trunking market is in the crossing the chasm state:

Pragmatists are participating (It will never be cost effective for us,
vendors dont have right products, This is too complex, Not enough
value) until chasm, they dont show up
This same transition occurred with VoIP 10 years ago and consumer
dialup 9 years ago
Chasm of SIP Trunking as typical service will be crossed by 2010

SIP Trunking for IP
PSTN Access
Cisco Public
16
SIP Trunk Considerations

Growth
Can be cheaper
Physical access more
versatile
Capacity changes more
dynamic
Equipment consolidation
Operational consolidation
Improved redundancy
New rich-media services
Vendor/SP advocates
Industry hype/pressure
Impeding
Immature PSTN-equivalent services
Emergency / 911
Fax/Modem
MLPP
MCID
Fault monitoring/isolation
Number portability
Poorly understood legal and

geographical implications
Inconsistent service delivery
Call-ID, recording
Unregulated service
Requires in-depth evaluation

Costs vary significantly based
on geography and SP
SIP Trunking for IP
PSTN Access
Cisco Public
17
Designing and
Configuring a
Network for SIP
Trunking
SIP Trunking for IP

PSTN Access
Cisco Public
18
Reference SIP Trunking Architecture

Functions
Products
Services
(Presence,
VM etc)
SP
CUBE, IAD,
demarcation
ISR
IP PBX or
TDM PBX
CUCM,
CUCME,
UC500, Non
Cisco
Voicemail
Unity, CUE
Media GW
AS5xxxXM,
MGX
Softswitch
PGW2200,
BTS, Non
Cisco
Signaling
ITP
PSTN
Bearer
Media
GW
SBC
SIP Trunk
CUBE
CUBE
NAT
ALG
NAT
ALG
CUBE
NAT
ALG
SIP Trunking for IP

PSTN Access
CUCM
CUCME
SBCS
Cisco Public
IP PBX TDM PBX
SP Network | Customer Premise
CUBE (SP)
SIP Proxy /
Softswitch
SP-Managed |
SBC
NMS &
OSS
20
Centralized and Distributed SIP Trunk

Models
Centralized
SP VoIP
PSTN
Distributed
SP VoIP
PSTN
CUBE
Hybrid
SP VoIP
CUBE
CUBE
CUBE
CUBE
PSTN
A
A
CUBE
CUBE
Site-SP RTP
Site-to-Site RTP
MPLS
SIP Trunking for IP

PSTN Access
MPLS
CUBE
MPLS
CUBE
Cisco Public
21
CUBE ASR
CUBE + CUSP
CUBE ISR
Large-Scale SIP Trunks

SP SIP
CUCM SIP Trunk
SP SIP Trunk
CUBE
CUBE
CUBE
CUBE
SBC
CUC
A
M
CUBE Cluster
SP SIP
SP
SIP
Trunk
CUCM
SIP
Trunk
SBC
CUBE
CUBE
CUBE
CUBE
CUC
A
M
CUBE Cluster
SP SIP
SP SIP Trunk
CUCM SIP Trunk
CUC
A
M
SBC
CUBE (Ent)
SIP Trunking for IP
PSTN Access
Cisco Public
22
CUBE Features
Cisco Unified Border Element provides

the necessary services for
interconnecting Unified
Communications networks securely,
flexibly and reliably
Session Mgmt
Demarcation
Real-time session Mgmt

Call Admissions Control
Ensuring QoS
PSTN GW Fallback
Statistics and Billing
Redundancy/Scalability
Fault isolation
Topology Hiding
Network Borders
L7 Protocol Demarc
Statistics and Billing
Interworking
Yours
H.323 and SIP

SIP Normalization
DTMF Interworking
Transcoding
Codec Filtering
Fax/Modem Support
SIP Trunking for IP

PSTN Access
Mine
Cisco Public
Security
Encryption
FW Integration
Authentication
Registration
Packet Inspection
Toll fraud
23
CUBE More than an SBC

The Integrated Approach
TDM Gateway
Voice and Video
TDM Interconnect
PSTN Backup
SBC Features
Address Hiding
H.323 and SIP
interworking
DTMF interworking
SIP security
Transcoding
Routing, FW,
IPS, QoS
Note: An SBC Appliance model

would have only these features
CUBE
Unified CM
Conferencing and
Transcoding
WAN Interfaces
RSVP
Agent
SIP Trunking for IP
PSTN Access
SRST
VXML
GK
Cisco Public
28
Cisco Unified Border Element (Enterprise

Edition) Portfolio
ASR 1000 Series
CPS
50+
AS5000XM
8-12
3800 ISR
2800 ISR
<5
<250
SIP Trunking for IP
PSTN Access
500-800
Session Capacity
Cisco Public
5000+
29
SIP Trunk Best Practises

Market is still maturing and there are many interop issues
Plan and execute thorough testing before production
Most issues can be resolved with targeted configuration changes
Evaluate different providers offerings vary considerably

CUCM interconnect recommendation
CUCM 4.x and 5.x: H.323
CUCM 6.x and 7.x: SIP
CUBE should be used as the onsite Border Element to

Normalize traffic
Interconnect/share SIP trunk to different enterprise IP-PBXs
Provide SP UNI
Security for CUCM and enterprise apps using the SIP trunk
QoS and troubleshooting demarc
Get a G.711 SIP trunk

Use the SRNDs and Configuration App Notes
SIP Trunking for IP
PSTN Access
Cisco Public
30
Common Issues
SIP Delayed Offer or Early Offer
CUCM prefers DO; SP SIP trunks mostly require EO; Use CUBE to interwork
MTP Requirements
Many nuances and variances based on CUCM releases and call flows
Fax interop especially on G.729 SIP trunks

Dial peer attributes
Use separate inbound & outbound dial-peers to define attributes per call leg
incorrect matching may result in calls failing or one way audio
SIP ports
CUBE to send SIP requests to a specific destination port, use dial-peer voice xx
voip > session target ipv4:x.x.x.x:5065
CUBE to send SIP requests with fixed source port, use sip-ua > connection-reuse
Firewall traversal and FW ALGs

Some FWs are better than others
SIP Trunking for IP

PSTN Access
Cisco Public
31
Common Issues
DNS
Using DNS names in SIP header fields instead of IP addresses
SIP Normalization
To comply with SP UNI, e.g. add user=phone in INVITEs
H.323 DTMF w/o Duration

Use voice service voip > h323 > h245-signal-update for H.245 signal (no
duration) <-> RFC2833 (with duration) interop on CUBE
RFC2833 DTMF Payload Type interop

Change RTP payload type on CUBE for RFC2833 packets from the default of 101 to
another value (96) in range 96 127
E.g. rtp payload-type cisco-codec-fax-ind 98, rtp payload-type nte 96
Failover
Tune PDD with sip-ua > retry invite/register x, timers connect x
Cause codes
Preserve cause code across both legs on CUBE to aid in troubleshooting and call
rerouting, use sip-ua > reason-header override
SIP Trunking for IP
PSTN Access
Cisco Public
32
Key Takeaways
SIP trunk trend is maturing and gathering momentum
2010 will be the year of implementation
SIP Trunks for PSTN Access are becoming more widely available and
should be considered as part of a Unified Communications design
SIP trunking should be carefully evaluated for benefits and network
design considerations
The major benefit of SIP Trunks in the future is the access to newer
services
Adoption of SIP Trunks should be considered as a TRANSITION and
not a REPLACEMENT scenario for TDM Trunks. A successful
deployment will allow customers to migrate easily from TDM to IP
Trunks, gaining new features.
SIP Trunking for IP

PSTN Access
Cisco Public
33
Key Takeaways
CUBE, as an enterprise SBC, offers a smooth and easy customer migration
strategy from TDM gateways to SIP trunking for PSTN access
CUBE also offers many tools for resolving interop issues
CUBE is used in many enterprise interconnect deployments, not just SIP

trunking
H.323 and SIP IP-PBX and application interconnect
TelePresensenc interconnect
Interdepartmental interconnect
Mergers/Acquisitions network integration
The Cisco Unified Border Element is not a standalone deviceit runs on

integrated network routers that may perform other functions such as routing,
TDM PSTN interconnect, QoS etc.
SIP Trunking for IP

PSTN Access
Cisco Public
34
Session Border
Controller
Cisco Public
35
Session Border Controllers

Service Providers require devices to connect islands of IP for signalling
and all kinds of media voice/video/presence this device is
generically known as an SBC
Pure TDM and to some extent TDM/IP interconnects are in decline
SBC can be seen as the logical progression of a TDM g/w device used
to enhance and ultimately replace TDM interconnects.
An SBC can be seen in some ways as a specialist firewall for media
and signalling (SIP and H323), ie a media specific application layer
gateway. (sometimes MGCP is included)
It contains many more functions than TDM gateway functionality and
can exist in both SP networks and Enterprise networks as it contains a
large toolkit of functions that may be required in both.
True SBCs are not SIP proxies but may be configured to be behave
with similar properties generally.
they employ techniques where calls passing across the SBC are seen
as completely independent call legs, this functionality is known as
Back to Back User Agent in SIP (B2BUA)
SBCs can be considered part of SP NGN infrastructure and appear in
various forms in both IMS and TISPAN architectures.
SIP Trunking for IP
PSTN Access
Cisco Public
36
Defining SBC
SBC Enables Direct IP to IP Interconnect Between
Multiple Administrative Domains for Session-Based
Services Providing: Protocol Interworking, Security,
Admission Control and Management
Signaling
Interworking
CAC and BW
Management
NAT/NAPT and
FW Traversal
Security
Signaling/Media
Monitoring, QoS
and Statistics
Call Routing
= SBC
SBC
SBC is a tool kit of functions

Depending on the application and deployment scenario, a different set
of functions can be turned on/off
SIP Trunking for IP

PSTN Access
Cisco Public
37
Where can I find this functionality?

SBC Functionality can be seen in following classes of
devices:
Standalone SBC Appliance
Integrated into Media Gateways
Integrated into Security Devices
Integrated into Routing Devices
Cisco has many of the basic functions in IOS but only with
the blade technology do we really have the correct
hardware components to create a market comparable SBC
Most deployed SBCs today are standalone appliances
Cisco are attempting with a small group of others to break
this paradigm and need to upsell the integration approach
especially when the customer has an existing usable
platform.
SIP Trunking for IP
PSTN Access
Cisco Public
38
Where Networks Interconnect?

SBC for Inter-Provider Networking (NNI)
Class 5
SS7 TDM Interconnect SP2 IP/MPLS

Network
PSTN
Peering Router + SBC
SP1
IP/MPLS Network
SP-SP Peering:
SBC eliminates
back-to-back media gateways
Improves media quality
AAA
Enables services not possible

over TDM interconnect
SP2
IP/MPLS
Network
Can use the same peering router

for voice, video and data
SBC provides topology hiding,
protocol interworking, admission
control, security, billing, etc.
SIP Trunking for IP

PSTN Access
Cisco Public
39
Where Networks Interconnect?

SBC for SP-Access Peering (UNI)
Class 5
SP2 IP/MPLS
Network
PSTN
SP1
IP/MPLS Network
SP-EP/Residential
Peering:
SBC
SBC enables seamless

end to end VoIP
SBC
SBC eliminates TDM

interconnect from
Enterprise
A
Managed
Enterprise
SIP Trunking for IP
PSTN Access
Residential
Broadband
Unmanaged
Enterprise
Cisco Public
SBC provides protocol

IW, NAT/FW traversal,
admission control,
security, VPN
interconnect, billing
40
Cisco Session Border Controller Portfolio

CUBE (Ent)
CUBE (SP)
CUBE Enterprise play included as IOS

Feature set.
XR12K
7600
CUBE(Ent) Supports
SIP/H.323
CUCM interworking
Demarcation
Security
On-board Transcoding
IOS Feature Set
ASR 1000
AS5000XM
CUBE(SP) Supports
7301
3800 ISR
7200VXR
7201
3700
and
Media & Protocol interworking

Unified and Distributed Deployments
SBC
functionality is
IMS support(C-BGF, I-BGF, P-CSCF)
CLI
SBC
similarSPinFocus
all these
platforms
2800 ISR
2600XM
2691
SIP/H.323
SBC application
Security based upon
CAC & Policies

portable
code.
Enterprise Focus SBC
SIP Trunking for IP

PSTN Access
Scale
Cisco Public
CUBE SP play same codebase all

platforms
Supported in 7600 12k and CRS by
41
In chassis Service Blade
Ciscos SBC Eliminates Need for Separate

Appliance
Appliance Based SBC Solution
SP B
MPLS
Enabled
PE
Ciscos Integrated SBC Solution
SP B
Service
Provider
A
SP C
MPLS
Enabled
PE with
SBC
SBC
Service
Provider
A
SP C
SBC
Appliance
Traffic Flow
Traffic Flow
Seamless integration
Eliminate overlay networks
Array of QoS and security features on ingress/egress interfaces
Integration with other L2/L3 services ( eg: MPLS PE + SBC, FW + SBC )
SIP Trunking for IP

PSTN Access
Cisco Public
42
Physical Deployment Modes for SBC

Cisco SBC consists of two logical
components
Services Card
Signalling Border Element (SBE)

Deals with all session signalling
functions and admission control
Signaling Border
Element (SBE)
Data Border Element (DBE)

Deals with all media plane functions
and policing
sig
sig
media
SBE
&
DBE
sig
External
SBE
Policy
HA
AAA
CDR
VPN Control
sig
Session Control Interface
DBE
media
NAPT
QoS
RTP
Policy
HA
Data Border Element

(DBE)
ACE or MSB or ASR
SIP Trunking for IP

PSTN Access
SIP
h248
media
media
SBC Host platform
H.323
PGW 9.8 act as SBE controlling external DBEs

Cisco Public
43
CUBE(SP) Deployment Models:

Unified v/s Distributed
Distributed Model
Unified Model
SBE
(SBE+DBE)
Domain A
Std H.248 Interface
Domain B
Domain A
Domain B
DBE
All required SBC functions integrated
Centralized signaling & control logic.
No dependency on other applications
Scalable Design. Enables a pay-as-yougrow business model.
SIP Trunking for IP

PSTN Access
Cisco Public
44
ASR 1000 CUBE(SP) Implementation

Fully Integrated
SBC
SBC with BRAS, Multicast, IPSec, etc., all

performed on the ESP, no service blades
required.
ASR1000
RPact
IOS
SIP
H.248 Packet
SIP
ASR 1000 SBC Implementation

External SBE controls ASR 1000 using
H.248 to setup / teardown media paths and
push per-session policies.
DBE/SBE Control function running on RP
IOS is responsible for setup / teardown of
media paths using H.248 control/Internalcontrol-communication.
DBE Media function running on QFP
handles media traffic on the ESP, enforces
per-session policy.
(RACS)
DBE
SBE
Control
IOS-SR Middleware
Chassis
Manager
Forwarding
Manager
Kernel
Consistent w/ Other Cisco SBCs

Same common code as 7600/GSR SBC for
consistent features and 3rd party interop.
ESPact
SIP
Scalability
Up to 64K call up to 350CPS (RP2)
Up to 10-16K calls up to ~75 CPS (RP1)
SPA
SPA
SPA
SPA
Driver
Driver
Driver
Driver
Chassis
Manager
Kernel
SIP Trunking for IP
PSTN Access
Cisco Public
Internal Control
Communication
DBE
Media
QFP
Forwarding
Manager
Chassis
Manager
Kernel
45
ASR 1000 CUBE(SP) Implementation

Fully Integrated
SBC with BRAS, Multicast, IPSec, etc., all
performed on the ESP, no service blades
required.
ASR 1000 SBC Implementation

External SBE controls ASR 1000 using
H.248 to setup / teardown media paths and
push per-session policies.
DBE/SBE Control function running on RP
IOS is responsible for setup / teardown of
media paths using H.248 control/Internalcontrol-communication.
DBE Media function running on QFP
handles media traffic on the ESP, enforces
per-session policy.
ASR1000
RPact
IOS
SBE
DBE
SBE
Control
Control
IOS-SR Middleware
Chassis
Manager
Forwarding
Manager
Kernel
Consistent w/ Other Cisco SBCs

Same common code as 7600/GSR SBC for
consistent features and 3rd party interop.
Up to 64K call up to 350CPS (RP2)
Up to 10-16K calls up to ~75 CPS (RP1)
Only Configuration changes required to make it
Unified SBC from Distributed SBC
DBE Control function becomes SBE functions and
able to execute SIP/H.323 signaling, DBE Media
function
stillforruns
similarly on QFP
SIP Trunking
IP
PSTN Access
ESPact
SIP
Scalability
SPA
SPA
SPA
SPA
Driver
Driver
Driver
Driver
Chassis
Manager
Kernel
Cisco Public
Internal Control
Communication
DBE
Media
QFP
Forwarding
Manager
Chassis
Manager
Kernel
46
Key SBC Features
Cisco Public
47
Topology Hiding
Peer network sees
SBC ext. interface as
Destination for all traffic
SIP
SBC can provide the capability

to obscure the details of
service platforms and
elements from external entities
Hide Proxy/Call Server
physical addresses
Allow load sharing and
facilitate platform migration
replacement
Restrict communication to
authorised/expected peers to
local addresses only
SIP
Apps
Peer Network
SIP
Apps
SIP
SBC acts as B2BUA
Re-originates signalling traffic
to real proxy on internal I/F
SIP
SBC
NGN Network
& Service Provider
SBC
SBC only
allows
signalling
from remote
peerand media
pinholes
opened
dynamically
SIP
Device sees SBC

Local address as Proxy
Cisco SBC Support

Public
10.1.1.1
10.1.1.2
10.1.1.3
Private
192.168.1.1
192.168.1.2
192.168.1.3
Proxy
Cisco SBC is a B2BUA and fully abstracts external peers from internal network characteristics
SIP Trunking for IP
PSTN Access
Cisco Public
48
Protocol Normalisation
There are increasing numbers of
SIP devices each with subtle
differences in how they use the
protocol. SBCs can be used to
Normalise many different
flavours of SIP into a single
homogenous version that can be
presented to internal servers
SIP
Apps
SIP
Peer Network
SIP
Apps
SIP
SBC homogenises SIP
SIP
SBC
SBC
homogenises
SIP
NGN Network
& Service Provider
SBC
SIP
SIP
SIP
B2BUA operation ensures this to a

great extent
Can be enhanced by Method and
Header filters
Further enhanced by parameter
rewriting policies/scripting
SIP Trunking for IP

PSTN Access
Cisco Public
49
Call Admission Control & Policy

Most SBCs have to provide CAC functionality
NNI configurations
Typically bandwidth based CAC ensuring that peer connections
are not oversubscribed simple algorithms for CBR typically
burst bandwidth for NNI.
Can also be used to sub-zone core networks if core network
bandwidth iis an issue (not typically in Europe)
UNI configurations
User facing CAC policies may be provided to help with DoS
protection or to enforce SLAs
Internal facing CAC policies may be used to prevent Registration
storms or overload of proxies due to mass call events.
SIP Trunking for IP

PSTN Access
Cisco Public
50
Overload, DoS & DDoS Protection

SBCs typically contain features to
mitigate DoS and in some cases
DDoS attacks
Robust protocol implementations
with normalisation capabilities
Message rate limiting per source
Call rate limits per source
Attack identification (e.g. corrupt
messages, failure to authenticate,
prolonged traffic surges,
unexpected traffic,,,,)
Source isolation and collaboration
with higher order DoS systems
(e.g. Cisco guard)
SIP Trunking for IP

PSTN Access
Non TISPAN/IMS
Application Provider
TDM Network
SIP
Apps
SBC
C7
ISUP
NGN Network
& Service Provider
X
MSAN
SBC
Peer TISPAN/IMS
Application Provider
SBC
X X
POTS & ISDN

Connections
DSLAM
xDSL
Connections
Cisco Public
Shared
ETTx etc.
51
Hosted NAT traversal solving the NAT

problem with SBCs
SBC supports all forms of NAT natively
Full cone, port restricted cone, symmetric
This is because it is always in the path for L3 L7
Its able to fixup embedded addresses as they pass via the
SBC , recall an SBC is a B2BUA
Generally SBCs should have some ability to inspect SIP
and detect NATs dynamically based on parameters in the
message vs L3 addresses
SBCs also employ methods to keep the NAT signalling

pinhole open in the CPE
SIP Trunking for IP
PSTN Access
Cisco Public
52
The UNI NAT problem..

Customer side CPEs typically employ L3 NAT techniques
NATs work at Layer3 and generally create dynamic bindings
NATs modify the source IP Address

NATs typically dont modify L4 / L5 / L6 / L7 addresses
Many applications (inc SIP -media addresses) embed IP Address at L4-L7
NAT breaks the end-to-end model of IP for routability, encryption, etc..
Embedded L4-L7 addresses become non-routable, so applications break

Bindings expire so a mechanism is required to interface
keep this
signalling pinhole alive
address
L3 source address:192.168.0.100
81.1.1.1
L3 source address:81.1.1.1
Peer
Embedded application addresses:

192.168.0.100
Embedded addresses application:

192.168.0.100
SIP Trunking for IP
PSTN Access
Public Network
Private Network
Cisco Public
53
Media & Protocol Interworking

In some cases SBCs can be deployed to provide
protocol interworking and deal with interoperability
issues such as
SIP & H.323 interworking
In band to out of band DTMF transport (e.g. RFC2833 to
SIP Info)
Transcoding services typically requires on or off board
DSPs
Normalising protocol implementations on external
sources into a single homogenous form for internal servers
and proxies (e.g. filtering SIP methods and headers etc).
SIP Trunking for IP

PSTN Access
Cisco Public
54
QoS Demarcation
Unless the SP manages the
network all the way up to and
including the end device then
some form of demarcation is
required
Internet
Or Peer Netork Provider
TDM Network
SIP
Apps
SBC
C7
ISUP
NGN Network
& Service Provider
SBCs can be used as SLA

demarcation points
SBCs allow internal QoS
monitoring ensuring issues
can be categorised as SP or
non-SP.
SIP Trunking for IP

PSTN Access
SBC
SBC
Unmanaged access
network
SBC
DSLAM
xDSL
Connections
Cisco Public
IP PBX
ETTx etc.
DSLAM
xDSL
Connections
IP PBX
ETTx etc.
55
ASR 1000 Series Session Border Controllers

Multi-service scale
No need to create overlay network; eliminate
additional appliances
Easier operations/lower costs
Integrated with BRAS, IPSec, FW, Ucast, Mcast. All
can be enabled simultaneously
Best in price-performance, with choice of
2RU/4RU/6RU Chassis and 5G, 10G, 20G engines
Up to 32K sessions with RP1/ESP10
Cisco ASR 1000 Series

Fully Integrated - No
Service Blades required.
Flexible and open architecture

Range of interfaces, chassis and engine options
Clear upgrade path with ASR 1000 HW roadmap
Continuous system operation

Stateful redundancy with active session
preservation
In-Service Software Upgrades
SIP Trunking for IP

PSTN Access
Choice of ASR chassis,

RP, ESP engines and
clear platform HW
roadmap for upgrades
Distributed SBC model

- aligns with IMS, ITU,
TISPAN architectures
Cisco Public
56
Q&A
SIP Trunking for IP

PSTN Access
Cisco Public
57
Cisco.com SIP Trunk and CUBE

Resources
Cisco UBE on Cisco.com
http://www.cisco.com/go/cube
Cisco Communications
Transformations Whitepapers
(section of Whitepapers)
Customer Case Studies

Cisco Networkers Presentations

SIP Trunks for PSTN
CUBE Designs
Cisco UBE PBX Interoperability Reports (Avaya / Nortel)

www.cisco.com/go/interoperability
CUCM 6.x SIP Trunk Documentation:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/6x/trunks.html#wp
1044916
CVP 7.0 SIP Trunk Integration

http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/
customer_voice_portal/srnd/7x/cvp_gtwy.html#wp1048342
SIP Trunking for IP

PSTN Access
Cisco Public
58
Cisco.com SIP Trunk Design

Documents
Document
Coverage
Reference
Location
CUCM 7.x SRND
CUCM Connectivity to SIP Trunks
cisco.com/go/srnd
- Unified Communications
- Unified Communications Manager
- View Design Guide (CUCM 7.x)
- Cisco Unified CM Trunks
- Cisco Unified Border Element
CVP 7.x SRND
Contact Center: CVP + CUBE
cisco.com/go/srnd
- Unified Communications
- Voice Portal
- View Design Guide (CVP 7.x)
- Gateway Options
- Cisco Unified Border Element
CUBE in Contact
Center Configuration
Guide
Contact Center: CVP + CUBE
http://cisco.com/en/US/docs/voice_i
p_comm/unified_communications/c
ubecc.html
SP SIP Trunk Interop
CUCM/CUBE Validation testing

with specific SP Offerings:
- AT&T TollFree, FlexReach, VoEVPN
- Allstream
- Verizon
- Paetec
cisco.com/go/interoperability
Cisco Unified Border Element
SIP Trunking for IP

PSTN Access
Cisco Public
59
SIP Trunking for IP

PSTN Access
Cisco Public
60

Vatanasov SIP Trunking

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Vatanasov SIP Trunking

Загружено:

Авторское право:

Доступные форматы

SIP Trunking for IP

2008 Cisco Systems, Inc. All rights reserved.

2008 Cisco Systems, Inc. All rights reserved.

2008 Cisco Systems, Inc. All rights reserved.

SIP Trunking for IP

2009 Cisco Systems, Inc. All rights reserved.

SIP Trunking for IP

2009 Cisco Systems, Inc. All rights reserved.

Designing and Configuring a Network for SIP

SIP Trunking for IP

2009 Cisco Systems, Inc. All rights reserved.

SIP Trunking for IP

2009 Cisco Systems, Inc. All rights reserved.

SIP Trunks Extend the Benefits of Converged

Residential Administrative Domain

SIP Trunking for IP

2009 Cisco Systems, Inc. All rights reserved.

Migration to End-to-End VoIP

Unified communications SIP

SIP Trunking for IP

2009 Cisco Systems, Inc. All rights reserved.

What is a SIP Trunk?

Any SIP-based connection between two applications

SIP Trunking for IP

2009 Cisco Systems, Inc. All rights reserved.

SIP Trunks for PSTN Access

SIP Trunking for IP

2009 Cisco Systems, Inc. All rights reserved.

SIP Trunks for PSTN Access

Future new rich-media services that cannot be done on TDM

SPs are motivated by:

Incumbents: Address new markets instead of cannibalizing their TDM base

SIP Trunking for IP

2009 Cisco Systems, Inc. All rights reserved.

SIP Trunks for PSTN Access

SIP Trunks can be

SIP Trunks are always

SIP Trunks provide the

SIP Trunks are easy to

SIP is easy to deploy, but interconnection between different vendors

SIP Trunks should

Evaluate carefully. In some cases TDM trunks make a better choice. Or

SIP Trunks offer the ability to have a voice call over

SIP Trunks offer the ability to have improved redundancy

Lower Costs by consolidating equipment and tariff flexibility

SIP Trunking for IP

2009 Cisco Systems, Inc. All rights reserved.

The Line Side Has Flipped to IP

Source: Infonetics, 2007

2001 2002 2003 2004 2005 2006 2007 2008 2009

How many years

North American SIP Trunk Forecast

Two years into 5, 10

2009 Cisco Systems, Inc. All rights reserved.

* Frost and Sullivan, July,

Crossing the Chasm SIP Trunks

The SIP trunking market is in the crossing the chasm state:

Chasm of SIP Trunking as typical service will be crossed by 2010

2009 Cisco Systems, Inc. All rights reserved.

SIP Trunk Considerations

Poorly understood legal and

Requires in-depth evaluation

2009 Cisco Systems, Inc. All rights reserved.

SIP Trunking for IP