from the Content and FECC channels in until the Collaboration Server sends out the first of the FW NAT
Keep Alive messages 30 seconds after the call starts.
If Content or FECC are required within the first 30 seconds of a call the FW NAT Keep Alive Interval should
be modified to a lower value.
To enable and modify FW NAT Keep Alive:
FW NAT Keep Alive is enabled in the New Profile - Advanced dialog box.
» Select the FW NAT Keep Alive check box and if required, modify the Interval field within the range
of 5 - 86400 seconds.
System Configuration in SBC environments
In an environment that includes SAM (a Polycom SBC), to ensure that a RealPresence Mobile endpoint can
send content to a conference the value of the system flag
NUM_OF_INITIATE_HELLO_MESSAGE_IN_CALL_ESTABLISHMENT must be set to at least 3.
For more details on modifying the values of system flags, see
SIP TCP Keep-Alive
SIP TCP Keep Alive behavior is defined for each IP Network Service and can be modified by adding the
following System Flags and modifying their values:
● SIP_TCP_KEEP_ALIVE_TYPE
● SIP_TCP_KEEP_ALIVE_BEHAVIOR
Polycom®, Inc.
Modifying System
Flags.
Network Security
572