Active Alarms And Troubleshooting - Polycom realpresence 1800 Administrator's Manual

The Master AVMCU participant will have a chairperson icon (
Server conference participants screen.
Since chairperson password is not supported in Microsoft Outlook, it is bypassed by exploiting the fact, that
the Collaboration Server does not request a chairperson password if the conference password was entered.
Therefore, the DMA generates a conference password, and uses this password when calling all the
participants in the conference, which in turn use it to connect the conference, without the chairperson
password being required.
All ContentConnect (Polycom content sharing for Microsoft environments) related actions
begin only after the Collaboration was moved from the AVMCU lobby into the conference.

Active Alarms and Troubleshooting

Active Alarms
The following active alarms may be displayed in the Collaboration Server System Alerts pane when the
Collaboration Server is configured for integration in the OCS environment:
Active Alarms
Alarm Code
SIP TLS: Failed to load or verify
certificate files
SIP TLS: Registration transport error
SIP TLS: Registration handshake
failure
Polycom®, Inc.
Appendix H - Deployment Into Microsoft Environments
Alarm Description
This alarm indicates that the certificate files required for SIP TLS could not
be loaded to the Collaboration Server. Possible causes are:
• Incorrect certificate file name. Only files with the following names can be
loaded to the system: rootCA.pem, pkey.pem, cert.pem and
certPassword.txt
• Wrong certificate file type. Only files of the following types can be loaded
to the system: rootCA.pem, pkey.pem and cert.pem and
certPassword.txt
• The contents of the certificate file does not match the system
parameters
This alarm indicates that the communication with the SIP server 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.
This alarm indicates a mismatch between the security protocols of the
OCS and the Collaboration Server, preventing the Registration of the
Collaboration Server to the OCS.
) attached to its name in the Collaboration
1016