Polycom RMX 1500, DOC2702A manual Alarm Code Alarm Description

Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide

Table H-9New Active Alarms (Continued)

Alarm Code	Alarm Description
SIP TLS: Registration transport	This alarm indicates that the communication with the SIP server
error	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	This alarm indicates a mismatch between the security protocols
handshake failure	of the OCS and the MCU, preventing the Registration of the
	MCU to the OCS.
SIP TLS: Registration server not	This alarm is displayed when the MCU does not receive a
responding	response from the OCS to the registration request in the
	expected time frame. Possible causes are:
	• The MCU 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 MCU FQDN name is not defined in the DNS server. Ping
	the DNS using the MCU FQDN name to ensure that the MCU
	is correctly registered to the DNS.
SIP TLS: Certificate has expired	The current TLS certificate files have expired and must be
	replaced with new files.
SIP TLS: Certificate is about to	The current TLS certificate files will expire shortly and will have
expire	to be replaced to ensure the communication with the OCS.
SIP TLS: Certificate subject	This alarm is displayed if the name of the MCU in the certificate
name is not valid or DNS failed	file is different from the FQDN name defined in the OCS.
to resolve this name	Note:
	Occasionally this alarm may be activated without real cause.
	Resetting the MCU may clear the alarm.

H-68 Polycom, Inc.