Polycom RealPresence RMX 1500 Administrator's Manual page 831

Manually Added, Modified, Deleted System Flags
Flag
SIP_BFCP_DIAL_OUT_MODE
SIP_DUAL_DIRECTION_TCP_CO
N
SIP_ENABLE_FECC
SIP_FAST_UPDATE_INTERVAL_E
NV
SIP_FAST_UPDATE_INTERVAL_E
P
SIP_FORMAT_GW_HEADERS_FO
R_REDCOM
Polycom®, Inc.
Description
Controls BFCP's use of UDP and TCP protocols for dial-out SIP Client
connections according to its value:
• AUTO (Default)
If SIP Client supports UDP, TCP or UDP and TCP:
- BFCP/UDP is selected as Content sharing protocol.
• UDP
If SIP Client supports UDP or UDP and TCP:
- BFCP/UDP selected as Content sharing protocol.
If SIP Client supports TCP
- Cannot share Content.
• TCP
If SIP Client supports TCP or UDP and TCP
- BFCP/TCP selected as Content sharing protocol.
If SIP Client supports UDP
- Cannot share Content.
In environments set to integration with Microsoft, if set to YES the system
sends a new request on the same TCP connection (instead of opening a
new one).
By default, FECC support for SIP endpoints is enabled at the MCU level.
You can disable it by manually adding this flag and setting it to NO.
Default setting is 0 to prevent the Collaboration Server from automatically
sending an Intra request to all SIP endpoints.
Enter n (where n is any number of seconds other than 0) to let the
Collaboration Server automatically send an Intra request to all SIP
endpoints every n seconds.
It is recommended to set the flag to 0 and modify the frequency in which the
request is sent at the endpoint level (as defined in the next flag).
Default setting is 6 to let the Collaboration Server automatically send an
Intra request to Microsoft OC endpoints only, every 6 seconds.
Enter any other number of seconds to change the frequency in which the
Collaboration Server send the Intra request to Microsoft OC endpoints only.
Enter 0 to disable this behavior at the endpoint level (not recommended).
Controls whether the RMX adds special gateway prefix and postfix
characters to the user portion of the SIP URI expressed in the From and
Contact headers of SIP messages sent during calls involving Gateway
Services. The addition of these characters can result in call failures with
some SIP call servers. It is recommended to set this flag to YES whenever
the RMX is deployed such that it registers its conferences to a SIP call
server.
Range: YES, NO
Default: NO
System Configuration Flags
800