Polycom realpresence 1800 Administrator's Manual page 831

The MCMS System Flags
Flag
SIP_TCP_KEEP_ALIVE_TYPE
SIP_TCP_KEEP_ALIVE_BEHAVIO
R
Polycom®, Inc.
Description
Possible Flag Values: 0, 1, 2, 3, 4
0 (NONE)
• No Keep Alive messages are sent.
1 (MS) (Default when Microsoft SIP Server Type is selected for the
Network
Service).
• Keep Alive messages are sent only after successful
registration.
• A Ping response is not expected.
2 (RFC5626)
• In the SIP Header, the Flow-Timer Header Field is mandatory.
• Keep Alive messages are sent only after successful
registration. A Ping 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 0:
 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 1:
 Both Register and Call Dialogs are disconnected.
3 (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.
4 (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 Ping response is expected
If the value of the System Flag, SIP_TCP_KEEP_ALIVE_TYPE=2
or 3 and no Ping is received, the value of this System Flag is
checked.
Possible Flag Values 0, 1:
• 0 (RE_REGISTRATION_WHEN_NO_PONG_RESPONSE)
• 1 (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).
System Configuration Flags
Add?


800