AudioCodes Mediant 800 - Page 412

CHAPTER18 Core Entities
Mediant 800 Gateway & E-SBC | User's Manual
Parameter Description
■ [8] P-Associated-URI
■ [9] P-Called-Party-ID
■ [10] Contact
■ [11] Referred-by
Note:
■ The parameter is applicable only when classification
is done according to the Classification table.
■ If the configured SIP header does not exist in the
incoming INVITE message, the classification of the
message to a source IP Group fails.
■ If the device receives an INVITE as a result of a
REFER request or a 3xx response, the incoming
INVITE is routed according to the Request-URI. The
device identifies such INVITEs according to a
specific prefix in the Request-URI header,
configured by the SBCXferPrefix parameter.
Therefore, in this scenario, the device ignores the
parameter setting.
'SIP Connect'
sip-connect
[IPGroup_SIPConnect]
Defines the IP Group as representing multiple registering
servers, each of which may use a single registration, yet
represent multiple users. In addition, it defines how the
device saves registration information for REGISTER
messages received from the IP Group, in its registration
database. For requests routed to the IP Group's users,
the device replaces the Request-URI header with the
incoming To header (which contains the remote phone
number).
■ [0] No = (Default) Disables the SIP Connect feature.
No extra key based on source IP address is added to
the registration database and registration is done by
Contact and Address of Record (AoR).
■ [1] Yes = Enables the SIP Connect feature. For
initial registrations that are received from the IP
Group, the device attempts to add two keys
representing the user to its registration database:
✔ Key 1: The first key contains the incoming
REGISTER message's source IP address, port
(only if UDP), and SIP Interface ID (e.g.,
"10.33.3.3:5010#1").
✔ Key 2: The second key contains the incoming
REGISTER message's URI (user@host) of the
Contact header, source IP address, port (only if
UDP), and SIP Interface ID (e.g., "user-
@host.com#10.33.3.3:5010#1").
If the device receives an initial registration request
that has the same IP address and Contact URI, or IP
address only, as an existing key (i.e., an existing
registration), the device rejects the request.
- 372 -