Handling Registered Aors With Same Contact Uris - AudioCodes E-SBC User Manual

CHAPTER 37 Advanced SBC Features
◆
● Index 2:
◆
◆
● Index 3:
◆
◆
7. In the Classification table, configure rules to classify calls from the IP Phones based on SIP
Interface:
● Index 0:
◆
◆
● Index 1:
◆
◆
8. In the IP-to-IP Routing table, configure the routing rules:
● Index 0:
◆
◆
● Index 1:
◆
◆
● Index 2:
◆
◆
● Index 3:
◆
◆

Handling Registered AORs with Same Contact URIs

The device can handle registration and call routing in cases where user registration includes AORs
with the same 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>
Classify By Proxy Set: Enable
Type: User
Name: IP-Phone-A
Type: User
Name: IP-Phone-B
Source SIP Interface: Interface-1
Source IP Group: IP-Phone-A
Source SIP Interface: Interface-2
Source IP Group: IP-Phone-B
Source IP Group: IP-Phone-A
Destination IP Group: Primary-Proxy
Source IP Group: Primary-Proxy
Destination IP Group: IP-Phone-A
Source IP Group: IP-Phone-B
Destination IP Group: Sec-Proxy
Source IP Group: Sec-Proxy
Destination IP Group: IP-Phone-B
Mediant 1000 Gateway & E-SBC | User's Manual
- 825 -