19.08.2013 Views

RMX 2000 Administrator's Guide - Polycom Support

RMX 2000 Administrator's Guide - Polycom Support

RMX 2000 Administrator's Guide - Polycom Support

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Appendix A-Disconnection Causes<br />

A-4<br />

Table A-1 Call Disconnection Causes (Continued)<br />

Disconnection Cause Description<br />

H323 call closed. Local<br />

capability wasn't accepted<br />

by remote<br />

H323 failure Internal error occurred.<br />

H323 call closed. Remote<br />

stop responding<br />

H323 call closed. Master<br />

slave problem<br />

The endpoint did not accept the capabilities sent<br />

by the gatekeeper.<br />

The endpoint stopped responding.<br />

A People + Content cascading failure occurred.<br />

SIP bad name The conference name is incompatible with SIP<br />

standards.<br />

SIP bad status A general IP card error occurred.<br />

SIP busy everywhere The participant's endpoints were contacted<br />

successfully, but the participant is busy and does<br />

not wish to take the call at this time.<br />

SIP busy here The participant's endpoint was contacted<br />

successfully, but the participant is currently not<br />

willing or able to take additional calls.<br />

SIP capabilities don't<br />

match<br />

The remote device capabilities are not<br />

compatible with the conference settings.<br />

SIP card rejected channels The IP card could not open the media channels.<br />

SIP client error 400 The endpoint sent a SIP Client Error 400 (Bad<br />

Request) response.<br />

The request could not be understood due to<br />

malformed syntax.<br />

SIP client error 402 The endpoint sent a SIP Client Error 402<br />

(Payment Required) response.<br />

SIP client error 405 The endpoint sent a SIP Client Error 405<br />

(Method Not Allowed) response.<br />

The method specified in the Request-Line is<br />

understood, but not allowed for the address<br />

identified by the Request-URI.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!