User manual TANDBERG TELEPRESENCE CALL DETAIL RECORDS FILE FORMAT REFERENCE GUIDE

[. . . ] Cisco TelePresence Call Detail Records File Format Reference Guide D14663. 03 November 2010 Contents Contents Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Overview of CDR file formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 How to use this reference guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 MCUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [. . . ] The section on IP gateway CDRs starts on page 17. The section on AM gateway CDRs starts on page 23. Call Detail Record File Format Reference Guide Page 4 of 26 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" encoding="UTF-8" ?> <cdr_events> <event index="0" date="13 April 2010" time="13:09:14" type="scheduled_conference_started"> <conference unique_id="3365002" name="Temporary conference" /> <conference_details numeric_id="1111" has_pin="no" billing_code="&lt;none&gt;" /> <owner name="admin" /> <end scheduled_date="13 April 2010" scheduled_time="13:18:00" scheduled_duration_in_minutes="9" /> </event> <event index="1" date="13 April 2010" time="13:09:38" type="scheduled_conference_started"> <conference unique_id="3365003" name="Permanent conference" /> <conference_details numeric_id="&lt;none&gt;" has_pin="yes" billing_code="&lt;none&gt;" /> <owner name="admin" /> <end scheduled_time="permanent" /> </event> <event index="2" date="13 April 2010" time="13:10:22" type="ad-hoc_conference_started"> <conference unique_id="3365005" name="3333" /> <conference_details numeric_id="3333" has_pin="no" billing_code="&lt;none&gt;" /> <creator participant_id="1" /> <end scheduled_time="&lt;none&gt;" /> </event> <event index="3" date="13 April 2010" time="13:10:26" type="participant_joined"> <conference unique_id="3365005" name="3333" /> <participant particpant_id="1" participant_id="1" /> <call direction="incoming" /> </event> <event index="4" date="13 April 2010" time="13:12:41" type="participant_left"> <conference unique_id="3365005" name="3333" /> <endpoint_details ip_address="10. 2. 160. 3" dn="&lt;none&gt;" h323_alias="sam. spade. e20o1@cisco. com" configured_name="&lt;none&gt;" /> <participant participant_id="1" /> <call time_in_conference="2 mins 15 sec" time_in_conference_in_minutes="3" disconnect_reason="participant ended call" /> <media_from_endpoint resolution="1280 x 768" video_codec="H. 264" audio_codec="AAC" bandwidth="832000 bit/s" /> <media_to_endpoint resolution="768 x 512" video_codec="H. 264" audio_codec="AAC" bandwidth="832000 bit/s" /> </event> <event index="5" date="13 April 2010" time="13:12:41" type="conference_finished"> <conference unique_id="3365005" name="3333" /> <limits audio_video_participants="20" audio_only_participants="60" streaming_participants_allowed="1" /> <participants max_simultaneous_audio_video="1" max_simultaneous_audio_only="0" max_simultaneous_streaming="0" total_audio_video="1" total_audio_only="0" total_streaming="0" /> <gatekeeper registered_with_gatekeeper="no" /> <end duration="2 mins 19 sec" duration_in_minutes="3" /> </event> <event index="6" date="13 April 2010" time="13:18:00" type="conference_finished"> <conference unique_id="3365002" name="Temporary conference" /> <limits audio_video_participants="20" audio_only_participants="60" streaming_participants_allowed="1" /> <participants max_simultaneous_audio_video="0" max_simultaneous_audio_only="0" max_simultaneous_streaming="0" total_audio_video="0" total_audio_only="0" total_streaming="0" /> <gatekeeper registered_with_gatekeeper="no" /> <end duration="10 mins 0 sec" duration_in_minutes="10" /> </event> </cdr_events> Call Detail Record File Format Reference Guide Page 5 of 26 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 scheduled_conference_started Description A scheduled conference was started. Either a permanent conference or one with a scheduled end time An ad hoc conference was started through the auto attendant A participant joined the conference A participant disconnected or was forcibly disconnected The conference finished ad-hoc_conference_started participant_joined participant_left conference_finished The tables in the sections below show the parameters for each event type in the order in which they appear in the CDR. There is an explanation for each parameter. scheduled_conference_started There are two variations for this event. One for permanent conferences and one for conferences with a scheduled end time. The differences are indicated in the table. Section <conference> Name unique_id Description Unique identifier for the conference in the format nnnnnnnn. Currently one of: unspecified no answer rejected rejected immediately busy gatekeeper error protocol error destination unreachable participant ended call participant dropped gatekeeper ended call name <endpoint_details> ip_address dn h323_alias configured_name <participant> participant_id <call> time_in_conference time_in_conference_in_ minutes disconnect_reason Call Detail Record File Format Reference Guide Page 8 of 26 MCUs Section <media_from_endpoint> Name resolution Description 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" One of: Null H. 261 Motion JPEG MPEG2 system stream raw H. 263 H. 264 Remote frame buffer One of: Null G. 711a G. 711mu MPEG2 system stream raw Linear G. 711mu ASF G. 722 G. 722. 1 G. 722. 1 Annex C G. 723. 1 G. 728 G. 729 G. 729A G. 729B G. 729AB Polycom(R) Siren14(TM) AAC Bandwidth in bits per second The highest resolution sent to or received from the endpoint during the course of its conference participation in the format "n x n" for example "704 x 576" As for <media_from_endpoint> above As for <media_from_endpoint> above Bandwidth in bits per second video_codec audio_codec bandwidth <media_to_endpoint> resolution video_codec audio_codec bandwidth conference_finished This event is seen when a conference completes according to its schedule end time or is terminated. Section <conference> Name unique_id Description Unique identifier for the conference in the format nnnnnnnn as seen in the scheduled_conference_started or ad-hoc_conference_started events For scheduled conferences, the conference name as allocated by the user and, for ad hoc conferences, a name allocated by the unit The maximum number of video plus audio 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 Page 9 of 26 name <limits> audio_video_participants Call Detail Record File Format Reference Guide MCUs Section Name audio_only_participants Description 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) The highest number of a type of participant present at any one time during the lifetime of the conference The total number of a type of participant who joined the conference during its lifetime Either yes or no: "yes" if at any point during its lifetime the conference was registered with a gatekeeper How long the conference lasted in minutes and seconds How long the conference lasted rounded up to the next whole number of minutes streaming_participants_allowed <participants> max_simultaneous_audio_video max_simultaneous_audio_only max_simultaneous_streaming total_audio_video total_audio_only total_streaming <gatekeeper> registered_with_gatekeeper <end> duration duration_in_minutes Call Detail Record File Format Reference Guide Page 10 of 26 ISDN gateways ISDN gateways Example CDR file: ISDN GW 3241/ ISDN GW MSE 8310 and 8321 blades The exported file has the name cdr_log. xml. The following is an extract showing each event type on the ISDN gateway unit or blade. <?xml version="1. 0" encoding="UTF-8" standalone="yes" ?> <cdr_events> <event index="0" date="17 March 2010" time="17:08:57" type="new_connection"> <connection unique_id="1200000" /> <call direction="ip to isdn" calling_number="sam. spade. t@tandberg. com" original_called_number="110541" /> <isdn call_type="bonding" max_call_duration="<no time limit>" /> </event> <event index="1" date="17 March 2010" time="17:09:03" type="connection_proceeding"> <connection unique_id="1200000" /> <call via_auto_attendant="no" final_called_number="0541" /> <isdn_numbers subcall_1="" subcall_2="" subcall_3="" subcall_4="" subcall_5="" subcall_6="" subcall_7="" subcall_8="" subcall_9="" subcall_10="" subcall_11="" /> </event> <event index="2" date="17 March 2010" time="17:09:37" type="new_connection"> <connection unique_id="1200001" /> <call direction="ip to isdn" calling_number="sam. spade. t@tandberg. com" original_called_number="11153030" /> <isdn call_type="bonding" max_call_duration="<no time limit>" /> </event> <event index="3" date="17 March 2010" time="17:09:52" type="connection_proceeding"> <connection unique_id="1200001" /> <call via_auto_attendant="no" final_called_number="153030" /> <isdn_numbers subcall_1="" subcall_2="" subcall_3="" subcall_4="" subcall_5="" subcall_6="" subcall_7="" /> </event> <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" /> <media_to_isdn resolution="105 x 111" video_codec="unknown" audio_codec="Null" bandwidth="576000 bit/s" /> </event> <event index="5" date="17 March 2010" time="17:10:08" type="multiway_call_transfer"> <connection unique_id="1200000" /> <call duration="1 mins 11 sec" duration_in_minutes="2" disconnect_reason="call transferred to multiway destination" new_called_number="0175300009@tandberg. com" /> <bandwidth max_bandwidth="768 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" /> <media_to_isdn resolution="105 x 111" video_codec="unknown" audio_codec="Null" bandwidth="768000 bit/s" /> </event> <event index="6" date="17 March 2010" time="17:10:27" type="connection_finished"> <connection unique_id="1200000" /> <call duration="1 mins 30 sec" duration_in_minutes="2" disconnect_reason="participant ended call" /> <bandwidth max_bandwidth="768 kbit/s" downspeeded="no" /> <h323_endpoint_details ip_address="10. 2. 160. 3" dn="0175300009@tandberg. com" h323_alias="multiway" /> Call Detail Record File Format Reference Guide Page 11 of 26 ISDN gateways <media_from_isdn resolution="1280 x 768" video_codec="H. 263" audio_codec="G. 722" bandwidth="824000 bit/s" /> <media_to_isdn resolution="704 x 576" video_codec="H. 263" audio_codec="G. 722" bandwidth="768000 bit/s" /> </event> <event index="7" date="17 March 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" /> </event> <event index="8" date="31 March 2010" time="10:24:41" type="new_connection"> <connection unique_id="381009" /> <call direction="isdn to ip" calling_number="084000" original_called_number="1500" /> <isdn call_type="bonding" max_call_duration="<no time limit>" /> </event> <event index="9" date="31 March 2010" time="10:25:03" type="connection_finished"> <connection unique_id="381009" /> <call duration="22 sec" duration_in_minutes="1" disconnect_reason="gatekeeper error" /> <bandwidth max_bandwidth="384 kbit/s" downspeeded="no" /> <h323_endpoint_details ip_address="0. 0. 0. 0" dn="Codian ISDN GW Auto Attendant" h323_alias="&lt;none&gt;" /> <media_from_isdn resolution="352 x 288" video_codec="H. 263" audio_codec="G. 711mu" bandwidth="448000 bit/s" /> <media_to_isdn resolution="352 x 288" video_codec="H. 263" audio_codec="G. 711mu" bandwidth="448000 bit/s" /> </event> <event index="10" date="31 March 2010" time="10:25:26" type="new_connection"> <connection unique_id="381010" /> <call direction="isdn to ip" calling_number="084000" original_called_number="1500" /> <isdn call_type="bonding" max_call_duration="<no time limit>" /> </event> <event index="11" date="31 March 2010" time="10:26:12" type="connection_proceeding"> <connection unique_id="381010" /> <call via_auto_attendant="yes" final_called_number="10. 2. 135. 150" /> <isdn_numbers subcall_1="" subcall_2="" subcall_3="" subcall_4="" subcall_5="" /> </event> <event index="11" date="31 March 2010" time="10:26:42" type="connection_finished"> <connection unique_id="381010" /> <call duration="1 mins 16 sec" duration_in_minutes="2" disconnect_reason="participant ended call" /> <bandwidth max_bandwidth="384 kbit/s" downspeeded="no" /> <h323_endpoint_details ip_address="10. 2. 135. 150" dn="Codian ISDN GW Auto Attendant" h323_alias="endpoint10. 2. 135. 150" /> <media_from_isdn resolution="1280 x 768" video_codec="H. 264" audio_codec="G. 722" bandwidth="440000 bit/s" /> <media_to_isdn resolution="704 x 576" video_codec="H. 263" audio_codec="G. 722" bandwidth="384000 bit/s" /> </event> </cdr_events> Call Detail Record File Format Reference Guide Page 12 of 26 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 new_connection connection_proceeding Description A new connection is initiated Appears whenever: - the call has been connected - a downspeeding event occurs. (Downspeding is a technique that limits the bandwidth used by a video conferencing unit to the maximum specified by the gatekeeper) - a channel is added in an aggregation call An H. 323 call leg is transferred to a multiway conference A connection is closed. The reason is provided within the event detail multiway_call_transfer connection_finished The tables in the sections below show the parameters for each event type in the order in which they appear in the CDR. There is an explanation for each parameter. new_connection This event is seen when a call starts. Section <connection> Name unique_id Description Unique identifier for the connection in the format nnnnnnnn. This is generated automatically by the ISDN gateway Either ip to isdn or isdn to ip For IP to ISDN calls, the H. 323 alias or E. 164 number of the IP endpoint. For ISDN to IP calls, the E. 164 number of the ISDN endpoint or ISDN if number is unknown The E. 164 number that was originally dialed by the calling endpoint, or <none> if an IP endpoint calls the ISDN gateway by its IP address One of: bonding (Video using bonding) voice (Telephone) h221 aggregation (Video using N x 64 kbps) Either <no time limit> or a number of seconds <call> direction calling_number original_called_number <isdn> call_type max_call_duration Call Detail Record File Format Reference Guide Page 13 of 26 ISDN gateways connection_proceeding This event is seen during a call. Section <connection> Name unique_id Description The same unique identifier for the connection as provided in the previous new_connection event in the format nnnnnnnn Whether or not the connection was set up via the auto attendant. Either yes or no The final called number in the format <ip address:port no> or a number as generated by the dial plan The subcall number in the format subcall_n where n is between 1 and 5. The full number is shown for aggregation calls. For bonding calls, only the final digits of the number are shown (that is, those numbers that are different from the master call). [. . . ] Note that there will be two participant disconnected events per call The tables in the sections below show the parameters for each event type in the order in which they appear in the CDR. There is an explanation for each parameter. connection_started A new connection is initiated on the AM gateway. Section <connection> <call> Name unique_id source destination Description Unique identifier for the connection Name of the calling participant Name of the called participant connection_finished A connection is terminated on the AM gateway. Section <connection> <call> Name unique_id duration duration_in_minutes disconnect_reason Description Unique identifier for the connection Duration in minutes and seconds Duration rounded up to nearest minute Reason the participant was disconnected. One of: unspecified unspecified error participant ended call gateway ended call no answer rejected rejected immediately busy timeout network error protocol error destination unreachable authentication failed service unavailable capability negotiation error Call Detail Record File Format Reference Guide Page 24 of 26 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 <connection> <endpoint_details> <media_from_endpoint> and <media_to_endpoint> Name unique_id ip_address dn resolution video_codec Description Unique identifier for the connection The IP address of the proxy server Participant name The highest resolution received during the call The codec used on the outgoing and incoming video. [. . . ]