Version 7.2 749 Mediant 500L Gateway & E-SBC
User's Manual 39. Advanced SBC Features
networks in France. For SPIROU, the device sets the value of the SIP Content-Type
header to "version=spirou; base=itu-t92+".
ITU-92, where the device sets the value of the SIP Content-Type header to
"version=itu-t92+; base=itu-t92+".
To configure interworking of SIP and SIP-I endpoints, using the 'ISUP Body Handling'
parameter (IpProfile_SBCISUPBodyHandling) in the IP Profile table (see ''Configuring IP
Profiles'' on page 438).
You can manipulate ISUP data, by configuring manipulation rules for the SIP Content-Type
and Content-Disposition header values in the Message Manipulations table (see
''Configuring SIP Message Manipulation'' on page 415). For a complete description of the
ISUP manipulation syntax, refer to the SIP Message Manipulation Reference Guide. In
addition, you can use AudioCodes proprietary SIP header X-AC-Action in Message
Manipulation rules to support various call actions (e.g., SIP-I SUS and RES messages) for
the ISUP SPIROU variant. For more information, see Using the Proprietary SIP X-AC-
Action Header on page 724.
39.4 Handling Registered AORs with Same Contact URIs
The device can handle registration and call routing in cases where user registration
includes AORs with identical Contact header URIs, as shown in the example below. Such a
scenario typically occurs when two SIP endpoints reside in separate private networks and
both are assigned the same local IP address.
User 1 Registration:
REGISTER sip:300@10.33.4.140;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.33.2.40;branch=OTGHREPCXDBIWECOCPJK
From: <sip:300@domain1;user=phone>;tag=ULYEYCGXHXMBPSOCXVWH
To: <sip:300@domain1;user=phone>
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 for 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.
To Next Page
Loading...
