Filter
Top Products
Polycom® RealPresence Collaboration ServerVirtual Edition Administrator’s Guide
G-32 Polycom, Inc.
Active Alarms and Troubleshooting
Active Alarms
The following active alarms may be displayed in the Collaboration Server System Alerts
pane when the Collaboration Server is configured for integration in the OCS environment:
Table G-7 New Active Alarms
Alarm Code Alarm Description
SIP TLS: Failed to load or verify
certificate files
This alarm indicates that the certificate files required for SIP TLS
could not be loaded to the Collaboration Server. Possible causes
are:
• Incorrect certificate file name. Only files with the following
names can be loaded to the system: rootCA.pem, pkey.pem,
cert.pem and certPassword.txt
• Wrong certificate file type. Only files of the following types
can be loaded to the system: rootCA.pem, pkey.pem and
cert.pem and certPassword.txt
• The contents of the certificate file does not match the system
parameters
SIP TLS: Registration transport
error
This alarm indicates that the communication with the SIP server
cannot be established. Possible causes are:
• Incorrect IP address of the SIP server
• The SIP server listening port is other than the one defined in
the system
• The OCS services are stopped
Note:
Sometimes this alarm may be activated without real cause.
Resetting the MCU may clear the alarm.
SIP TLS: Registration
handshake failure
This alarm indicates a mismatch between the security protocols
of the OCS and the Collaboration Server, preventing the
Registration of the Collaboration Server to the OCS.