Guest

Preview Tool

Cisco Bug: CSCuj42268 - Conductor does not send CDR data to external manager

Last Modified

Mar 03, 2018

Products (1)

  • Cisco TelePresence Conductor

Known Affected Releases

XC2.1 XC2.2

Description (partial)

Symptom:
Conductor does not send CDR data to an external manager. The request for this enhancement is for the Conductor to generate CDR's  and forward them to the configured external manager.

Conditions:
To reproduce this:

1. Start a packet sniff on TMS server.
2. Schedule a conference including the Conductor.
3. End the conference.
4. Stop the packet capture.

Looking at the packet capture you will notice that the Conductor sends no feedback to TMS about the conference

You will see that the Conductor does not send any details about the conference.  The MCU selected for the conference does send CDR information but it is not linked to the Conference ID of the call on the Conductor (CSCug78968) which is postponed.

Seeing that the Conductor Manages MCU resources, when gathering CDR data TMS should be gathering this data from the Conductor rather than the MCU chosen to host the conference.

Related Community Discussions

<key>CSCuj42268</key> - Conductor does not send CDR data to external manager
Hello, When this limitation will be fix?
Latest activity: May 11, 2015
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.