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

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

CHAPTER 60 Configuration Parameters Reference
Mediant 4000 SBC | User's Manual
Parameter Description
■ [1] Enable = Rejects a CANCEL request received during the
INVITE transaction by sending a SIP 481 (Call/Transaction
Does Not Exist) response and maintains the call session.
configure voip >
sip-definition
settings >
verify-rcvd-
requri
[VerifyRecievedReque
stUri]
Enables the device to reject SIP requests (e.g., ACK, BYE, or re-
INVITE) whose user part in the Request-URI is different from the
user part in the Contact header of the last sent SIP request.
■ [0] = (Default) Disable. Even if the user part is different, the
device accepts the SIP request.
■ [1] = Enable. If the user part in the Contact header of the
previous SIP request is different to the user part in the Request-
URI for in-dialog requests, the device rejects the SIP request. A
BYE request is responded with a SIP 481, a re-INVITE request
is responded with a SIP 404, and an ACK request is ignored.
■ [2] = If the user part in the Contact header of the previous SIP
request is different to the user part in the Request-URI for dialog-
initiating INVITE requests, the device rejects the SIP request.
■ Verify dialog-initiating INVITE for all required conditions (Via,
Source IP and user in Request-URI)
■ [3] = Verify dialog-initiating INVITE and in-dialog requests.
The VerifyRecievedRequestUri parameter functions together with
the RegistrarProxySetID parameter, as follows:
■ Handling Dialog-Initiating INVITEs: If the
VerifyRecievedRequestUri parameter is configured to [2] or [3]
and the RegistrarProxySetID parameter is configured to some
Proxy Set, the device accepts dialog-initiating INVITE requests
received from the registrar at which the Accounts (configured in
the Accounts table) are registered. For dialog-initiating INVITE
requests received from the registrar on a specific SIP Interface,
the following rules apply (listed according to priority):
✔
The top-most Via header must contain a host-resolved IP
address of the registrar; otherwise, the device drops the
INVITE request.
✔
The source IP address must be the same as the IP address
of the registrar; otherwise, the device rejects the requests
and sends a SIP 403 (Forbidden) response to the registrar.
✔
The user part, specified in the Request-URI header, must be
identical to the Contact user part configured for the
associated Account, and the Account must be registered.
Otherwise, the device rejects the request with a SIP 404
(Not Found) response. If the RegistrarProxySetID
parameter is not configured or no Accounts are configured,
the device accepts the dialog-initiating INVITE request.
- 927 -