Polycom 1800 Security Camera User Manual


  Open as PDF
of 1183
 
RealPresence Collaboration Server (RMX) 1500/1800/2000/4000 Administrator’s Guide
Polycom®, Inc. 1047
Collaboration Server System Flag Configuration
Enabling the Microsoft Environment
The Collaboration Server can be installed in Microsoft R2 environments. To adjust the Collaboration Server
behavior to the Microsoft environment in each release, system flags must be set.
To configure the system flags on the Polycom Collaboration Server system:
1 On the Collaboration Server menu, click Setup > System Configuration.
The System Flags - MCMS_PARAMETERS_USER dialog box opens.
2 Scroll to the flag MS_ENVIRONMENT and click it.
The Edit Flag dialog box is displayed.
3 In the Value field, enter YES to set the Collaboration Server SIP environment to Microsoft solution.
4 Click OK to complete the flag definition.
5 When prompted, click Yes to reset the MCU and implement the changes to the system
configuration. After system reset the Collaboration Server can register to the OCS server and make
SIP calls.
In some configurations, the following flags may require modifications when MS_ENVIRONMENT flag is set
to YES:
Reset can be performed after setting the system flags (for example, setting the MS_ENVIRONMENT
flag). After system reset the Collaboration Server can register to the OCS server and make SIP calls.
Sometimes the system fails to read the *.pfx file and the conversion process fails, which is indicated
by the active alarm “SIP TLS: Registration server not responding” and/or “SIP TLS: Registration
handshake failure”. Sending *.pfx file again, as described in this procedure and then resetting the
system may resolve the problem.
Collaboration Server set to MS_ENVIRONMENT=YES supports SIP over TLS only and not over
TCP.
Sometimes the system fails to read the *.pfx file and the conversion process fails, which is indicated
by the active alarm “SIP TLS: Registration server not responding” and/or “SIP TLS: Registration
handshake failure”. Sending *.pfx file again, as described in this procedure and then resetting the
system may resolve the problem.