This article relates to the Cisco TelePresence MCU 4203, Cisco TelePresence MCU MSE 8420, Cisco TelePresence MCU 4505 and Cisco TelePresence MCU MSE 8510 products.
A. When a call ends, the reason for the disconnection is shown in the status column of the Previous Participants table in the Conference > Participants. The different reasons include:
Remote destination unavailable - The MCU received a reply indicating that H.323 calls cannot be established, for example, endpoint is switched off, if IP address was mis-typed or the MCU called to an address that cannot receive a H.323 call
DNS name lookup failed - The address typed was not registered to a gatekeeper, could not be dialed as an IP address and could not be found with a DNS lookup
Timeout error - No reply from the endpoint, for example if network problems prevented any messages reaching the endpoint from the MCU, or vice versa
No gatekeeper configured to resolve DN - The address could not be resolved as an IP address, but no gatekeeper is set on the Settings > Gatekeeper page to resolve the number into an E.164 address
Local Gatekeeper refused call - The gatekeeper that the MCU is registered to refused to let the call complete, for instance because it could not route the called number, it blocked the call for security reasons or because the gatekeeper did not respond.
Far End Gatekeeper refused call - The gatekeeper that the destination is registered to refused to let the call complete
Capability negotiation error - This is due to the MCU's capabilities being rejected, or the MCU not receiving a reply to its capability message. Check your endpoint is running the latest version, and that there is no network congestion that could stop messages reaching the MCU.
H.225 Network Connection Error - The MCU could not successfully negotiate the call with the endpoint. Check the network to find out if any firewalls or routers are not passing the initial TCP connection to port 1720 which is necessary to initiate a call
H.245 Network Connection Error - The MCU could not contact the endpoint during a call, for example because the network went down. If this reason is given during call set up, it means that the initial TCP connection to port 1720 succeeded, but the second TCP connection to a TCP ephemeral port failed. This is a network error, and messages in the event log will tell you the IP address and port that the MCU is trying to connect to
No answer- The endpoint started ringing, then sent no further messages back to the MCU
Call rejected - For example if an endpoint chose to reject an incoming call instead of answering
Call ended by remote party - The endpoint hung up a call that was in progress
MCU initiated disconnection - The MCU ended the call, for example if a user hung up the call via the web interface
Endpoint disconnected - This is a 'catch all' reason used when no extra information can be provided. This reason is also reported when some endpoints are busy