19.08.2013 Views

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Table B-1 Alarms (Continued)<br />

Alarm Code Alarm Description<br />

Security mode failed. Certificate not yet<br />

valid.<br />

Security mode failed. Error in certificate<br />

file.<br />

Appendix B-Alarms and Faults<br />

Single clock source No Backup clock could be established as only one span is connected to the<br />

system or, there is a synchronization failure with another span. This alarm can<br />

be cancelled by adding the appropriate flag is the system configuration.<br />

SIP registrations limit reached SIP registrations limit reached.<br />

SIP TLS: Certificate has expired The current TLS certificate files have expired and must be replaced with new<br />

files.<br />

SIP TLS: Certificate is about to expire The current TLS certificate files will expire shortly and will have to be replaced<br />

to ensure the communication with the OCS.<br />

SIP TLS: Certificate subject name is not<br />

valid or DNS failed to resolve this name<br />

SIP TLS: Failed to load or verify certificate<br />

files<br />

This alarm is displayed if the name of the <strong>RMX</strong> in the certificate file is different<br />

from the FQDN name defined in the OCS.<br />

This alarm indicates that the certificate files required for SIP TLS could not be<br />

loaded to the <strong>RMX</strong>. Possible causes are:<br />

• Incorrect certificate file name. Only files with the following names can be<br />

loaded to the system: rootCA.pem, pkey.pem, cert.pem and<br />

certPassword.txt<br />

• Wrong certificate file type. Only files of the following types can be loaded to<br />

the system: rootCA.pem, pkey.pem and cert.pem and certPassword.txt<br />

• The contents of the certificate file does not match the system parameters<br />

SIP TLS: Registration handshake failure This alarm indicates a mismatch between the security protocols of the OCS<br />

and the <strong>RMX</strong>, preventing the Registration of the <strong>RMX</strong> to the OCS.<br />

SIP TLS: Registration server not<br />

responding<br />

This alarm is displayed when the <strong>RMX</strong> does not receive a response from the<br />

OCS to the registration request in the expected time frame. Possible causes<br />

are:<br />

• The <strong>RMX</strong> FQDN name is not defined in the OCS pool, or is defined<br />

incorrectly.<br />

• The time frame for the expected response was too short and it will be<br />

updated with the next data refresh. The alarm may be cleared<br />

automatically the next time the data is refreshed.<br />

• The <strong>RMX</strong> FQDN name is not defined in the DNS server. Ping the DNS<br />

using the <strong>RMX</strong> FQDN name to ensure that the <strong>RMX</strong> is correctly registered<br />

to the DNS.<br />

SIP TLS: Registration transport error This alarm indicates that the communication with the SIP server cannot be<br />

established. Possible causes are:<br />

• Incorrect IP address of the SIP server<br />

• The SIP server listening port is other than the one defined in the system<br />

• The OCS services are stopped<br />

Smart Report found errors on hard disk Smart Report found errors on hard disk.<br />

<strong>Polycom</strong>, Inc. B-9

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!