19.08.2013 Views

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

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.

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

Disconnection Cause Description<br />

H323 call closed. Remote sent bad<br />

capability<br />

H323 call closed. Local capability wasn't<br />

accepted by remote<br />

H323 failure Internal error occurred.<br />

H323 call closed. Remote stop<br />

responding<br />

Appendix A-Disconnection Causes<br />

There was a problem in the capabilities sent by the<br />

endpoint.<br />

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

gatekeeper.<br />

The endpoint stopped responding.<br />

H323 call closed. Master slave problem 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 successfully,<br />

but the participant is busy and does not wish to take the<br />

call at this time.<br />

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

but the participant is currently not willing or able to take<br />

additional calls.<br />

SIP capabilities don't match The remote device capabilities are not compatible with<br />

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 Request)<br />

response.<br />

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

syntax.<br />

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

Required) response.<br />

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

Allowed) response.<br />

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

but not allowed for the address identified by the<br />

Request-URI.<br />

SIP client error 406 The endpoint sent a SIP Client Error 406 (Not<br />

Acceptable) resources.<br />

The remote endpoint cannot accept the call because it<br />

does not have the necessary responses. The resource<br />

identified by the request is only capable of generating<br />

response entities that have content characteristics not<br />

acceptable according to the Accept header field sent in<br />

the request.<br />

<strong>Polycom</strong>, Inc. A-3

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

Saved successfully!

Ooh no, something went wrong!