Table of Contents
Advertisement
Alert 6102
Conference <VMR> on MCU <MCU> failed to start: <reason>.
A conference using the conference room identifier <VMR> has failed to start for the specified reason. If no
MCU was selected, <MCU> is "unresolved". This alert automatically clears after two minutes.
Click the link to go to the Network > Users page to find the specified VMR number and begin
troubleshooting.
See also:
Alerts
Alert 6103
Ongoing conference <VMR> on MCU <MCU> failed: <reason>.
A conference using the conference room identifier <VMR> has been aborted for the specified reason. This
alert automatically clears after two minutes.
Click the link to go to the Network > Users page to find the specified VMR number and begin
troubleshooting.
See also:
Alerts
Alert 6104
Ongoing conference <VMR> on MCU <MCU1> failed over to MCU <MCU2>: <reason>.
A conference using the conference room identifier <VMR> has been moved from <MCU1> to <MCU2> for
the specified reason. This alert automatically clears after two minutes.
Click the link to go to the Network > Users page to find the specified VMR number and begin
troubleshooting.
See also:
Alerts
Lync Presence Publishing
The following alerts provide information on problems the system may encounter when publishing presence
for Polycom conference contacts.
Alert 6201
Cluster <cluster>: Errors in presence publication for Lync server <lyncserver>. Presence
for <NN> of <MM> Polycom conference contacts will not be published due to Lync server
configuration 'MaxEndpointExpiration' value <expire>.
The system was unable to publish presence status for the specified number of Polycom conference contacts
because the Lync server has been configured with a maximum endpoint logon period of <expire> seconds.
To publish presence status for Polycom conference contacts, the RealPresence DMA system registers each
contact with the Lync server every 'MaxEndpointExpiration' seconds. Depending on how many conference
Polycom, Inc.
System Management and Maintenance
375
Advertisement
Table of Contents
