Related Manuals for Cisco TELEPRESENCE CALL DETAIL RECORDS FILE FORMAT
Summary of Contents for Cisco TELEPRESENCE CALL DETAIL RECORDS FILE FORMAT
- Page 1 Cisco TelePresence Call Detail Records File Format Reference Guide D14663.03 November 2010...
-
Page 2: Table Of Contents
Contents Contents Introduction ......................... 3 Overview of CDR file formats ........................3 How to use this reference guide ......................4 MCUs ............................ 5 Example CDR file: MCU 4200 Series/MCU 4500 Series/MCU MSE blades .......... 5 MCU and MCU MSE blade CDR event types ..................6 scheduled_conference_started ...................... -
Page 3: Introduction
Introduction Introduction Call Detail Records (CDRs) are used by Cisco TelePresence products for auditing and billing purposes. The following Cisco TelePresence products are able to generate CDRs: MCUs: MCU 4200 Series, MCU 4500 Series, MCU MSE 8420 and the MCU MSE 8510. ... -
Page 4: How To Use This Reference Guide
Introduction How to use this reference guide For each product type the following information is provided: Example exported CDR file in XML. Summary of reported event types. Details of the parameters for each event type. The section on MCU CDRs starts on page 5. The section on ISDN gateway CDRs starts on page 11. -
Page 5: Mcus
MCUs MCUs Example CDR file: MCU 4200 Series/MCU 4500 Series/MCU MSE blades The exported file has the name cdr_log.xml. You can change the filename if necessary. Below is a short extract showing each event type on the MCU or MCU MSE blade. <?xml version="1.0"... -
Page 6: Mcu And Mcu Mse Blade Cdr Event Types
MCUs MCU and MCU MSE blade CDR event types Currently the MCU and MCU MSE blade CDRs support the event types listed in the table below. They are listed in the order that they occur in the CDR. Event type Description scheduled_conference_started A scheduled conference was started. -
Page 7: Ad-Hoc_Conference_Started
MCUs Section Name Description created the conference <end> scheduled_date End date of the conference in the format dd Month yyyy unless this is a permanent conference in which case the end date is not included scheduled_time Either the time in the format hh:mm:ss or permanent. -
Page 8: Participant_Joined
MCUs participant_joined This event is seen whenever a participant joins a conference. Section Name Description The unique identifier in the format nnnnnnnn for <conference> unique_id the conference seen in the scheduled_conference_started ad-hoc_conference_started events name For scheduled conferences, the conference name as allocated by the user and, for ad hoc conferences, a name allocated by the unit <participant>... -
Page 9: Conference_Finished
MCUs Section Name Description <media_from_endpoint> resolution The highest resolution sent to or received from the participant’s endpoint during the course of its conference participation in the format n x n, for example "704 x 576" video_codec One of: Null H.261 Motion JPEG MPEG2 system stream raw... - Page 10 MCUs Section Name Description audio_only_participants The maximum number of audio-only participants that were allowed on this conference. This limit can either be explicitly set by the conference owner or will be the maximum number of participants that the MCU supports Either 1 (allowed) or 0 (not allowed) streaming_participants_allowed <participants>...
-
Page 11: Isdn Gateways
<event index="4" date="17 March 2010" time="17:10:07" type="multiway_call_transfer"> <connection unique_id="1200001" /> <call duration="30 sec" duration_in_minutes="1" disconnect_reason="call transferred to multiway destination" new_called_number="0175300009@tandberg.com" /> <bandwidth max_bandwidth="512 kbit/s" downspeeded="no" /> <h323_endpoint_details ip_address="10.2.160.3" dn="1119" h323_alias="sam.spade.t@tandberg.com" /> <media_from_isdn resolution="116 x 105" video_codec="unknown" audio_codec="unknown" bandwidth="116 bit/s" />... - Page 12 2010" time="17:10:32" type="connection_finished"> <connection unique_id="1200001" /> <call duration="55 sec" duration_in_minutes="1" disconnect_reason="participant ended call" /> <bandwidth max_bandwidth="512 kbit/s" downspeeded="no" /> <h323_endpoint_details ip_address="10.2.160.3" dn="0175300009@tandberg.com" h323_alias="multiway" /> <media_from_isdn resolution="1280 x 768" video_codec="H.264" audio_codec="G.711a" bandwidth="64000 bit/s" /> <media_to_isdn resolution="1280 x 768" video_codec="H.264" audio_codec="G.711a" bandwidth="64000 bit/s" />...
-
Page 13: Isdn Gateway Event Types
ISDN gateways ISDN gateway event types Currently the ISDN gateway CDRs support the event types listed in the table below. They are listed in the order that they occur in the CDR. Event type Description new_connection A new connection is initiated connection_proceeding Appears whenever: - the call has been connected... -
Page 14: Connection_Proceeding
ISDN gateways connection_proceeding This event is seen during a call. Section Name Description <connection> unique_id The same unique identifier for the connection as provided in the previous new_connection event in the format nnnnnnnn <call> via_auto_attendant Whether or not the connection was set up via the auto attendant. -
Page 15: Connection_Finished
ISDN gateways Section Name Description <media_from_isdn> resolution This is the highest resolution sent to or received from that endpoint during the course of the connection in and/or the format "n x n" (e.g. "704 x 576") <media_to_isdn> video_codec One of: Null H.261 H.263... - Page 16 ISDN gateways Section Name Description <h323_endpoint_details> ip_address The endpoint’s IP address Either <none> or the IP endpoint's E.164 number h323_alias The IP endpoint’s configured endpoint name <media_from_isdn> resolution This is the highest resolution sent to or received from that endpoint during the course of the and/or connection in the format "n x n"...
-
Page 17: Ip Gateways
IP gateways IP gateways Example CDR file: IP GW 3500 Series and IP GW MSE 8350 The exported file has the name cdr_log.xml. You can change this if necessary. The following is an extract showing each event type on the IP gateway unit or blade. <?xml version="1.0"... - Page 18 IP gateways <target called_number="10.2.161.253" protocol="h323" gateway="" gatekeeper=""> </target> <screening screened="yes"> </screening> </event> <event index="102411" date="17 September 2010" time="11:26:13" type="call_rejected"> <connection unique_id="27004"> </connection> <target disconnect_reason="participant ended call"> </target> </event> <event index="102412" date="17 September 2010" time="11:26:19" type="connection_finished"> <connection unique_id="27004" duration="2 mins 46 sec"...
-
Page 19: Ip Gateway Event Types
IP gateways IP gateway event types Currently the IP gateway CDRs support the event types listed in the table below. They are listed in the order that they occur in the CDR. Event type Description incoming_connection An endpoint has dialed in to the IP gateway and a connection is initiated call_operator An endpoint has dialed in to the IP gateway and the call is connected to the operator... -
Page 20: Call_Rejected
IP gateways Section Name Description <target> called_number The number, URI, or IP address of the endpoint being called protocol The protocol used on the connection. Either SIP or H.323 gateway Gateway address. Only present if the protocol is H.323 gatekeeper Name of the gatekeepers used to make the call. -
Page 21: Call_Accepted
IP gateways call_accepted The far end accepted the call either through the operator or directly. After this event, the caller is talking to the far end. Section Name Description <connection> unique_id Unique identifier for the connection in the format nnnnnnnn <target>... -
Page 22: Connection_Finished
IP gateways connection_finished A call completes or is terminated. Section Name Description <connection> unique_id Unique identifier for the connection in the format nnnnnnnn.. duration How long the connection lasted in minutes and seconds duration_in_minutes How long the connection lasted rounded up to the nearest minute disconnect_reason A string explaining the reason why the participant was... -
Page 23: Advanced Media Gateway
Advanced Media Gateway Advanced Media Gateway Example CDR file: AM GW 3610 The exported file has the name cdr_log.xml. You can change the filename if necessary. Below is a short extract showing each event type on the AM gateway. <?xml version="1.0" encoding="UTF-8" ?> <cdr_events>... -
Page 24: Am Gateway Event Types
Advanced Media Gateway AM gateway event types Currently the AM gateway CDRs support the event types listed in the table below. They are listed in the order that they occur in the CDR. Event type Description <connection_started> A new connection is initiated <connection_finished>... -
Page 25: Participant_Disconnected
Advanced Media Gateway participant_disconnected A participant has or has been disconnected from the AM gateway. Note that there will be two participant_disconnected events per call record. Section Name Description <connection> unique_id Unique identifier for the connection <endpoint_details> ip_address The IP address of the proxy server Participant name <media_from_endpoint>... - Page 26 Advanced Media Gateway THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.