AudioCodes Mediant 4000 SBC, Руководство пользователя

Страница: 389 / 1037

CHAPTER 18 Core Entities
Mediant 4000 SBC | User's Manual
Parameter Description
■ 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'
dst-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
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.
- 356 -