AudioCodes Mediant 500L MSBR

User's Manual 20. Control Network
Version 6.8 301 Mediant 500L MSBR
Parameter Description
Load balancing is only performed on Proxy servers that are
tagged as 'online'. All outgoing messages are equally distributed
across the list of IP addresses. REGISTER messages are also
distributed unless a RegistrarIP is configured. The IP addresses
list is refreshed according to ProxyIPListRefreshTime. If a
change in the order of the entries in the list occurs, all load
statistics are erased and balancing starts over again.
 [2] Random Weights = The outgoing requests are not
distributed equally among the Proxies. The weights are received
from the DNS server, using SRV records. The device sends the
requests in such a fashion that each Proxy receives a
percentage of the requests according to its' assigned weight. A
single FQDN should be configured as a Proxy IP address.
Random Weights Load Balancing is not used in the following
scenarios:

The Proxy Set includes more than one Proxy IP address.

The only Proxy defined is an IP address and not an FQDN.

SRV is not enabled (DNSQueryType).

The SRV response includes several records with a different
Priority value.
Web/EMS: Is Proxy Hot Swap
CLI: voip-network proxy-set >
is-proxy-hot-swap
[ProxySet_IsProxyHotSwap]
Enables the Proxy Hot-Swap redundancy mechanism, which
provides real-time switching from the primary Proxy server to
redundant Proxies when no response is received from the primary.
 [0] No (default)
 [1] Yes = The device sends the SIP INVITE/REGISTER
message to the first address (Proxy/Registrar server) listed in
the Proxy Set. If a SIP response is received and this response
code is defined in the 'Keep Alive Failure Response' parameter
(above), the device assumes the Proxy as down and sends the
message again; otherwise, the device assumes the proxy "alive"
and does not send the message again. Each time a defined
response code is received, the device re-sends the message.
This can occur until a user-defined maximum number of
retransmissions, configured by the HotSwapRtx parameter, after
which the device sends the same message to the next address
(redundant Proxy/Registrar), and so on. If there is no response
from any of the Proxies, the device goes through the address
list again until a "live" Proxy is located.
Web/EMS: Proxy Redundancy
Mode
CLI: voip-network proxy-set >
proxy-redundancy-mode
[ProxySet_ProxyRedundancy
Mode]
Determines whether the device switches from a redundant Proxy to
the primary Proxy when it becomes available again.
 [-1] Not configured = (Default) The global parameter,
ProxyRedundancyMode applies.
 [0]
Parking = The device continues operating with the redundant
(now active) Proxy until the next failure, after which it operates
with the next redundant Proxy.
 [1] Homing = The device always attempts to operate with the
primary Proxy. The device switches back to the primary Proxy
whenever it becomes available.
Notes:
 To enable this functionality, you must also enable the Proxy
Keep-Alive mechanism (using the 'Enable Proxy Keep Alive'
parameter).
 The Homing option can only be used if the 'Enable Proxy Keep
Alive' parameter is set to Using Options.