User's Manual 1062 Document #: LTRT-10532
Mediant 500L Gateway & E-SBC
Parameter Description
configure voip > sip-definition
settings > authentication-mode
[AuthenticationMode]
[0] Per Endpoint = Registration and authentication is
performed separately for each endpoint/B-channel. This is
typically used for FXS interfaces, where each endpoint
registers (and authenticates) separately with its user name
and password.
[1] Per Gateway = (Default) Single registration and
authentication for the entire device. This is typically used for
FXO interfaces and digital modules.
[3] Per FXS = Registration and authentication for FXS
endpoints.
.
Note: The parameter is applicable only to the Gateway
application.
Set Out-Of-Service On
Registration Failure
configure voip > sip-definition
proxy-and-registration > set-oos-
on-reg-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 503
) 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.
The out-of-service method is configured using the
FXSOOSBehavior parameter.
configure voip > sip-definition
settings > expl-un-reg
[UnregistrationMode]
Enables the device to perform explicit unregisters.
[0] Disable (default)
[1] Enable = The device sends an asterisk ("*") value in the
SIP C
ontact 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".