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 C-CDR Fields - Unformatted File<br />

C-38<br />

Table C-18 Event Fields for Events 17, 23 - H323 PARTICIPANT CONNECTED,<br />

SIP PARTICIPANT CONNECTED (Continued)<br />

Field Description<br />

Secondary Cause Note: This field is only relevant if the Participant Status<br />

is Secondary.<br />

The cause for the secondary connection (not being able<br />

to connect the video channels), as follows:<br />

0 - Default.<br />

11 - The incoming video parameters are not compatible<br />

with the conference video parameters<br />

13 - The conference video settings are not compatible<br />

with the endpoint capabilities<br />

14 - The new conference settings are not compatible<br />

with the endpoint capabilities<br />

15 - Video stream violation due to incompatible annexes<br />

or other discrepancy<br />

16 - Inadequate video resources<br />

17 - When moved to a Transcoding or Video Switching<br />

conference, the participant’s video capabilities are not<br />

supported by the video cards<br />

18 - Video connection could not be established<br />

24 - The endpoint closed its video channels<br />

25 - The participant video settings are not compatible<br />

with the conference protocol<br />

26 - The endpoint could not re-open the video channel<br />

after the conference video mode was changed<br />

27 - The gatekeeper approved a lower bandwidth than<br />

requested<br />

28 - Video connection for the SIP participant is<br />

temporarily unavailable<br />

255 - Other

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

Saved successfully!

Ooh no, something went wrong!