Polycom RealPresence 2000, Administrator'S Manual

Page: 800 / 1130

RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide
23-18
Polycom, Inc.
For more information see " IP Network Service Definition” on page 1-66 .
Table 23-3 System Flags - SIP_TCP_KEEPALIVE_TYPE / BEHAVIOR
Flag Possible Flag Values
SIP_TCP_KEEPALIVE_TYPE
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_RESP
ONSE:
•
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