Cisco Cisco TelePresence MCU 4510 Developer's Guide
Related information
Cisco TelePresence MCU API 2.9
Page 126 of 223
Reason
Description
Moved
The endpoint has moved to a different conference
networkError
There has been an unspecified network error
noAnswer
The endpoint started ringing but the call was not accepted by the user
noGatekeeperForDN
No gatekeeper has been found for dialed number. This can occur when
attempting a call to an invalid E164 number
attempting a call to an invalid E164 number
portAllocationExceeded
The number of available ports (both audio and video) on the MCU has been
exceeded
exceeded
protocolError
There has been an unspecified protocol error
q931DecodeError
Error decoding incoming Q.931 message. For example the MCU was unable to
decode the incoming Q.931 message
decode the incoming Q.931 message
q931ProtocolError
There has been a Q.931 protocol error. For example the endpoint has sent an
invalid Q.931 message to the MCU
invalid Q.931 message to the MCU
Rejected
The endpoint chose to reject an incoming call instead of answering
rejectedImmediately
The endpoint rejected the call without ringing
remoteGatekeeperRefused
The remote gatekeeper refused the call. This maybe because the MCU is not
registered to the the gatekeeper required by the endpoint
registered to the the gatekeeper required by the endpoint
remoteGatekeeperUnreachable The remote gatekeeper did not respond to the endpoint that the MCU was trying
to call
remoteGatewayResources
The remote gateway has insufficient resources to let the call complete. For
example the call is being routed to an ISDN gateway with insufficient channels
to allow the call to complete
example the call is being routed to an ISDN gateway with insufficient channels
to allow the call to complete
remoteTeardown
The endpoint disconnected the call
serviceUnavailable
The requested service is unavailable. This directly corresponds to an H.323 or
SIP message received from the far end to indicate that the call is unable to
proceed. The far end could have made this decision for any one of a number of
reasons, including lack of resource availability or a call routing policy that
prevents the MCU from calling the destination number
SIP message received from the far end to indicate that the call is unable to
proceed. The far end could have made this decision for any one of a number of
reasons, including lack of resource availability or a call routing policy that
prevents the MCU from calling the destination number
Timeout
Could not establish call due to network timeout
Unspecified
This is a "catch all" reason used when no extra information can be provided
unspecifiedError
This is a "catch all" reason used when no extra information can be provided
videoPortAllocationExceeded
The number of available video ports on the MCU has been exceeded
HTTP keep-alives
Note: This feature is available from API version 2.4 onwards.
Your application can use use HTTP keep-alives to reduce the amount of TCP traffic that results from
constantly polling the device. Any client which supports HTTP keep-alives may include the following line in
the HTTP header of an API request:
constantly polling the device. Any client which supports HTTP keep-alives may include the following line in
the HTTP header of an API request:
Connection: Keep-Alive