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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Appendix A<br />

Disconnection Causes<br />

If a participant was unable to connect to a conference or was disconnected<br />

from a conference, the Connection Status tab in the Participant Properties<br />

dialog box indicates the call disconnection cause. In some cases, a possible<br />

solution may be displayed.<br />

A video participant who is unable to connect the video channels, but is<br />

able to connect as an audio only participant, is referred to as a Secondary<br />

participant. For Secondary participants, the Connection Status tab in the<br />

Participant Properties dialog box indicates the video disconnection cause.<br />

In some cases, a possible solution may be indicated.<br />

The table below lists the call disconnection causes that can be displayed in<br />

the Call Disconnection Cause field and provides an explanation of each<br />

message<br />

IP Disconnection Causes.<br />

Table A-1 Call Disconnection Causes<br />

Disconnection Cause Description<br />

Disconnected by User The user disconnected the endpoint from the<br />

conference.<br />

Remote device did not<br />

open the encryption<br />

signaling channel<br />

Remote devices selected<br />

encryption algorithm does<br />

not match the local<br />

selected encryption<br />

algorithm<br />

The endpoint did not open the encryption<br />

signaling channel.<br />

The encryption algorithm selected by the<br />

endpoint does not match the MCU's encryption<br />

algorithm.<br />

A-1

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

Saved successfully!

Ooh no, something went wrong!