Cisco Cisco TelePresence MCU 4510 Developer's Guide
Disconnect reasons
These are the possible values for disconnectReason:
Reason
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
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
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
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
was selected on the gatekeeper
gatekeeperRequiredButAbsent
No gatekeeper has been configured but MCU settings require that one be
present
present
h225DecodeError
Error decoding incoming H.225 message. For example the MCU was unable to
decode the incoming H.225 message
decode the incoming H.225 message
h225ProtocolError
There has been an H.225 protocol error. For example the endpoint has sent an
invalid H.255 message to the MCU
invalid H.255 message to the MCU
h225SocketError
There has been an error establishing a TCP connection to the H.225 socket on
the endpoint. For example there is no route to the desired IP address
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
decode the incoming H.245 message
h245ProtocolError
There has been an H.245 protocol error. For example, the endpoint has sent an
invalid H.245 message to the MCU
invalid H.245 message to the MCU
h245SocketError
There has been an error establishing a TCP connection to the H.245 socket on
the endpoint. For example, the endpoint is not listening on the H.245 port it had
previously specified
the endpoint. For example, the endpoint is not listening on the H.245 port it had
previously specified
incompatibleVncVersion
VNC version is incompatible with MCU. Check knowledge base for details of
supported versions
supported versions
localGatekeeperRefused
"The local gatekeeper refused the call. This maybe because the destination is
not registered to the gatekeeper, for example when dialling direct by IP
address"
not registered to the gatekeeper, for example when dialling direct by IP
address"
localTeardown
The MCU disconnected the call
messageQueueOverflow
An excess of information in the message buffer has caused it to run out of space
and overflow
and overflow
Cisco TelePresence MCU API 2.10
Page 185 of 296
Related information
Disconnect reasons