Filter
Top Products
Appendix A-Disconnection Causes
A-4
H323 call closed. Local
capability wasn't accepted
by remote
The endpoint did not accept the capabilities sent
by the gatekeeper.
H323 failure Internal error occurred.
H323 call closed. Remote
stop responding
The endpoint stopped responding.
H323 call closed. Master
slave problem
A People + Content cascading failure occurred.
SIP bad name The conference name is incompatible with SIP
standards.
SIP bad status A general IP card error occurred.
SIP busy everywhere The participant's endpoints were contacted
successfully, but the participant is busy and does
not wish to take the call at this time.
SIP busy here The participant's endpoint was contacted
successfully, but the participant is currently not
willing or able to take additional calls.
SIP capabilities don't
match
The remote device capabilities are not
compatible with the conference settings.
SIP card rejected channels The IP card could not open the media channels.
SIP client error 400 The endpoint sent a SIP Client Error 400 (Bad
Request) response.
The request could not be understood due to
malformed syntax.
SIP client error 402 The endpoint sent a SIP Client Error 402
(Payment Required) response.
SIP client error 405 The endpoint sent a SIP Client Error 405
(Method Not Allowed) response.
The method specified in the Request-Line is
understood, but not allowed for the address
identified by the Request-URI.
Table A-1 Call Disconnection Causes (Continued)
Disconnection Cause Description