Acme Packet Solution: Net-Net SIP Multimedia-Xpress

N
O
TI
01/2012
LU
SO
Net-Net SIP
T
Multimedia-
Xpress
KE
C
Simplifying trusted, first class, SIP interactive
communications session delivery | Technical
PA
Overview
E
M
C
N
O
Disclaimer
TI
Acme Packet has made no commitments or
LU
promises orally or in writing with respect to delivery
of any future software features or functions. All
SO
presentations, RFP responses and/or product
roadmap documents, information or discussions,
either prior to or following the date herein, are for
T
informational purposes only, and Acme Packet has
KE
no obligation to provide any future releases or
upgrades or any features, enhancements or
C
functions, unless specifically agreed to in writing by
PA
both parties.
E
M
01/2012 ACME PACKET CONFIDENTIAL | Net-Net SIP Multimedia-Xpress Technical Overview 2

C
N
O
Table of contents
TI
 Business drivers & solution requirements
LU
 Net-Net SMX solution
SO
 Use cases
 Deployment architectures
T
 Signaling – theory of operation
KE
C
PA
E
M

C
N
IMS - too complex and costly today,
O
hinders service expansion & innovation
TI
 IMS complexity & cost
LU
– Too many decomposed
functions = too many products Carriers must come to grips with
the fact that IMS is too costly and
SO
– Many signaling interactions
complex to adopt in a wholesale
– Complexity slows network
manner and that the architecture
migration
will be adopted over the next few
– Not for all service providers
T
years in an incremental fashion.
 IMS goals remain
– Access network independence
– Service expansion & innovation
KE IMS Status Report:
A Protracted Adoption
C
– Common service delivery platform
for fixed & mobile
PA
– Central subscriber profiles

– Integrated mobility
E
– Rapid deployment of new

applications and services
M
01/2012 ACME PACKET CONFIDENTIAL | Net-Net SIP Multimedia-Xpress Technical Overview

4
C
N
Net-Net SIP Multimedia-Xpress - simplifying
O
IMS
TI
 Integrated session delivery platform
LU
 Provides IMS access, call session
SMX
SO
control, routing and interconnect
functions in single platform
 Eliminates signaling complexity versus
T
 Lowers total cost of ownership
– CAPEX - fewer systems to deploy KE
C
– OPEX savings - easier to certify,
maintain & troubleshoot
PA
E
M

C
N
O
Net-Net SMX – comprehensive solution
TI
Service & applications data centers (IMS/NGN)
 Integrated session delivery core in Net-Net
LU
SBC ENUM/DNS PSTN
 IMS solution for voice, RCS(-e), FMC
& multimedia services
SO
Cx
– Subscriber populations of thousands to IP peer
millions ISC
Mg, Mj
Rf
– Initial service roll-outs evolving to large
scale Ici
T
e2
subscriber deployments
Growth & evolution SMX
KE

SMX
SMX
– Scalable Net-Net SMX – SLB with SBC
clusters and interconnect & routing Rx Rx/Rq
solutions
C
Gm Gm
– Optional path to decomposed IMS; SBC

investment preserved
PA
EPC FTTx
xDSL
Cable
 Lower total cost of ownership Enterprise
– CAPEX - fewer systems to deploy, $1-4
E
per subscriber end point

eUTRAN
– OPEX savings - easier to certify,
M
maintain & troubleshoot LTE Fixed Access

C
N
O
Net-Net SMX reduces CAPEX & OPEX
TI
 OPEX - simplified signaling model, easier to maintain &
LU
troubleshoot
 CAPEX- fewer systems to certify, deploy & maintain
Decomposed IMS Net-Net SMX
SO
Data center Data center
PSTN PSTN
T
IP peer IP peer
P-CSCF
Backbone
KE SMX
SBC
Backbone
C
PA
Wireless Wireline Wireless Wireline

DSL/Cable DSL/Cable
FTTX FTTX
E
M

C
N
Net-Net SIP Multimedia-Xpress
O
– the Acme Packet edge
TI
 Industry leading SBC capabilities
LU
Data center
 Low cost for integrated service PSTN
SO
delivery solution with reduced
operating expenses
IP peer
T
SMX
 Cost effective & flexible system
evolution for subscriber growth
KE Backbone
C
 Flexible subscriber database
Wireline
options - HSS, ENUM or local Wireless
PA
DSL/Cable
FTTX
E
M

C
8
N
O
Industry leading SBC capabilities
TI
 Multi-protocol – SIP, H.323, MGCP/NCS, H.248, RTSP, MSRP,
LU
H.239; H.248 border gateway control
 Security – Net-SAFE: SBC DoS/DDoS protection, access control,
topology hiding, VPN separation, privacy; virus & SPIT protection;
SO
service infrastructure DoS prevention; fraud prevention;
monitoring & reporting; IDP/IDR; encryption – IPsec, TLS, SRTP
 Service reach – NAT traversal; IP address translation – private-
T
public, OLIP/VPN bridging, IPv4-IPv6; number & URI
manipulation; signaling message header manipulation; protocol
KE
interworking – signaling, transport & encryption protocols,
SIP/SIP-I/SIP-T; response code translations; transcoding &
transrating; SDP & DTMF manipulation
C
 SLA assurance – admission control – signaling & bandwidth
PA
constraints per user, network or session agent; signaling overload

control; transport control – QoS marking/VLAN mapping, peer-
peer media release; policy control; QoS & ASR routing &
reporting; network element (L3 router, registrar, session agent)
E
failure discovery, re-routing &/or load balancing; QoE reporting

M

C
N
Industry leading SBC capabilities
O
(continued)
TI
 Revenue & cost optimization – accounting; routing
LU
– source or destination-based, LCR, ENUM, by codec;
CNAM; service theft protection – bandwidth policing,
QoS marking; session timers; service core
SO
normalization
 Regulatory compliance – lawful intercept &
emergency services – E911 & GETS; session
T
replication for recording

KE
High availability – checkpointing of media,
signaling, IPsec tunnel & config state ensures no loss
of active sessions, or state required for NAT traversal,
C
session handling (transfer/hold, etc.) or accounting
PA
 Management – EMS, RMC, CLI, HTTPS, XML, telnet,

FTP, SFTP, RADIUS, SNMP, syslog, secure
management
E
M

C
N
O
Integrated service delivery solution
TI
 Compact, scalable solution
LU
– All functions in single 1 RU system, SLB
cluster or ATCA chassis
– Cluster support for millions of subscribers
Net-Net SMX
SO
 Access and service core delivery functions
– SBC with P-CSCF, E-CSCF, IMS-AGW & SIP system architecture
firewall functions
– SIP registrar & core session control functions
ALF Cx, DNS
 IMS SIP, Diameter & ENUM interfaces
T
I-CSCF/S-CSCF
– HSS, ENUM or local subscriber database
KE
– Service orchestration with application servers Rf
ISC reference interface SCF
P-CSCF, E-CSCF, e2
– PCRF, OCS & RACS (Rx, Rf) SFF
I-BCF, B2BUA
– NASS/CLF (e2) IWF Signaling
C
Mi, Mx,
– PSTN break-in/break-out (Mj) Ia+ Mj, ISC
PA
 Optionally integrated functions

Policy enforcement Rx
– Interconnect SBC (I-BCF, IWF & TrGW)
– Session routing (BGCF)
BGF Media
E
Mb
M

C
N
55-75% less per subscriber than
O
traditional IMS solutions
TI
LU
SO
T
KE
C
PA
E
M

C
N
O
OPEX Savings
TI
 Lower CAPEX = lower Net-Net SMX
LU
annual maintenance
support contracts
SO
 Savings in expertise &
training of operation and
T
maintenance teams
 Savings in certifying and KE Vs
Traditional IMS
C
deploying infrastructure
PA
 Savings in integrating
applications; improved
time to market
E
M

C
N
Fewer systems; simpler signaling &
O
operation
TI
IMS SIP REGISTER model
LU
P-CSCF
SO
20 messages
between
T
5 systems
KE
C
SMX SIP REGISTER model
PA
SMX
10 messages
E
between
3 systems
M

C
N
O
Simplicity and interoperability built-in
TI
LU
Smart Border IMS Net-Net SMX

PSTN PSTN
SO
IP peer IP peer
T
P-CSCF SMX
SBC
Complex signaling difficult to debug

KE Simplified signaling improves operation
and debugging dramatically
C
Integrated call control functions minimize
Signaling issues slow deployments signaling issues; streamlining deployment
PA
Interoperability issues with application

Leverage HMR to swiftly achieve
servers could delay delivery of new
interoperability with application servers
services
E
M

C
N
Inherent service stability and geographic
O
distribution with session-aware load
balancer
TI
LU
Smart Border IMS Net-Net SMX
SO
PSTN PSTN
IP peer IP peer
T
SMX SMX SMX SMX SMX SMX
P-CSCF
KE
SBC
SLB
Under heavy load, session service delivery Session service delivery remains
C
becomes unstable distributed and stable under heavy load
PA
No inherent load detection or rebalancing Automatic and graceful load re-distribution
No inherent geo-redundancy SLB allows geo-redundant deployment

E
M

C
N
Net-Net SMX allows cost-effective,
O
scalable evolution Data center
TI
PSTN
LU
• Initial deployment
• Access border functions
IP peer
• Routing functions SMX
SO
• Interconnect functions
• Single SMX SBC supports up to 250K Data centers
registered end points
• Scale for subscriber growth PSTN
T
• Deploy SMX SBC cluster(s) with
integrated routing
• Single SMX SBC cluster supports up
to 2M registered end points
KE SMX
SMX
SMX
SMX
IP peer
C
• Scale for IP interconnect growth
Data centers
• Deploy interconnect SBC to
PA
accommodate additional IP peers

PSTN
• Deploy high performance
session routing proxy to offload from
E
SMX SBC cluster(s) IP peers

SMX
SMX
SMX
SMX SRP SBC
M
BGCF SBC
SBC
I-BCF
I-BCF
I-BCF
C
N
Optional SIP Multimedia-Xpress evolution
O
to Smart Border de-composed IMS solution
TI
LU
 Fully compliant, Smart Border IMS
architecture evolution
 Net-Net SMX SBC evolution
SO
– SBC remains at access border Data center
– Dedicated as access SBC with
P-CSCF, E-CSCF, IMS-AGW & PSTN
SIP firewall
T
– Configure interfaces to new elements
Acme Packet elements SRP
KE
 BGCF
IP peer
– Interconnect SBC – I-BCF, TrGW & IWF
– Session routing proxy – BGCF SBC
I-BCF
C
 Deploy new I-CSCF and S-CSCF P-CSCF
 Deploy HSS subscriber database (if ENUM
PA
server previously deployed)

E
M

C
N
O
Multiple subscriber database options
TI
HSS ENUM Local
LU
Query
High performance; High performance; Highest performance;
performance High to mid-range cost Mid-range cost lowest cost
versus cost
Millions of end points Billions of end points Up to 250K end points
SO
Capacity
Standards /
Diameter Cx ENUM / DNS / DDNS ENUM / XML
interfaces
Message types ENUM/DNS: “Local” ENUM:
Diameter Cx:
T
supported Query/response Query/response
UAR/UAA - User Authorization
SAR/SAA - Service Assignment
KE
DDNS: Dynamic DNS
LIR/LIA - Location Information
MAR/MAA - Multimedia Authorization
RTR/RTA - Registration Termination
C
Interoperability HSS / CSCF signaling interaction is Utilizes standard Utilizes simple XML
complexity proprietary for some vendors’ signaling found in format to store auth
PA
implementations commercial and open credentials in

source ENUM/DNS standalone solution for
servers up to 250K end points
Support Optional feature per vendor Standard feature – Standard feature

E
multiple implementation NAPTR results with

same order and
contacts per
M
preference values
DN
C
N
Net-Net SIP Multimedia-Xpress
O
Use cases
TI
LU
 IMS access service delivery (VoLTE & fixed line)
 RCS (Rich Communication Services)
SO
 Fixed mobile convergence
T
 Contact Center
 Over-the-top VoIP & video calling service KE

C
PA
E
M

C
N
O
IMS access service delivery with SMX
TI
Service & applications data centers
(IMS/NGN)
 Voice, video and RCS-e services
LU
– SIP VoIP & video calling service ENUM/DNS PSTN
– Presence-based IM service
SO
– Multimedia content sharing – Cx/Dx
IP peer
video share, picture/file transfer
ISC
Mg, Mj
 Net-Net SMX SBC Rf
– SBC with registrar
T
Ici
e2
– Digest authentication of SIP registrations
KE
SMX
SMX
– Diameter Cx interface with HSS SMX
– 3rd party registration to application servers Rx Rx/Rq

C
Other solution components Gm Gm
– SIP IM, VoIP and video clients

PA
– RCS, voice and video application servers EPC FTTx

xDSL
– HSS subscriber database Cable
Enterprise
– ENUM routing database
E
– Policy via PCRF/RACS

eUTRAN
M
LTE Fixed Access

C
N
O
RCS with SMX
TI
Facebook SMSC
 Rich Communication Suite services FlickR
LU
Twitter
– Presence-based IM WLM GoogleTalk
– Multimedia content sharing –
SO
video share, picture/file transfer
SMS IWF SIP/XMPP
– Interfaces to Web/social networks
– Mobile and Internet delivery networks AP
 Net-Net SMX SBC
T
WLM GW IM XDMS PS
–
– DNS/ENUM interface – subscriber KE
Digest authentication of SIP registrations
authentication & dynamic DNS update

SMX
C
– 3rd party registration to application servers IP Backbone / Internet
PA
 Other solution components

– SIP IM clients
– RCS application servers
E
– ENUM server subscriber database

Mobile SIP PC SIP Communicator
M
Communicator IM client IM client

C
N
O
FMC with SMX
TI
 Cost-effective roaming/out of coverage
LU
IMS PSTN
areas
Services
– Single number - make and receive calls in & apps
both IMS and legacy HLR networks
SO
– Send and receive SMS messages in both
IMS and legacy HLR networks Core IP
Backbone
TDM/SS7
Backbone
– Roam geographically / internationally via transport
broadband / WiFi / Internet
T
 Net-Net SMX SBC
KE
Aggregation BSS
– SIP digest authenticate registrations
PoP SMX
– Diameter Cx interface with HSS
C
– 3rd party registration to
application server (IS-41 gateway)
PA
 Other components Internet RAN

– SIP IM / VoIP clients Access
– MAP/IS-41 gateway app server
– HSS subscriber database
E
M

C
N
O
Enterprise & contact center with SMX
TI
 Low cost, high performance call
LU
Contact Contact
management / routing PSTN
center
site B
center
site C
– Replace / eliminate need for other costly call Out-
sourced
managers services
SO
– Register / authenticate local and remote Service
providers MPLS VPN Hosting
agents provider
– Manage inbound & outbound calling

 Net-Net SMX SBC
T
Contact center site A
– SBC with registrar Agents
KE SMX
– SIP digest authenticate registrations
– DNS/ENUM interface –
subscriber authentication & dynamic DNS
C
update for location or local subscriber
database for <250K registered SIP end
PA
points Managed
Internet
network
– 3rd party registration to IVR /
application servers
 Other components
E
– IVR, Application / media servers Callers Callers Home Remote

agent site
M

C
N
Over-the-top VoIP & video calling service
O
with SMX
TI
 Service delivered
LU
– SIP VoIP & video calling service
Data Center Conference
– Roam geographically / internationally PSTN
VMAIL
SO
via broadband / WiFi / Internet
– Universal DN calling
IP peers
– Radio Access Network by-pass / off-
SBC
load
T
 Acme Packet SMX SBC
KE
– SBC with registrar SMX
– Digest authentication of SIP
registrations Private IP Backbone / Internet
– ENUM/DNS or HSS/Cx interface –
C
subscriber authentication & location
update
PA
– Routing to IP peers, vmail,

conferencing & PSTN
 Other components
Mobile SIP Mobile SIP
– SIP VoIP & video clients PC SIP PC SIP
E
VoIP/video VoIP/video VoIP/video VoIP/video

– Vmail & conferencing servers client client client client
M
– ENUM server or HSS

C
N
O
Net-Net
TI
Data centers
 Cost effective, integrated
LU
service delivery core solution PSTN
SO
 Cost effective, scalable system SRP
IP peers
 High performance, scalable SMX

SMX
SMX
SMX SBC
subscriber databases
T
Backbone
 Simplified architecture, reduces
operating expenses KE Wireline
C
Wireless Wireline
DSL/Cable
 Accelerates revenue by DSL/Cable
FTTX
FTTX
PA
allowing rapid introduction of

new applications & services
with less complexity
E
M

C
N
O
TI
LU
Net-Net SIP
Multimedia-Xpress
SO
Deployment
Architectures
T
KE
C
PA
E
M

C
N
Single SMX SBC deployment with local
O
subscriber database
TI
 Provides deployment for up to
LU
250K registered end points Data center
 Provides SIP registration and PSTN
SO
subscriber authentication for
service access authorization
IP peer
 May be used for smaller service
T
provider deployments
 May be used in place of call

managers in contact center with KE Backbone or Internet
C
interactive voice response service
or other application Wireless Wireline
PA
DSL/Cable
servers FTTX
 Uses onboard local subscriber

database; ENUM or HSS not
E
Service provider subscribers,

required contact center operators & others
M

C
N
Flexible SMX cluster deployment options
O
– co-located cluster solution
TI
 2M registered end points
LU
Services & apps datacenters
supported per cluster
PSTN PSTN
 Aggregation PoP
SO
– Suited for large access *each SMX SBC has identical signaling paths*
IP peer IP peer
geographic footprint
– Eliminates core transport
bandwidth consumption
T
for hair pinned service paths
 Core
KE
Data center
transport
– Suited for smaller access
geographic footprint
C
 SLBs and SMX nodes
Aggregation
physically co-located PoPs
PA
 Each cluster operates as

single virtual SMX node; single
IP address may be provisioned
E
in clients for each cluster

Mobile Residential Enterprise
M
SBC
Access Access Access cluster

C
N
O
– distributed cluster solution
TI
 SLB and SMX SBCs
LU
physically distributed Services & apps datacenters
via encapsulated IP PSTN PSTN
SO
connections
 Subscriber load IP peer *each SBC has identical signaling paths*
IP peer
balancing across multiple

PoPs and/or data centers
T
 1:1 SMX SBC Pool:SLB Core
KE
transport
relationship
 Improved geo-redundancy
C
 Each cluster operates as Aggregation
PoPs
single virtual SMX SBC;
PA
single IP address may be

provisioned in clients
for each cluster
E
Mobile Residential Enterprise SBC

M

C
N
O
– distributed cluster solution
TI
 SLB and SMX nodes
LU
physically distributed
via encapsulated IP Services & apps datacenters
connections PSTN PSTN

SO
Subscriber load
balancing across
multiple IP peer *each SBC has identical signaling paths*
IP peer
PoPs and/or data
centers

T
1:1 SMX node pool:
SLB
Core
KE
relationship
transport
 Improved geo-
redundancy
 Each cluster operates
C
as Aggregation
single virtual SMX PoPs
PA
node;
single IP address may
be
provisioned in clients
for each cluster
E
Mobile Residential Enterprise SBC

M

C
N
Flexible SMX cluster deployment
O
options – fully distributed, fully meshed
cluster model
TI
LU
 SLB and SMX nodes
physically Services & apps datacenters
distributed PSTN PSTN
via encapsulated IP
SO
 Multiple SLBs per IP peer
cluster per SMX IP peer *each SBC has identical signaling paths*
node
 All SMX nodes
treated
T
as common resource Core
pool
KE
transport
 Improved geo-
redundancy Aggregation
over distributed
C
PoPs
model
 Cluster operates as
PA
single virtual SMX

node;
single IP address
may be
provisioned in
E

clients Access Access Access
SBC
cluster
M

C
32
N
Subscriber and services growth to
O
SMX multi-cluster with BGCFs & I-BCFs
TI
 Multiple SMX clusters
LU
supporting up to 2M Services & apps datacenters
subscribers
 SMX nodes scale as PSTN PSTN
subscriber and service
SO
demands grow
 Session Routing Proxies IP peer
IP peer
(BGCF) perform routing to
*each SBC has identical signaling paths*
IP peers and PSTN
 Interconnect SBCs (I-BCF)
T
secure border with IP peers
 Clusters operate as single
virtual SMX node; clients
may
be provisioned with IP
address
KE Core
transport
C
for each cluster providing Aggregation
geo-redundancy PoPs
PA
E

M
Access Access Access SBC

cluster

C
Acme Packet
N
Optionally evolve SMX clusters to
O
de-composed IMS solution
TI
 De-composed IMS architecture Services & apps
LU
evolution datacenters
 SMX evolution
– Remains at access PSTN PSTN
SO
border
– Dedicated as access
SBC IP peer IP peer
with P-CSCF, E-CSCF, *each SBC/P-CSCF has
IMS-AGW & SIP firewall identical signaling paths*
– Configure interfaces to
T
new
KE
elements
 Interconnect SBC – IBCF, Core
TrGW & IWF transport
 Session routing proxy – BGCF
C
 Deploy new I-CSCF and S-
Aggregation
CSCF
PoPs
PA
 Clusters operate as single

virtual
P-CSCF; clients may be
provisioned with IP address for
each cluster providing geo-
E
redundancy
M
SBC

C
Acme Packet
N
O
TI
LU
Net-Net SIP
Multimedia-XPress
SO
Signaling - theory of
operation
T
KE
C
PA
E
M

C
N
O
IMS SIP register model inefficient
TI
LU
SBC
SO
T

consuming capacity KE
SIP register dialog state maintained across three SIP systems; taxing performance;
C
 Each SIP registration crosses three SIP systems and requires multiple HSS transactions
 SBC with integrated P-CSCF performs security, spoofing protection, overload protection sends
PA
REGISTER to I-CSCF
 I-CSCF queries HSS and selects S-CSCF
 S-CSCF queries HSS to retrieve auth data, creates challenge to end point and downloads filter
criteria
For digest-challenge or IMS-AKA, the SIP register message flow occurs twice
E

 First time without auth data and 401/407 challenged, second time includes auth data and finally
updates HSS
M

C
N
IMS SIP register model more
O
efficient with Smart Border SBC
TI
LU
SBC
SO
T
KE
C
PA
 SBC offloads registration refreshes from core after initial

registration
 Reduces work for core
E
 Provides NAT pinhole maintenance (HNT), failure detection, geo-

redundancy and SIP interoperability fixing/interworking
M

C
N
SMX SIP register model simple &
O
efficient
TI
LU
SBC
SO
T
 KE
No need to use discreet P, I & S-CSCF to handle a security function
 SMX SBC can challenge end point’s SIP REGISTER message
C
 No need to have P, I & S-CSCF each cache contact information per end point
 Simpler to troubleshoot & support
PA
 Simplify the network, increase scale

 SBC is necessary due to security, HNT, overload control and SIP interoperability
& interworking
 Subscriber database (HSS or ENUM server) is necessary, to store subscriber
credentials & end point location info
E
 Everything else is not necessary

M

C
N
O
TI
LU
Net-Net SIP
Multimedia-XPress
SO
Signaling – 3GPP Cx
(Diameter)
T
KE
C
PA
E
M

C
N
Cx/HSS in action for SIP REGISTER
O
(auth & location update)
TI
LU
SBC
Data center
SIP REGISTER
SO
Cx User-Authorization-Request
PSTN
Cx User-Authorization-Answer
Download IP peer
T
Cx Multimedia-Auth-Request auth data
SBC
KE
Cx Multimedia-Auth-Answer
SIP 401 Unauthorized Backbone

Compare
auth data
SIP REGISTER w/authorization
C
Update
location
info
Cx Server-Assignment-Request
PA
Cx Server-Assignment-Answer
SIP 200OK
Wireless Wireline
DSL/Cable
E
SIP ACK
Optional: 3rd party REGISTER FTTX
(push location info)
M

C
N
SMX – Cx/HSS in action for simple
O
call routing - SIP INVITE
TI
SMX1 SMX2
LU
User A User B
Data center
SMX
SBC SMX
SBC
SO
SIP INVITE
PSTN
Cx Location-Information-Req
(User B)
SMX1 SMX2
Cx Location-Information-Ans IP peer
(SMX2)
T
SIP INVITE
SBC SBC
SIP 180 RINGING KE SIP INVITE
SIP 180 RINGING SIP 180 RINGING

Backbone
C
SIP 200OK SIP 200OK SIP 200OK
PA
SIP ACK SIP ACK SIP ACK
RTP RTP RTP

User A User B
E
M

C
N
O
TI
LU
Net-Net SIP
Multimedia-XPress
SO
Signaling – IETF
ENUM (DNS/DDNS)
T
KE
C
PA
E
M

C
N
SMX – DNS/ENUM in action for SIP
O
REGISTER (auth & location update)
TI
LU
SBC
Data center
SO
SIP REGISTER
ENUM query (credential retrieval)
PSTN
ENUM response (return credential)
SIP 401/407 IP peer
T
Compare
credentials
SIP REGISTER w/authorization SBC
SIP 200OK
KE Update
location
Backbone
C
SIP ACK info
DDNS Update (push location info)
PA
DDNS Response (ack push)
Optional: 3rd party REGISTER (to AS)

(push location info)
Wireless Wireline
E
DSL/Cable
FTTX
M

C
N
SMX - DNS in action for simple call
O
routing - SIP INVITE
TI
LU
SMX
SBC SMX
SBC
Data center
SIP INVITE
SO
ENUM query (location?)
PSTN
ENUM response (target SBC)
SIP INVITE
IP peer
T
ENUM query
(location?)
SBC SBC
SIP 180 RINGING

KE
ENUM response
(target SBC) SIP INVITE
SIP 180 RINGING SIP 180 RINGING

Backbone
C
PA
RTP RTP RTP

E
M

C
N
How “features” may be performed using an
O
ENUM subscriber & routing database
TI
 ENUM query may result in one or more NAPTR
LU
records in a response
 NAPTR records returned in a response include
SO
weight and priority information that can be
leveraged for calling features
T
KE
 Advanced features require Application Servers
 ENUM can point to the App Servers, loose routing
C
via SIP Route headers
PA
 Application Servers can query ENUM or use SMX or

a Session Router (BGCF) to query until they
support ENUM
E
M

C
N
O
NAPTR Records
TI
 NAPTR records are defined in RFC 2915
LU
 Key components of the NAPTR record
Weight/ Flag Service Type Regular Replacement
SO
Priority Expression String
4.3.2.1 NAPTR 10 100 "u" "E2U+sip" "!^.*$!sip:user@example.com!" .

NAPTR 10 200 "u" "E2U+H323" "!^.*$!tel:+17035551212!" .
T
 Responses are ordered by weight and priority
KE
 Flag may indicate terminal/non-terminal NAPTR
 Flag of “” indicates additional query to resulting domain
 Flag of “u” indicates final answer
C
 Regular expression is applied to query number for ENUM
 Replacement string indicates new URI
PA
 Typical replacement captures all digits (^.*)$ but may capture sets of digits
 The captured digits are represented as \1, \2, etc. in replacement strings
 e.g "!(^.*)$!sip:\1@example.com!“
E
 e.g "!^(+1)(.*)$!sip:\2@example.com!“
M

C
N
Voicemail in SMX (call routing services)
O
555-1111 osbc tsbc 555-2222 vmail
TI
tsbc’s NAPTR results for
SBC 2.2.2.2.5.5.5.domain lookup
SBC
LU
SIP INVITE
ENUM query
(NAPTR lookup)
Data center
ENUM response
(target: tsbc)
SO
SIP INVITE
PSTN
ENUM query
(NAPTR lookup)
ENUM response IP peer

(multiple
T
NAPTR results) SIP INVITE
SBC SBC
KE
SIP 180 RINGING SIP 180 RINGING SIP 180 RINGING
Backbone
(Request Timeout
on No Answer)
SIP CANCEL
C
SIP 200OK
PA
SIP INVITE
SIP 200OK SIP 200OK SIP 200OK 555-1111 555-2222

E
RTP RTP RTP
lookup order pref flags replacement

M
2.2.2.2.5.5.5.domain 100 100 “u” 5552222@tsbc

2.2.2.2.5.5.5.domain 100 200 “u” 555222@vmail
47
C

N
O
Call forwarding in SMX
TI
555-1111 osbc tsbc 555-2222 555-3333
LU
SBC SBC
SIP INVITE Data center
ENUM query
(NAPTR lookup)
SO
ENUM response
(target: tsbc) PSTN
SIP INVITE
ENUM query
(NAPTR lookup) IP peer
T
ENUM response SBC SBC
(multiple
KE
NAPTR results) SIP INVITE
Backbone
SIP 180 RINGING SIP 180 RINGING SIP 180 RINGING

C
PA
RTP RTP RTP
555-1111 555-2222 555-3333
tsbc’s NAPTR results

E

2.2.2.2.5.5.5.domain 90 100 “u” 5553333@tsbc
M
2.2.2.2.5.5.5.domain 100 100 “u” 5552222@tsbc

2.2.2.2.5.5.5.domain 100 200 “u” 555222@vmail
C
N
Call forwarding -
O
details of DNS zone provisioning
TI
 In the example below, the portions in grey are provisioned by the service provider which include
LU
the hash of the subscriber’s password, used by SMX to compare with the hash provided in the SIP
REGISTER msg
 To enable call forwarding, in addition to the NAPTR record dynamically created by SMX at the time
of 555-2222’s SIP registration (in blue), an additional NAPTR record is needed for the calling
SO
forwarding number. This record may be provisioned through a subscriber portal application.
 The NAPTR record for the call forwarding number (in red below) needs to have a lower order than
the dynamically SMX-created NAPTR record (in blue below) to give it a higher priority. Additionally
this record has an empty/null flag which indicates the lookup is not terminal and that a subsequent
lookup will occur.
T
$ORIGIN 2.2.2.2.5.5.5
TXT "hash=<unique hash>"

KE
IN NAPTR 90 100 "" "E2U+sip" "" 3.3.3.3.5.5.5. serviceprovider.com.
IN NAPTR 100 100 "u" "E2U+sip" "!^.*$!sip:5552222@172.16.1.5:5060\;ts=1285186763!" .
There will also be a NAPTR record for the target 111-111, dynamically provisioned by SMX at the
C
time of 555-3333’s SIP registration.
$ORIGIN 3.3.3.3.5.5.5
PA

 With these NAPTR records provisioned in the DNS server, calls to 555-2222 will be forwarded to
555-3333 at 172.16.1.5:5060.
E
M

C
N
O
Multiple registered contacts in SMX
TI
555-1111 osbc tsbc 555-0001 555-0001 555-0001
555-1111 dials 555-0001
LU
SBC SBC
INVITE 555-0001
ENUM query (NAPTR lookup 555-0001)
Data center
SO
ENUM response (multiple NAPTR results)
PSTN
SIP INVITE 555-0001
SIP INVITE 555-0001
SIP INVITE 555-0001 osbc tsbc IP peer
T
ENUM query (NAPTR lookup for each INVITE)
ENUM response for each INVITE (tsbc)
KE
SBC SBC
SIP INVITE 555-0001
SIP INVITE 555-0001

Backbone

C
SIP CANCEL
SIP CANCEL
PA
RTP RTP RTP
555-1111 555-0001 555-0001 555-0001

1.0.0.0.5.5.5.doman 90 100 “u” 5552222@tsbc

E
1.0.0.0.5.5.5.doman 90 100 “u” 5552222@tsbc

osbc’s NAPTR results
1.0.0.0.5.5.5.doman 90 100 “u” 6664444@osbc
M
1.0.0.0.5.5.5.domain 100 200 “u” 5550001@vmail *some SIP 180, 200OK and ACK
messages omitted due to space constraints

C
N
“Find me, follow me” service in SMX
O
555-1111 osbc tsbc 555-2222 555-3333 666-4444
TI
555-1111 dials
SBC SMX find me, follow me virtual number
SBC
LU
INVITE 555-0001
ENUM query (NAPTR lookup 555-0001) (555-0001)
ENUM response (multiple NAPTR results)

Data center
SO
SIP INVITE 666-4444
SIP INVITE 555-2222 PSTN

SIP INVITE 555-3333
ENUM query (NAPTR lookup for each INVITE)

osbc tsbc IP peer
ENUM response for each INVITE (tsbc)
T
SIP INVITE 555-2222
KE
SIP INVITE 555-3333 SBC SBC
SIP 200OK SIP 200OK SIP 200OK Backbone
SIP CANCEL
C
SIP CANCEL
RTP RTP RTP
PA

1.0.0.0.5.5.5.doman 90 100 “” 2.2.2.2.5.5.5.domain 555-1111 666-4444 555-2222 555-3333
1.0.0.0.5.5.5.doman 90 100 “” 3.3.3.3.5.5.5.domain
1.0.0.0.5.5.5.doman 90 100 “” 4.4.4.4.6.6.6.domain
E
2.2.2.2.5.5.5.domain 100 100 “u” 5552222@tsbc osbc’s NAPTR results

3.3.3.3.5.5.5.domain 100 100 “u” 5553333@tsbc
M
*some SIP 180, 200OK and ACK

4.4.4.4.6.6.6.domain 100 100 “u” 6664444@osbc messages omitted due to space constraints
1.0.0.0.5.5.5.domain
01/2012 100 200 | Net-Net
ACME PACKET CONFIDENTIAL “u” 5550001@vmail Technical Overview
SIP Multimedia-Xpress 51
C
N
“Find me, follow me” (parallel ringing) -
O
TI
 To enable parallel ringing of multiple contacts, the service provider provides the subscriber with a
LU
portal to setup the phone numbers that they would like to have ring for the virtual service number
555-0001. The subscriber portal application will populate NAPTR records for each destination;
each with the same order value (in red). With lookup results in red returned for a call to 555-0001,
SO
SMX will perform a recursive lookup to resolve the contact for each number and simultaneously
place calls to 555-2222, 555-3333, 555-4444.
$ORIGIN 1.0.0.0.5.5.5
IN NAPTR 90 100 "" "E2U+sip" "" 2.2.2.2.5.5.5.serviceprovider.com.
T
KE
$ORIGIN 2.2.2.2.5.5.5
C
$ORIGIN 3.3.3.3.5.5.5
PA

$ORIGIN 4.4.4.4.5.5.5
E
M

C
N
“Find me, follow me” (serial ringing) -
O
TI
 Similar to parallel ringing, sequential or serial ringing can be accomplished by provisioning
LU
NAPTR records. For serial ringing the order of the call attempts is driven by the provisioned
“order” value. A negative response or a timeout will trigger the SMX to route advance to the next
destination in lowest to highest order.
SO
$ORIGIN 1.0.0.0.5.5.5
T
$ORIGIN 2.2.2.2.5.5.5
KE
$ORIGIN 3.3.3.3.5.5.5
C
$ORIGIN 4.4.4.4.5.5.5
PA

E
M

C
N
ENUM in action with originating &
O
terminating application servers
TI
OSBC OAS TSBC TAS B
A
LU
SIP INVITE
SBC SBC
ENUM query (location?)
ENUM response (target: tsbc
SO
with loose route to orig AS)
SIP INVITE PSTN

Route: OAS
Route: OSBC
SIP INVITE
Route: OSBC IP peer
T
SIP INVITE
SBC SBC
KE
ENUM query
(location?)
ENUM response
(target SBC with loose
route to term AS)
C
SIP INVITE
Route: TAS
PA
Route: TSBC
SIP INVITE
Route: TSBC
SIP INVITE
SIP 180 & 200OK (follows reverse path of INVITE)

E
SIP 180 & 200OK

SIP 180 & 200OK
M
SIP ACK (follows same path)
RTP
54
RTP RTP
01/2012 ACME PACKET CONFIDENTIAL | Net-Net SIP Multimedia-Xpress Technical Overview
C
C
M
Thank you!
E
PA
C
KE
T
SO
LU
TI
O
N

Acme Packet Solution: Net-Net SIP Multimedia-Xpress

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Acme Packet Solution: Net-Net SIP Multimedia-Xpress

Încărcat de

Drepturi de autor:

Formate disponibile

N

01/2012 ACME PACKET CONFIDENTIAL | Net-Net SIP Multimedia-Xpress Technical Overview 2

01/2012 ACME PACKET CONFIDENTIAL | Net-Net SIP Multimedia-Xpress Technical Overview 3

– Central subscriber profiles

– Rapid deployment of new

01/2012 ACME PACKET CONFIDENTIAL | Net-Net SIP Multimedia-Xpress Technical Overview

 Eliminates signaling complexity versus

01/2012 ACME PACKET CONFIDENTIAL | Net-Net SIP Multimedia-Xpress Technical Overview 5

– Optional path to decomposed IMS; SBC

per subscriber end point

maintain & troubleshoot LTE Fixed Access

01/2012 ACME PACKET CONFIDENTIAL | Net-Net SIP Multimedia-Xpress Technical Overview 6

Wireless Wireline Wireless Wireline

01/2012 ACME PACKET CONFIDENTIAL | Net-Net SIP Multimedia-Xpress Technical Overview 7

01/2012 ACME PACKET CONFIDENTIAL | Net-Net SIP Multimedia-Xpress Technical Overview 88

constraints per user, network or session agent; signaling overload

failure discovery, re-routing &/or load balancing; QoE reporting

01/2012 ACME PACKET CONFIDENTIAL | Net-Net SIP Multimedia-Xpress Technical Overview 9

 Management – EMS, RMC, CLI, HTTPS, XML, telnet,

01/2012 ACME PACKET CONFIDENTIAL | Net-Net SIP Multimedia-Xpress Technical Overview 10

 Optionally integrated functions

01/2012 ACME PACKET CONFIDENTIAL | Net-Net SIP Multimedia-Xpress Technical Overview 11

01/2012 ACME PACKET CONFIDENTIAL | Net-Net SIP Multimedia-Xpress Technical Overview 12

01/2012 ACME PACKET CONFIDENTIAL | Net-Net SIP Multimedia-Xpress Technical Overview 13

01/2012 ACME PACKET CONFIDENTIAL | Net-Net SIP Multimedia-Xpress Technical Overview 14

Data center Data center

Complex signaling difficult to debug

Interoperability issues with application

01/2012 ACME PACKET CONFIDENTIAL | Net-Net SIP Multimedia-Xpress Technical Overview 15

No inherent load detection or rebalancing Automatic and graceful load re-distribution

No inherent geo-redundancy SLB allows geo-redundant deployment

01/2012 ACME PACKET CONFIDENTIAL | Net-Net SIP Multimedia-Xpress Technical Overview 16

accommodate additional IP peers

SMX SBC cluster(s) IP peers

server previously deployed)

01/2012 ACME PACKET CONFIDENTIAL | Net-Net SIP Multimedia-Xpress Technical Overview 18

implementations commercial and open credentials in

Support Optional feature per vendor Standard feature – Standard feature

multiple implementation NAPTR results with

 RCS (Rich Communication Services)

 Over-the-top VoIP & video calling service KE

01/2012 ACME PACKET CONFIDENTIAL | Net-Net SIP Multimedia-Xpress Technical Overview 20

– SBC with registrar

– Digest authentication of SIP registrations

– SIP IM, VoIP and video clients

– RCS, voice and video application servers EPC FTTx

– Policy via PCRF/RACS

LTE Fixed Access

 Net-Net SMX SBC

authentication & dynamic DNS update

 Other solution components

– ENUM server subscriber database

Communicator IM client IM client

01/2012 ACME PACKET CONFIDENTIAL | Net-Net SIP Multimedia-Xpress Technical Overview 22

 Other components Internet RAN

01/2012 ACME PACKET CONFIDENTIAL | Net-Net SIP Multimedia-Xpress Technical Overview 23

– Manage inbound & outbound calling

– IVR, Application / media servers Callers Callers Home Remote

01/2012 ACME PACKET CONFIDENTIAL | Net-Net SIP Multimedia-Xpress Technical Overview 24

– Routing to IP peers, vmail,

VoIP/video VoIP/video VoIP/video VoIP/video

– ENUM server or HSS

 High performance, scalable SMX