Filter
Top Products
Appendix H-Setting the RMX for Integration Into Microsoft OCS Environment
H-30
SIP TLS: Registration
handshake failure
This alarm indicates a mismatch between the
security protocols of the OCS and the RMX,
preventing the Registration of the RMX to the
OCS.
SIP TLS: Registration server not
responding
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 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.
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
expire
The current TLS certificate files will expire
shortly and will have to be replaced to ensure
the communication with the OCS.
SIP TLS: Certificate subject
name is not valid or DNS failed
to resolve this name
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.
Table H-2 New Active Alarms (Continued)
Alarm Code Alarm Description