AudioCodes Mediant 4000 SBC User Manual page 857

User's Manual
Parameter
Add Empty Authorization Header
configure voip > sip-definition
settings > add-empty-author-hdr
[EmptyAuthorizationHeader]
Add initial Route Header
configure voip > sip-definition
proxy-and-registration > add-init-
rte-hdr
[InitialRouteHeader]
configure voip > sip-definition
settings > ping-pong-keep-alive
[UsePingPongKeepAlive]
Version 7.2
attempt to influence the expiration interval selected by the
Registrar. A UA requests the immediate removal of a binding
by specifying an expiration interval of "0" for that contact
address in a REGISTER request. UA's should support this
mechanism so that bindings can be removed before their
expiration interval has passed. Use of the "*" Contact header
field value allows a registering UA to remove all bindings
associated with an address-of-record (AOR) without knowing
their precise values.
Note: The REGISTER-specific Contact header field value of "*"
applies to all registrations, but it can only be used if the Expires
header field is present with a value of "0".
Enables the inclusion of the SIP Authorization header in initial
registration (REGISTER) requests sent by the device.

[0] Disable (default)

[1] Enable
The Authorization header carries the credentials of a user agent
(UA) in a request to a server. The sent REGISTER message
populates the Authorization header with the following parameters:

username - set to the value of the private user identity

realm - set to the domain name of the home network

uri - set to the SIP URI of the domain name of the home
network

nonce - set to an empty value

response - set to an empty value
For example:
Authorization: Digest
username=alice_private@home1.net,
realm="home1.net", nonce="",
response="e56131d19580cd833064787ecc"
Note: This registration header is according to the IMS 3GPP
TS24.229 and PKT-SP-24.220 specifications.
Enables the inclusion of the SIP Route header in initial
registration or re-registration (REGISTER) requests sent by the
device.

[0] Disable (default)

[1] Enable
When the device sends a REGISTER message, the Route
header includes either the Proxy's FQDN, or IP address and port
according to the configured Proxy Set, for example:
Route: <sip:10.10.10.10;lr;transport=udp>
or
Route: <sip: pcscf-
gm.ims.rr.com;lr;transport=udp>
Enables the use of the carriage-return and line-feed sequences
(CRLF) Keep-Alive mechanism, according to RFC 5626
"Managing Client-Initiated Connections in the Session Initiation
Protocol (SIP)" for reliable, connection-orientated transport types
such as TCP.
857
60. Configuration Parameters Reference
Description
Mediant 4000 SBC