Call Detail Recording (CDR) is enabled, but no Monitoring database was found in the topology document. As a result, CDR data will not be captured. Component: %1 Cause: This typically occurs when the topology document does not contain a valid Monitoring database. Resolution: Add a valid Monitoring database to the topology document and associate it with this pool to ensure that CDR data is captured.
By resetting your Assigned Conference information you automatically create a new Meeting URL. Your old Meeting URL will no ...
Call admission control (CAC) is an optional component that manages the bandwidth used by unified communications traffic within ...
Call admission control (CAC), also known as WAN bandwidth management, helps to prevent poor quality of experience for users ...
Call cannot be established with specific destination uri because it is in a conversation that is already connected to a conference. ...
Call Detail Recording (CDR) is enabled, but no Monitoring database was found in the topology document. As a result, CDR data ...
Call Park Service definition is removed from topology configuration. The service will be running using the old topology configuration. ...
Call Park Service encountered an orbit with an unknown type. The orbit will be assigned default value 'CallPark'. Identity: ...
Call Park Service failed to establish a connection on the primary application endpoint. Conferencing Announcement Service ...
Call Park Service startup is pending as configuration database is not yet available. Cause: Possible local configuration ...