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

Страница: 838 / 872

User's Manual 838 Document #: LTRT-89729
Mediant 3000
Parameter Description
INVITE) using one or more alternative URIs included in the 3xx
response. The device sends the new request to the alternative
destination according to the IP-to-IP Routing table (the 'Call
Trigger' field must be set to
3xx ).
Notes:

When this parameter is changed from 1 to 0, new 3xx Contact
headers remain unchanged. However, requests with the special
prefix continue using the device's database to locate the new
destination.

Only one database entry is supported for the same host, port, and
transport combination. For example, the following URLs cannot
be distinguished by the device:

sip:10.10.10.10:5060;transport=tcp;param=a

sip:10.10.10.10:5060;transport=tcp;param=b

The database entry expires two hours after the last use.

The maximum number of destinations (i.e., database entries) is
50.

This parameter can also be configured as an IP Profile.

For more information on SIP 3xx Redirect response handling, see
'Handling SIP 3xx Redirect Responses' on page
420 .
Web: Enforce Media Order
[SBCEnforceMediaOrder]
Enables the device to arrange media lines (‘m=’ line) in the SDP
offer according to the previous offer-answer exchange (RFC 3264).

[0] Disable

[1] Enable (default)
Web: Lifetime of the nonce in
seconds
[AuthNonceDuration]
Defines the lifetime (in seconds) that the current nonce is valid for
server-based authentication. The device challenges a message that
attempts to use a server nonce beyond this period. This parameter is
used to provide replay protection (i.e., ensures that old
communication streams are not used in replay attacks).
The valid value range is 30 to 600. The default is 300.
Web: Authentication
Challenge Method
[AuthChallengeMethod]
Defines the type of server-based authentication challenge.

[0] 0 = (Default) Send SIP 401 "Unauthorized" with a WWW-
Authenticate header as the authentication challenge response.

[1] 1 = Send SIP 407 "Proxy Authentication Required" with a
Proxy-Authenticate header as the authentication challenge
response.
Web: Authentication Quality
of Protection
[AuthQOP]
Defines the authentication and integrity level of quality of protection
(QoP) for digest authentication offered to the client. When the device
challenges a SIP request (e.g., INVITE), it sends a SIP 401 response
with the Proxy-Authenticate header or WWW-Authenticate header
containing the 'qop' parameter. The QoP offered in the 401 response
can be 'auth', 'auth-int', both 'auth' and 'auth-int', or the 'qop'
parameter can be omitted from the 401 response. In response to the
401, the client needs to send the device another INVITE with the
MD5 hash of the INVITE message and indicate the selected auth
type.

[0] 0 = The device sends 'qop=auth' in the SIP response,
requesting authentication (i.e., validates user by checking user
name and password). This option does not authenticate the
message body (i.e., SDP).

[1] 1 = The device sends 'qop=auth-int' in the SIP response,
indicating required authentication and authentication with integrity