AudioCodes Mediant 1000B User Manual page 386

Parameter
[Account_Register]
Contact User
contact-user
[Account_ContactUser]
Registrar Stickiness
registrar-stickiness
[Account_RegistrarStickiness]
User's Manual
Description
typically done for INVITE messages sent to the
"serving" IP Group. If the device receives a SIP 401
(Unauthorized) in response to a sent INVITE, the
device checks for a matching "serving" and "served"
entry in the table. If a matching row exists, the device
authenticates the INVITE by providing the
corresponding MD5 authentication username and
password to the "serving" IP Group.

[1] Regular = Regular registration process. For more
information, see ''Regular Registration Mode'' on page
388.

[2] GIN = Registration for legacy PBXs, using Global
Identification Number (GIN). For more information, see
''Single Registration for Multiple Phone Numbers using
GIN'' on page 389.
Note:

Gateway application: To enable registration, you also
need to set the 'Registration Mode' parameter to Per
Account in the Trunk Group Settings table (see
Configuring Trunk Group Settings on page 505).

The account registration is not affected by the
IsRegisterNeeded parameter.
Defines the AOR username. This appears in REGISTER
From/To headers as ContactUser@HostName, and in
INVITE/200 OK Contact headers as
ContactUser@<device's IP address>.
Note:

If the parameter is not configured, the 'Contact User'
parameter in the IP Groups table is used instead.

If registration fails, the user part in the INVITE Contact
header contains the source party number.
Enables the Registrar Stickiness feature, whereby the
device always routes SIP requests of a registered
Account to the same registrar server to where the last
successful REGISTER request was routed. In other
words, once initial registration of the Account to one of
the IP addresses in the Proxy Set (associated with the
Serving IP Group) is successful (i.e., 200 OK), binding
("stickiness") occurs to this specific address (registrar). All
future SIP requests (INVITEs, SUBSCRIBEs and
REGISTER refreshes) whose source and destination
match the Account are sent to this registrar only. This
applies until the registrar is unreachable or registration
refresh fails, for whatever reason.

[0] Disable = (Default) Disables the Registrar
Stickiness feature. After successful initial registration
of the Account with a registrar (IP address), whenever
the device receives a SIP request or registration
refresh, the device sends the request to whichever IP
address is the currently working registrar. In other
words, there is no binding to a specific IP address in
the Proxy Set and at any given time, requests may be
sent to a different IP address, whichever is the working
386
Mediant 1000B Gateway & E-SBC
Document #: LTRT-27055