Справочник Пользователя для Polycom DOC2702A
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide
B-8
Polycom, Inc.
SIP TLS: Registration server not
responding
responding
This alarm is displayed when the MCU does not receive a response from the
OCS to the registration request in the expected time frame. Possible causes
are:
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.
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.
updated with the next data refresh. The alarm may be cleared
automatically the next time the data is refreshed.
•
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.
using the MCU FQDN name to ensure that the MCU is correctly registered
to the DNS.
SIP TLS: Registration transport error
This alarm indicates that the communication with the SIP server cannot be
established. Possible causes are:
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
SSH is enabled
SWITCH not responding
System Configuration modified
System configuration flags were modified.
Reset the MCU.
Reset the MCU.
Temperature Level - Critical
Possible explanations:
•
Temperature has reached a critical level. Card or if critical system element
the MCU will shut down.
the MCU will shut down.
Temperature Level - Major
Possible explanations:
•
Temperature has reached a problematic level and requires attention.
The software contains patch(es)
The software contains patch(es).
The system has been configured for Ultra
Secure Mode, but communication is not
secured until a TLS certificate is installed
and the MCU is set to Secured
Communication.
Secure Mode, but communication is not
secured until a TLS certificate is installed
and the MCU is set to Secured
Communication.
Although the System Flag ULTRA_SECURE_MODE is set to YES, the Ultra
Secure Mode is not fully implemented as the TLS certificate was not installed.
Please install the TLS certificate and set the MCU to Secured Communication
Mode to fully enable the Enhanced Security Environment.
Secure Mode is not fully implemented as the TLS certificate was not installed.
Please install the TLS certificate and set the MCU to Secured Communication
Mode to fully enable the Enhanced Security Environment.
User initiated MCU reset
MCU reset was initiated by a system user.
User Name "SUPPORT" cannot be used
in Ultra Secure Mode
in Ultra Secure Mode
When Ultra Secure Mode (ULTRA_SECURE_MODE=YES) is enabled, the
User Name "SUPPORT" cannot be used to define a new User.
User Name "SUPPORT" cannot be used to define a new User.
Version upgrade is in progress
Voltage problem
Possible reasons for the problem:
•
Card voltage problem.
•
Shelf voltage problem.
•
Voltage problem
Yellow Alarm
Table B-1
Alarms (Continued)
Alarm Code
Alarm Description