Appendix G-Setting the Collaboration Server for Integration Into Microsoft Environment
Polycom, Inc. G-33

Troubleshooting

• At the end of the installation and configuration process, to test the solution and the
integration with the OCS, create an ongoing conference with two participants, one dial-
in and one dial-out and connect them to the conference.
•If the active Alarm “SIP TLS: Registration server not responding” is displayed, stop and
restart the OCS Pool Service.
• If the communication between the OCS and the Collaboration Server cannot be
established, one of the possible causes can be that the Collaboration Server FQDN name
is defined differently in the DNS, OCS and Collaboration Server. The name must be
defined identically in all three devices, and defined as type A in the DNS. The definition
of the Collaboration Server FQDN name in the DNS can be tested by pinging it and
receiving the Collaboration Server signaling IP from the DNS in return.
• The communication between the OCS and the Collaboration Server can be checked in
the Logger files:
—SIP 401/407 reject messages indicate that the Collaboration Server is not
configured as Trusted in the OCS and must be configured accordingly.
—SIP 404 reject indication indicates that the connection to the OCS was established
successfully.
SIP TLS: Registration server not
responding
This alarm is displayed when the Collaboration Server does not
receive a response from the OCS to the registration request in
the expected time frame. Possible causes are:
•The Collaboration Server 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 Collaboration Server FQDN name is not defined in the
DNS server. Ping the DNS using the Collaboration Server
FQDN name to ensure that the Collaboration Server 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 Collaboration Server 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 G-7 New Active Alarms (Continued)
Alarm Code Alarm Description