AudioCodes Mediant 500L User Manual page 1057

Enterprise session border controller (e-sbc) & media gateway
Hide thumbs Also See for Mediant 500L:
Table of Contents

Advertisement

User's Manual
Parameter
User Name
configure voip > sip-definition
proxy-and-registration > user-
name-4-auth
[UserName]
Password
configure voip > sip-definition
proxy-and-registration >
password-4-auth
[Password]
Cnonce
configure voip > sip-definition
proxy-and-registration > cnonce-
4-auth
[Cnonce]
Challenge Caching Mode
configure voip > sip-
definition settings >
challenge-caching
[SIPChallengeCachingMode]
Version 7.2
[2] Server = Device's IP address is used in the From and To
headers in keep-alive OPTIONS messages.
Defines the username for registration and Basic/Digest
authentication with a Proxy/Registrar server.
By default, no value is defined.
Note:
The parameter is applicable only to the Gateway application.
The parameter is applicable only if single device registration is
used (i.e., the parameter AuthenticationMode is set to
authentication per gateway).
Analog interfaces: Instead of configuring the parameter, the
Authentication table can be used (see Authentication on page
613).
Defines the password for Basic/Digest authentication with a
Proxy/Registrar server. A single password is used for all device
ports.
The default is 'Default_Passwd'.
Note: Analog interfaces: Instead of configuring the parameter, the
Authentication table can be used (see Authentication on page
613).
Defines the Cnonce string used by the SIP server and client to
provide mutual authentication.
The value is free format, i.e., 'Cnonce = 0a4f113b'. The default is
'Default_Cnonce'.
Enables local caching of SIP message authorization challenges
from Proxy servers.
The device sends the first request to the Proxy without
authorization. The Proxy sends a 401/407 response with a
challenge for credentials. The device saves (caches) the
response for further uses. The device sends a new request with
the appropriate credentials. Subsequent requests to the Proxy
are automatically sent with credentials (calculated from the saved
challenge). If the Proxy doesn't accept the new request and
sends another challenge, the old challenge is replaced with the
new one. One of the benefits of the feature is that it may reduce
the number of SIP messages transmitted through the network.
[0] None = (Default) Challenges are not cached. Every new
request is sent without preliminary authorization. If the request
is challenged, a new request with authorization data is sent.
[1] INVITE Only = Challenges issued for INVITE requests are
cached. This prevents a mixture of REGISTER and INVITE
authorizations.
[2] Full = Caches all challenges from the proxies.
Note:
Challenge caching is used with all proxies and not only with
the active one.
For the Gateway application: The challenge can be cached
per endpoint or per Account.
1057
69. Configuration Parameters Reference
Description
Mediant 500L Gateway & E-SBC

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents