Cisco Cisco TelePresence MCU 4510 Developer's Guide
Participant disconnect reasons
Cisco TelePresence MCU API 2.8
Page 106 of 120
Participant disconnect reasons
These are the possible values of the “disconnectReason” field in participant information responses:
Value
Description
authenticationFailed
VNC authentication failed. Check username and password
Busy
The endpoint is in another call
capabilityNegotiationError
Unable to negotiate a common capability set between
endpoint and MCU. For example there is no video codec that
both sides support
destinationUnreachable
The destination endpoint could not be reached or did not
respond
disconnectAll
The MCU disconnected all calls. This occurs at the end of a
scheduled conference or a user initiates a disconnect all from
the web interface
dnsFailed
A DNS lookup has failed. This can occur when dialling by
DNS name
failedToConnectToServer
Unable to connect to VNC server. This can be due to a
network problem or if a VNC server is not listening on the
specified host
gatekeeperEnded
The gatekeeper ended the call
gatekeeperError
The gatekeeper refused to let the call complete or did not
respond
gatekeeperForced
The gatekeeper forced the call to disconnect. For example
the end call option was selected on the gatekeeper
gatekeeperRequiredButAbsent
No gatekeeper has been configured but MCU settings require
that one be present
h225DecodeError
Error decoding incoming H.225 message. For example the
MCU was unable to decode the incoming H.225 message
h225ProtocolError
There has been a H.225 protocol error. For example the
endpoint has sent an invalid H.255 message to the MCU
h225SocketError
There has been a error establishing a TCP connection to the
H.225 socket on the endpoint. For example there is no route
to the desired IP address
h245DecodeError
Error decoding incoming H.245 message. For example the
MCU was unable to decode the incoming H.245 message
h245ProtocolError
There has been a H.225 protocol error. For example the
endpoint has sent an invalid H.255 message to the MCU