Keep Alive Frequency - Polycom RealPresence 1500 Administrator's Manual

System Flags - SIP_TCP_KEEP_ALIVE_TYPE / BEHAVIOR
Flag
SIP_TCP_KEEP_ALIVE_TYPE
SIP_TCP_KEEP_ALIVE_TYPE
SIP_TCP_KEEP_ALIVE_BEHAVIOR

Keep Alive Frequency

The Keep Alive frequency is set by the SIP Server using the Via Header keep and Flow Timer fields of the
SIP Header.
Polycom®, Inc.
Possible Flag Values
NONE
• No Keep Alive messages are sent.
MS (Default when Microsoft SIP Server Type is selected for the Network
Service).
• Keep Alive messages are sent only after successful registration.
• A Pong response is not expected.
RFC5626
• In the SIP Header, the Flow-Timer Header Field is mandatory.
• Keep Alive messages are sent only after successful registration. A Pong
response is expected and if none is received, the value of the
SIP_TCP_KEEP_ALIVE_BEHAVIOR system flag is checked.
If its value is
DO_NOT_RE_REGISTRATION_WHEN_NO_PONG_RESPONSE:
 For a Register Dialog, a Reregister Message is sent. There is no
disconnection.
 For a Call Dialog, no further messages are sent. There is no
disconnection.
If its value is RE_REGISTRATION_WHEN_NO_PONG_RESPONSE:
 Both Register and Call Dialogs are disconnected.
RFC6223
• Behavior is the same as for RFC5626 with the following differences:
 In the SIP Header, the Via Header "keep" is mandatory.
 In the SIP Header, the Flow-Timer Header Field is optional.
PLCM (Default when Generic SIP Server Type is selected for the Network
Service).
• For Call and successful Register Dialogues:
 Two CR LF character sequences are sent
 No PONG response is expected
If the value of the System Flag, SIP_TCP_KEEP_ALIVE_TYPE=
RFC5626 or RFC6223 and no Pong is received, the value of this System
Flag is checked.
Possible Values:
• RE_REGISTRATION_WHEN_NO_PONG_RESPONSE
• DO_NOT_RE_REGISTRATION_WHEN_NO_PONG_RESPONSE
(Default)
For a full description see the description for the
SIP_TCP_KEEP_ALIVE_TYPE flag (above).
Ultra Secure Mode
822