AudioCodes Mediant 800B User Manual page 928

Parameter
Web: SBC Server Auth Mode
CLI: sbc-server-auth-mode
[SBCServerAuthMode]
Web: Lifetime of the nonce in
seconds
CLI: lifetime-of-nonce
[AuthNonceDuration]
Web: Authentication Challenge
Method
CLI: auth-chlng-mthd
[AuthChallengeMethod]
Web: Authentication Quality of
Protection
CLI: auth-qop
[AuthQOP]
User's Manual
answer exchange (RFC 3264).

[0] Disable (default)

[1] Enable
For example, assume a call (audio) has been established
between two endpoints and one endpoint wants to subsequently
send an image in the same call session. If this parameter is
enabled, the endpoint includes the previously negotiated media
type (i.e., audio) with the new negotiated media type (i.e.,
image) in its SDP offer:
v=0
o=bob 2890844730 2890844731 IN IP4
host.example.com
s=
c=IN IP4 host.example.com
t=0 0
m=audio 0 RTP/AVP 0
m=image 12345 udptl t38
If this parameter is disabled, the only 'm=' line included in the
SDP is the newly negotiated media (i.e., image).
Defines whether authentication of the SIP client is done locally
(by the device) or by a RADIUS server.

[0] (default) = Authentication is done by the device (locally).

[1] = Authentication is done by the RFC 5090 compliant
RADIUS server

[2] = Authentication is done according to the Draft Sterman-
aaa-sip-01 method.
Note: Currently, option [1] is not supported.
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.
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.
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,
928
Mediant 800B Gateway and E-SBC
Description
Document #: LTRT-10278