Active Alarms And Troubleshooting - Polycom RealPresence RMX 1500 Administrator's Manual

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:
Active Alarms
Alarm Code
SIP TLS: Failed to load or verify
certificate files
SIP TLS: Registration transport error
SIP TLS: Registration handshake
failure
SIP TLS: Registration server not
responding
SIP TLS: Certificate has expired
Polycom®, Inc.
Appendix H - Deployment Into Microsoft Environments
Alarm Description
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
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.
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.
This alarm is displayed when the Collaboration Server does not receive a
response from the OCS to the registration request in the expected time
frame. Possible causes are:
• The Collaboration Server FQDN name is not defined in the OCS pool,
or is defined incorrectly.
• The time frame for the expected response was too short and it will be
updated with the next data refresh. The alarm may be cleared
automatically the next time the data is refreshed.
Alternatively, the OCS Pool Service can be stopped and restarted to
refresh the data.
• The Collaboration Server FQDN name is not defined in the DNS server.
Ping the DNS using the Collaboration Server FQDN name to ensure
that the Collaboration Server is correctly registered to the DNS.
The current TLS certificate files have expired and must be replaced with
new files.
1004