A server did not respond to HTTP request Server %1 did not respond to HTTP request %2 targeted at %3. Cause: Server might be down or the network path between servers might not be properly configured. Resolution: Please ensure that the server can be connected on the target port using telnet and then re-try.
A request received a final response but timed-out without the response being sent out. Application Uri: '%1' Cause: Possible ...
A request to create a conference was rejected because the system health level has reached a degraded state. Health State: ...
A request was redirected to another Audio/Video Edge Server. ClientID %1 Cause: Lack of resources for allocation. Resolution: ...
A Server connection has started throttling A Server connection from Web Conferencing Server with FQDN %1 has entered throttling ...
A server did not respond to HTTP request Server %1 did not respond to HTTP request %2 targeted at %3. Cause: Server might ...
A server is displayed in the list if there are at least 30 calls going over the server and the poor quality call percentage ...
A significant number of authentication or authorization failures have occurred on messages for the account %1 and the first ...
A significant number of connection failures have occurred with remote server %2 IP %1. There have been %3 failures in the ...
A significant number of DNS queries have been requested by user %1. There have been %2 queries in the last %3 minutes. There ...