CHAPTER37 Advanced SBC Features
Mediant 800 Gateway & E-SBC | User's Manual
Call-ID: XDRXGAAWNVBTFHBMQCKE@10.33.2.38
CSeq: 1 REGISTER
Contact: <sip:300@10.33.2.40>
■ User 2 Registration:
REGISTER sip:300@10.33.4.140;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.33.2.40;branch=YHDWUJRMMOEIJRXVYKHD
From: <sip:300@domain2;user=phone>;tag=CVYTCHLIVMPBCGNGRTUA
To: <sip:300@domain2;user=phone>
Call-ID: INRNGFCHFHETRXAQNAIT@10.33.2.38
CSeq: 1 REGISTER
Contact: <sip:300@10.33.2.40>
For two such user registrations as shown in the example above, the device adds two AORs
("300@domain1" and "300@domain2") to its registration database, where each AOR is assigned
the same Contact URI ("300@10.33.2.40"). To route a call to the correct user, the device needs to
search the database for the full URl (user@host parts). To enable this support, perform the
following configuration steps:
➢ To enable handling of multiple AORs with identical Contact URIs:
1. Open the Proxy & Registration page (Setup menu > Signaling & Media tab > SIP
Definitions folder > Proxy & Registration).
2. From the 'DB Routing Search Mode' drop-down list (SBCDBRoutingSearchMode), select Dest
URI dependant, and then click Apply.
Enabling Interworking of SIP and SIP-I Endpoints
The device can interwork between SIP and SIP-I endpoints for SBC calls. SIP-I endpoints are
entities that are connected to the SS7 PSTN network, referred to as the ISDN User Part (ISUP)
domain. The device supports the SIP-I Application-layer signaling protocol, which is the standard
for encapsulating a complete copy of the SS7 ISUP message in SIP messages, according to ITU-T
Q.1912.5, Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call
Control protocol or ISDN User Part. In other words, SIP-I is SIP encapsulated with ISUP and the
interworking is between SIP signaling and ISUP signaling. This allows you to deploy the device in a
SIP environment where part of the call path involves the PSTN.
- 848 -
To Next Page
Loading...
