Conference rollover failed. Conference: '%1' MCU Type: '%2' Existing Mcu: '%3' Cause: Conference rollover occurs when an MCU becomes unavailable or is restarted. A rollover failure indicates that no MCU is available for the requested MCU type. Resolution: This operation will be automatically retried. This error can be ignored if MCU outage is planned. Otherwise ensure that at least one MCU for the specified type is available and that there are no connectivity issues between this server and the MCU.
Conference directory with ID "{0}" was deleted, but some unused stale conference data was left behind on the back-end server. ...
Conference directory with ID "{0}" was moved, but some stale conference data was left behind on the former service (DCOM ...
Conference directory with ID "{0}" will not be checked to see if it is safe to delete because the operation was invoked with ...
Conference escalation failed because the existing party did not join the conference. Additional participants cannot be added. ...
Conference rollover failed. Conference: '%1' MCU Type: '%2' Existing Mcu: '%3' Cause: Conference rollover occurs when an ...
Conference session could not recover from route set failure because its signaling session or subscription session is already ...
Conferencing Announcement Service configuration has changed. No Conferencing Announcement Service AOR currently available ...
Conferencing Announcement Service could not negotiate TLS and failed to establish a SIP connection. Reason=%1. Front End=%2. ...
Conferencing Announcement Service did not detect a private contact object. %1. Cause: Administration issues. Resolution: ...