AudioCodes Mediant 800B User Manual page 377

User's Manual
Parameter
User Stickiness
sbc-user-stickiness
[IPGroup_SBCUserStickin
ess]
Version 7.2

[2] Registrations not Needed = The device adds users to its database
in active state.
Enables user "stickiness" (binding) to a specific registrar server. The
registrar server is one of the IP addresses of the Proxy Set associated
with this Server-type IP Group. This feature applies to users belonging
to a User-type IP Group that are routed to this destination Server-type IP
Group.

[0] Disable = After a successful initial registration of the user to a
registrar, whenever the device receives a SIP request or registration
refresh from the user, the device sends the request to whichever
registrar (IP address of the Proxy Set) is currently active. In the case
of proxy load-balancing, there is no certainty to which IP address the
request is routed.

[1] Enable = The device always routes SIP requests (INVITEs,
SUBSCRIBEs and REGISTER refreshes) received from the user to
the same registrar server to which the last successful REGISTER
request for that user was routed. In other words, once initial
registration of the user to one of the IP addresses of the Proxy Set
associated with this destination Server-type IP Group is successful
(i.e., 200 OK), binding occurs to this specific address (registrar) and
all future SIP requests from the user are routed (based on matched
routing rule) only to this specific registrar.
Note:

The parameter is applicable only to Server-type IP Groups.

The Proxy Set associated with the Server-type IP Group must be
configured with multiple IP addresses (or an FQDN that resolves into
multiple IP addresses).

This feature is also applicable to IP Group Sets (see Configuring IP
Group Sets on page 734). If a user is bound to a registrar associated
with this Server-type IP Group which also belongs to an IP Group
Set, IP Group Set logic of choosing an IP Group is ignored and
instead, the device always routes requests from this user to this
specific registrar.

A user's "stickiness" to a specific registrar ends upon the following
scenarios:

If you modify the Proxy Set.

If the Proxy Set is configured with an FQDN and a DNS
resolution refresh removes the IP address to which the user is
bound.

User registration expires or the user initiates an unregister
request.

The Proxy Set's Hot-Swap feature (for proxy redundancy) is not
supported for users that are already bound to a registrar. However,
you can achieve proxy "hot-swap" for failed initial (non-bounded)
REGISTER requests. If a failure response is received for the initial
REGISTER request and the response's code appears in the
Alternative Routing Reasons table (see Configuring SIP Response
Codes for Alternative Routing Reasons onn page 728), "hot-swap" to
the other IP addresses of the Proxy Set is done until a success
response is received from one of the addresses. In the case of failed
REGISTER refresh requests from users that are already bound to a
registrar, no "hot-swap" occurs for that request; only for subsequent
refresh requests.
377
Description
Mediant 800B Gateway & E-SBC
17. Control Network