User's Manual 888 Document #: LTRT-89730
Mediant 3000
Parameter Description
the entire device. This is typically used for and digital modules.
Note: The parameter is applicable only to the Gateway application.
Set Out-Of-Service On
Registration Failure
[OOSOnRegistrationFail]
Enables setting the , trunk, or entire device (i.e., all endpoints) to out-of-
service if registration fails.
ï‚§ [0] Disable (default)
ï‚§ [1] Enable
If the registration is per endpoint (i.e., AuthenticationMode is set to 0) or
per Account (see Configuring Trunk Group Settings on page 463) and a
specific endpoint/Account registration fails (SIP 4xx or no response),
then that endpoint is set to out-of-service until a success response is
received in a subsequent registration request. When the registration is
per the entire device (i.e., AuthenticationMode is set to 1) and
registration fails, all endpoints are set to out-of-service. If all the
Accounts of a specific Trunk Group fail registration and if the Trunk
Group comprises a complete trunk, then the entire trunk is set to out-of-
service.
Note: The parameter is applicable only to the Gateway application.
[UnregistrationMode]
Enables the device to perform explicit unregisters.
ï‚§ [0] Disable (default)
ï‚§ [1] Enable = The device sends an asterisk ("*") value in the SIP
Contact header, instructing the Registrar server to remove all
previous registration bindings. The device removes SIP User Agent
(UA) registration bindings in a Registrar, according to RFC 3261.
Registrations are soft state and expire unless refreshed, but they can
also be explicitly removed. A client can 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".
Add Empty Authorization
Header
[EmptyAuthorizationHead
er]
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,