AudioCodes Mediant 4000 SBC User Manual page 858

Parameter
configure voip > sip-definition
settings > ping-pong-keep-alive-
time
[PingPongKeepAliveTime]
Max Generated Register Rate
configure voip > sip-definition
settings > max-gen-reg-rate
[MaxGeneratedRegistersRate]
Generated Registers interval
gen-reg-int
[GeneratedRegistersInterval]
User's Manual

[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
(REGISTER messages) that the device sends (to a proxy or
registrar server) at a user-defined rate configured by the
GeneratedRegistersInterval parameter. The parameter is useful
in that it may be used to prevent an overload on the device's CPU
caused by sending many registration requests at a given time.
The valid value is 30 to 300 register requests per second. The
default is 150.
For configuration examples, see the description of the
GeneratedRegistersInterval parameter.
Defines the rate (in seconds) at which the device sends user
register requests (REGISTER messages). The parameter is
based on the maximum number of REGISTER messages that
can be sent at this rate, configured by the
MaxGeneratedRegistersRate parameter.
The valid value is 1 to 5. The default is 1.
Configuration examples:

If you configure the MaxGeneratedRegistersRate parameter to
100 and the GeneratedRegistersInterval to 5, the device
sends a maximum of 20 REGISTER messages per second
858
Mediant 4000 SBC
Description
Document #: LTRT-40203