Polycom RealPresence 800s Administrator's Manual page 561

Table B-1 Active Alarms (Continued)
Alarm Code
SIP TLS: Failed to load or verify certificate
files
SIP TLS: Registration handshake failure
SIP TLS: Registration server not
responding
SIP TLS: Registration transport error
Software upgrade in component
SSH is enabled
SWITCH not responding
System Cards MPM Plus mode are not
supported in Event mode
System configuration changed. Please
reset the MCU
System Configuration modified
System resources of Audio ports usage
has exceeded Port Gauge threshold
System resources of Video ports usage
has exceeded Port Gauge threshold
Polycom, Inc.
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 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.
•
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.
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
Check the Switch card.
System configuration flags were modified.
Reset the MCU.
Appendix B-Active Alarms
B-9