AudioCodes Mediant 4000 SBC User Manual page 356

Parameter
Always Use Src Address
always-use-source-addr
[IPGroup_AlwaysUseSource
Addr]
SBC Advanced
Source URI Input
src-uri-input
[IPGroup_SourceUriInput]
Destination URI Input
dst-uri-input
User's Manual
Avaya's UCID value has the following format (in hexadecimal): 00 +
FA + 08 + node ID (2 bytes) + sequence number (2 bytes) +
timestamp (4 bytes)
This is interworked in to the SIP header as follows:
User-to-User: 00FA080019001038F725B3;encoding=hex
Note: To define the Network Node Identifier of the device for Avaya
UCID, use the 'Network Node ID' (NetworkNodeId) parameter.
Enables the device to always send SIP requests and responses, within
a SIP dialog, to the source IP address received in the previous SIP
message packet. This feature is especially useful in scenarios where
the IP Group endpoints are located behind a NAT firewall (and the
device is unable to identify this using its regular NAT mechanism).

[0] No = (Default) The device sends SIP requests according to the
settings of the global parameter, SIPNatDetection.

[1] Yes = The device sends SIP requests and responses to the
source IP address received in the previous SIP message packet.
For more information on NAT traversal, see ''Remote UA behind NAT''
on page 144.
Defines the SIP header in the incoming INVITE that is used for call
matching characteristics based on source URIs.

[-1] Not Configured (default)

[0] From

[1] To

[2] Request-URI

[3] P-Asserted - First Header

[4] P-Asserted - Second Header

[5] P-Preferred

[6] Route

[7] Diversion

[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, then 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.
Defines the SIP header in the incoming INVITE to use as a call
matching characteristic based on destination URIs. The parameter is
used for classification and routing purposes. The device first uses the
356
Mediant 4000 SBC
Description
Document #: LTRT-40203