Sip Tcp Keep-Alive - Polycom RealPresence RMX 1500 Administrator's Manual

SIP TCP Keep-Alive

In compliance with UC APL requirements, the NAT Keep Alive method has been enhanced according to
IETF RFC 5626 and For a full description of Keep Alive see IETF RFC 5626 and IETF RFC 6223.
Keep Alive behavior is defined for each IP Network Service and can be modified by adding the following
system flags and modifying their values according to System Flags: SIP_TCP_KEEP_ALIVE_TYPE /
BEHAVIOR. For more information see
System Flags - SIP_TCP_KEEP_ALIVE_TYPE / BEHAVIOR
Flag
SIP_TCP_KEEP_ALIVE_TYPE
SIP_TCP_KEEP_ALIVE_TYPE
Polycom®, Inc.
IP Network Services.
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 Ping 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 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
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 Ping response is expected
Ultra Secure Mode
836