AudioCodes Mediant 800 MSBG - Page 128

SIP User's Manual 128 Document #: LTRT-12804
Mediant 800 MSBG
Parameter Description
sent to the next Proxy in the list. The same logic applies to
REGISTER messages (if RegistrarIP is not defined).
Notes:
 If EnableProxyKeepAlive is set to 1 or 2, the device monitors
the connection with the Proxies by using keep-alive messages
(OPTIONS or REGISTER).
 To use Proxy Redundancy, you must specify one or more
redundant Proxies.
 When a port number is specified (e.g., domain.com:5080),
DNS NAPTR/SRV queries aren't performed, even if
ProxyDNSQueryType is set to 1 or 2.
Transport Type
[ProxyIp_TransportType]
The transport type per Proxy server.
 [0] UDP
 [1] TCP
 [2] TLS
 [-1] = Undefined
Note: If no transport type is selected, the value of the global
parameter SIPTransportType is used (see ''Configuring SIP
General Parameters'' on page 130).
Web/EMS: Enable Proxy Keep
Alive
[ProxySet_EnableProxyKeepAl
ive]
Determines whether Keep-Alive with the Proxy is enabled or
disabled. This parameter is configured per Proxy Set.
 [0] Disable = Disable (default).
 [1] Using Options = Enables Keep-Alive with Proxy using SIP
OPTIONS messages.
 [2] Using Register = Enables Keep-Alive with Proxy using SIP
REGISTER messages.
If set to 'Using Options', the SIP OPTIONS message is sent every
user-defined interval (configured by the parameter
ProxyKeepAliveTime). If set to 'Using Register', the SIP
REGISTER message is sent every user-defined interval
(configured by the RegistrationTime parameter for the GW/IP2IP
application or by the SBCProxyRegistrationTime parameter for
SBC application). Any response from the Proxy, either success
(200 OK) or failure (4xx response) is considered as if the Proxy is
communicating correctly.
Notes:
 For Survivability mode for USER-type IP Groups, this
parameter must be enabled (1 or 2).
 This parameter must be set to 'Using Options' when Proxy
redundancy is used.
 When this parameter is set to 'Using Register', the homing
redundancy mode is disabled.
 When the active proxy doesn't respond to INVITE messages
sent by the device, the proxy is tagged as 'offline'. The
behavior is similar to a Keep-Alive (OPTIONS or REGISTER)
failure.
 If this parameter is enabled and the proxy uses the TCP/TLS
transport type, you can enable CRLF Keep-Alive mechanism,