AudioCodes Mediant 800B User Manual page 790

Parameter
EMS: Ping Pong Keep Alive Time
[PingPongKeepAliveTime]
Web: Max Generated Register Rate
CLI: configure voip/sip-definition
proxy-and-registration/max-gen-reg-
rate
[MaxGeneratedRegistersRate]
User's Manual
Protocol (SIP)" for reliable, connection-orientated transport
types such as TCP.

[0] Disable (default)

[1] Enable
The SIP user agent/client (i.e., device) uses a simple periodic
message as a keep-alive mechanism to keep their flow to the
proxy or registrar alive (used for example, to keep NAT
bindings open). For connection-oriented transports such as
TCP/TLS this is based on CRLF. This mechanism uses a
client-to-server "ping" keep-alive and a corresponding server-
to-client "pong" message. This ping-pong sequence allows the
client, and optionally the server, to tell if its flow is still active
and useful for SIP traffic. If the client does not receive a pong
in response to its ping, it declares the flow "dead" and opens a
new flow in its place. In the CRLF Keep-Alive mechanism the
client periodically (defined by the PingPongKeepAliveTime
parameter) sends a double-CRLF (the "ping") then waits to
receive a single CRLF (the "pong"). If the client does not
receive a "pong" within an appropriate amount of time, it
considers the flow failed.
Note: The device sends a CRLF message to the Proxy Set
only if the Proxy Keep-Alive feature (EnableProxyKeepAlive
parameter) is enabled and its transport type is set to TCP or
TLS. The device first sends a SIP OPTION message to
establish the TCP/TLS connection and if it receives any SIP
response, it continues sending the CRLF keep-alive
sequences.
Defines the periodic interval (in seconds) after which a "ping"
(double-CRLF) keep-alive is sent to a proxy/registrar, using the
CRLF Keep-Alive mechanism.
The default range is 5 to 2,000,000. The default is 120.
The device uses the range of 80-100% of this user-defined
value as the actual interval. For example, if the parameter
value is set to 200 sec, the interval used is any random time
between 160 to 200 seconds. This prevents an "avalanche" of
keep-alive by multiple SIP UAs to a specific server.
Defines the maximum number of user register requests that the
device can send to a proxy (or registrar) server per second.
This feature is useful in that it can be used to prevent an
overload on the device's CPU caused by the sending of many
(for example, 1,000) registration requests to a proxy server at
any given time.
The valid value is 30 to 300 register requests per second. The
default is 100.
790
Mediant 800B Gateway and E-SBC
Description
Document #: LTRT-10286