Filter
Top Products
Appendix B-Alarms and Faults
Polycom, Inc. B-5
Gatekeeper failure (cont.)
• Gatekeeper rejected RRQ due to invalid terminal alias.
• Gatekeeper rejected RRQ due to resource unavailability.
• Gatekeeper rejected RRQ due to Security Denial.
• Gatekeeper rejected RRQ due to terminal type.
• Gatekeeper rejected RRQ due to unsupported Additive Registration.
• Gatekeeper rejected RRQ due to unsupported feature.
• Gatekeeper rejected RRQ due to unsupported QOS transport.
• Gatekeeper rejected RRQ due to unsupported transport.
• Gatekeeper rejected RRQ. Full registration required.
• Gatekeeper rejected RRQ. Reason 18.
• Gatekeeper Unregistration State.
• Registration succeeded.
GUI System configuration file is invalid
xml file
The XML format of the system configuration file that contains the user interface
settings is invalid.
Hard disk error Hard disk not responding.
Insufficient resources Insufficient resources.
Insufficient UDP Ports
Internal System configuration during
startup
System configuration during startup.
Invalid System Configuration
IP addresses of Signaling Host and
Control Unit are the same
IP Network Service configuration modified IP Network Service was modified.
Reset the MCU.
IP Network Service deleted IP Network Service was deleted.
Reset the MCU.
IP Network Service not found Possible explanations:
• IP Service not found in the Network Services list.
• m_StatusRead IpServiceList.
ISDN/PSTN Network Services
configuration changed
License not found
Management Network not configured
Missing Central Signaling configuration
MPL startup failure. Authentication not
received.
Table B-1 Alarms (Continued)
Alarm Code Alarm Description