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

Create successful ePaper yourself

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

<strong>Polycom</strong> 1500/<strong>RMX</strong> <strong>2000</strong>/4000 Administrator’s <strong>Guide</strong><br />

Table C-2 CDR Event Types (Continued)<br />

Event Code Event Name Description<br />

28 SIP PRIVATE<br />

EXTENSIONS<br />

30 GATEKEEPER<br />

INFORMATION<br />

31 PARTICIPANT<br />

CONNECTION<br />

RATE<br />

32 EVENT NEW<br />

UNDEFINED<br />

PARTY<br />

CONTINUE IPV6<br />

ADDRESS<br />

33 PARTY CHAIR<br />

UPDATE<br />

100 USER<br />

TERMINATE<br />

CONFERENCE<br />

101 USER ADD<br />

PARTICIPANT<br />

102 USER DELETE<br />

PARTICIPANT<br />

Contains SIP Private Extensions information.<br />

For more information about the fields, see Table C-25, “Event<br />

Fields for Event 28 - SIP PRIVATE EXTENSIONS,” on<br />

page C-30.<br />

Contains the gatekeeper caller ID, which makes it possible to<br />

match the CDR in the gatekeeper and in the MCU.<br />

For more information about the fields, see Table C-26, “Event<br />

Fields for Event 30 - GATEKEEPER INFORMATION,” on<br />

page C-30.<br />

Information about the line rate of the participant connection.<br />

This event is added to the CDR file each time the endpoint<br />

changes its connection bit rate. For more information about the<br />

fields, see Table C-27, “Event fields for Event 31 -<br />

PARTICIPANT CONNECTION RATE,” on page C-30.<br />

Information about the IPv6 address of the participant’s<br />

endpoint.<br />

Participants connect to the conferences as standard<br />

participants and they are designated as chairpersons either by<br />

entering the chairperson password during the IVR session<br />

upon connection, or while participating in the conference using<br />

the appropriate DTM code.<br />

For more information about the fields, see see “Event fields for<br />

Event 33 - PARTY CHAIR UPDATE” on page C-31.<br />

A user terminated the conference.<br />

For more information about the fields, see Table C-30, “Event<br />

Fields for Event 100 - USER TERMINATE CONFERENCE,”<br />

on page C-31.<br />

A user added a participant to the conference during the<br />

conference.<br />

For more information about the fields, see Table C-14, “Event<br />

Fields for Events 10, 101, 105 - DEFINED PARTICIPANT,<br />

USER ADD PARTICIPANT, USER UPDATE PARTICIPANT,”<br />

on page C-20.<br />

A user deleted a participant from the conference.<br />

For more information about the fields, see Table C-31, “Event<br />

Fields for Events 102,103, 104 - USER DELETE<br />

PARTICIPANT, USER DISCONNECT PARTICIPANT, USER<br />

RECONNECT PARTICIPANT,” on page C-31.<br />

C-6 <strong>Polycom</strong>, Inc.

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

Saved successfully!

Ooh no, something went wrong!