User's Manual 354 Document #: LTRT-89730
Mediant 3000
Parameter Description
ï‚§
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.
Destination URI Input
[IPGroup_DestUriInput]
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 parameter’s
settings as a matching characteristic (input) to classify the incoming
INVITE to an IP Group (source IP Group) in the Classification table.
Once classified, the device uses the parameter for routing the call. For
example, if set to To, the URI in the To header of the incoming INVITE is
used as a matching characteristic for classifying the call to an IP Group
in the Classification table. Once classified, the device uses the URI in the
To header as the destination.
ï‚§ [-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
Notes:
ï‚§ 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.