Telepresence Conductor

[dinesh.purohit]

Hello,

Is there any CDR for Telepresence Conductor export report possible, like CUCM. or we require TMS for reporting. Pls suggest

[Patrick Sparkman · Accepted solution]

Conductor doesn't send CDR data to anything at the moment, see bug CSCuj42268, in order to get conference CDRs you'll need to add the conference bridges into TMS. Below are the reporting limitations outlined with Conductor conferences.

• Call Detail Records (CDRs) from TelePresence Conductor-managed conference bridges will not contain any ConferenceIDs.
• TelePresence Conductor itself does not feed back any conference CDRs to Cisco TMS. The bridges themselves will however, if added to Cisco TMS.
• Depending on the call direction you might get incomplete CDR data, as dialing out can lead to incorrect data.
• Bridge utilization reporting is not supported for conferences hosted on a TelePresence Conductor.

To read about these limitations and others, refer to the Conductor with TMS Deployment Guide (XC3.0 with TMS 14.6).  You can also refer to the CMR Premises Deployment Guides for more information as well.

[dinesh.purohit]

Patrick Sparkman

Thanks for information. As per your comment its bug not yet resolved. It means we cant collect the cdr report from conductor itself ? 

If we want to achieve cdr , its mandatory to have integrated with Cisco TMS ?

 As this line says Depending on the call direction you might get incomplete CDR data, as dialing out can lead to incorrect data.

It means get the CDR but not correct it means ?

Pls suggest.

[Patrick Sparkman]

No, Conductor doesn't report CDR data itself.  You'll need to add the conference bridges into TMS, and CDR data will be gathered from them.  Regarding the possible incomplete CDR data depending on the call direction, I don't know the specifics, sorry.

[dinesh.purohit]

Thanks Patrick.