Version 6.8 273 Mediant 2600 E-SBC
User's Manual 17. Control Network
Parameter Description
mechanism using SIP REGISTER messages. The device
sends the REGISTER message every user-defined interval,
configured by the SBCProxyRegistrationTime parameter.
Any SIP response from the Proxy - success (200 OK) or
failure (4xx response) - is considered as if the Proxy is
"alive". If the Proxy does not respond to INVITE messages
sent by the device, the Proxy is considered as down (offline).
Notes:
Proxy keep-alive using REGISTER messages (Using
REGISTER option) is applicable only to the Parking
redundancy mode ('Redundancy Mode' parameter
configured to Parking).
For Survivability mode for User-type IP Groups, you must
enable this Proxy Keep-Alive feature.
If you enable this Proxy Keep-Alive feature and the proxy
uses the TCP/TLS transport type, you can enable CRLF
Keep-Alive feature, using the UsePingPongKeepAlive
parameter.
If you enable this Proxy Keep-Alive feature, the device can
operate with multiple proxy servers (addresses) for
redundancy and load balancing (see the 'Proxy Load
Balancing Method' parameter).
Web: Proxy Keep Alive Time
EMS: Keep Alive Time
CLI: voip-network proxy-set >
proxy-keep-alive-time
[ProxySet_ProxyKeepAliveTime]
Defines the interval (in seconds) between Keep-Alive messages
sent by the device when the Keep-Alive mechanism is enabled.
The valid range is 5 to 2,000,000. The default is 60.
Note: This parameter is applicable only if the 'Enable Proxy
Keep Alive' parameter is set to Using Options.
Web: Keep-Alive Failure
Responses
CLI: keepalive-fail-resp
[ProxySet_KeepAliveFailureRes
p]
Defines SIP response codes that if any is received in response
to a keep-alive message using SIP OPTIONS, the device
considers the Proxy as down.
Up to three response codes can be configured, where each
code is separated by a comma (e.g., 407,404). By default, no
responses are defined. If no responses are configured or
responses received are not those configured, the proxy is
considered "alive".
Note: The SIP 200 response code is not supported by this
feature.
Success Detection Retries
success-detect-retries
[ProxySet_SuccessDetectionRetrie
s]
Defines the minimum number of consecutive, successful keep-
alive messages that the device sends to an offline proxy, before
the device considers the proxy as being online.
The valid range is 1 to 10. The default is 1.
Note: The parameter is applicable only if the 'Proxy Keep-Alive'
parameter is set to Using Options.
Success Detection Interval
success-detect-int
[ProxySet_SuccessDetectionInterv
al]
Defines the interval (in seconds) between each keep-alive
retries (as configured by the 'Success Detection Retries'
parameter) that the device performs for offline proxies.
The valid range is 1 to 30. The default is 10.
Note: The parameter is applicable only if the 'Proxy Keep-Alive'
parameter is set to Using Options.
Failure Detection Retransmissions Defines the maximum number of UDP retransmissions that the
To Next Page
Loading...
