Polycom RealPresence 4000 Administrator's Manual page 1056

Polycom® RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator's Guide
Table H-11
Alarm Code
SIP TLS: Registration transport
error
SIP TLS: Registration
handshake failure
SIP TLS: Registration server not
responding
SIP TLS: Certificate has expired
SIP TLS: Certificate is about to
expire
SIP TLS: Certificate subject
name is not valid or DNS failed
to resolve this name
H-76
New Active Alarms (Continued)
Alarm Description
This alarm indicates that the communication with the SIP server
cannot be established. Possible causes are:
•
•
•
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 RMX, preventing the Registration of the RMX
to the OCS.
This alarm is displayed when the RMX does not receive a
response from the OCS to the registration request in the
expected time frame. Possible causes are:
•
•
•
The current TLS certificate files have expired and must be
replaced with new files.
The current TLS certificate files will expire shortly and will have
to be replaced to ensure the communication with the OCS.
This alarm is displayed if the name of the RMX in the certificate
file is different from the FQDN name defined in the OCS.
Note:
Occasionally this alarm may be activated without real cause.
Resetting the MCU may clear the alarm.
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
The RMX 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 RMX FQDN name is not defined in the DNS server. Ping
the DNS using the RMX FQDN name to ensure that the RMX
is correctly registered to the DNS.
Polycom, Inc.