Polycom realpresence 1800 Administrator's Manual page 836

You can use the same procedure to manually add flags in the CS_MODULE_PARAMETERS tab.
The CS System Flags
Flag
CS_ENABLE_EPC
H245_TUNNELING
H323_RAS_IPV6
H323_TIMERS_SET_INDEX
MS_UPDATE_CONTACT_REMOV
E
Polycom®, Inc.
Description
Add this flag with the value YES (default value is NO) to enable endpoints
that support People+Content and require a different signaling (for example,
FX endpoints) to receive Content.
For use in the Avaya Environment.
In the Avaya Environment, set the flag to YES to ensure that H.245 is
tunneled through H.225. Both H.245 and H.225 will use the same signaling
port.
Default: NO.
If the Collaboration Server is configured for IPv4 & IPv6 addressing, RAS
(Registration, Admission, and Status) messages are sent in both IPv4 and
IPv6 format. If the gatekeeper cannot operate in IPv6 addressing mode,
registration fails and endpoints cannot connect using the Collaboration
Server prefix.
In such cases this System Flag should be set to NO.
Default: YES
Enables or disables H.323 index timer according to standard or proprietary
H.323 protocol.
Possible values:
0 (Default) - Sets the H.323 index timer to Polycom proprietary.
1 - Sets the H.323 index timer based on the H.323 Standard
recommendation.
Note: For homologation and certification testing, this flag must be set to 1.
When the flag value is set to:
• YES - The Contact Header is removed from the UPDATE message that
is sent periodically to the endpoints.
This is required when the SIP Server Type field of the IP Network
Service is set as Microsoft. Removal of the Contact Header from the
UPDATE message is required specifically by OCS R2.
• NO - The Contact Header is included in the UPDATE message. This is
the system behavior when the SIP Server Type is set as Generic.
This is required when the Collaboration Server is configured to accept
calls from both Microsoft LYNC and Cisco CUCM as CUCM requires the
Contact Header.
System Configuration Flags
805