CDR billing for Transfer, conference and forwarding
We found some difficulties when trying to link several CDRs within a conference or transfer. The doc says they should have the same call leg, while from the actual CDR files from customers, we find the call legs are all different through out one single conference.
Re: CDR billing for Transfer, conference and forwarding
Thank you for you answear.
The DOC that you sent to me is about CDR for CUCM version 7.0.1 and my version is CUCM 6.1.4, I don't know if there are diferences between them.
I've opened a case with TAC to try solve or find a solution for this "issue".
Follow the TAC's position:
As per your conversation with David, there is no report that Call Manager generates that will let you see who transfer and where were those calls transferred to, neither who created/participated in conferences and how long would those conferences lasted. However you can pull that information from Call Manager with a billing server. Attached you will find the link that talks about the supported billing servers that Cisco recommends to use
Note: As stated in the document you provided each time that a call is transferred, the Cisco Unified Communications Manager terminates the CDR for that call and initiates a new CDR. For conferences the number of CDRs that are generated depends on the number of parties in the conference. One CDR exists for each party in the conference, one CDR for the original placed call, and one CDR for each setup call that is used to join other parties to the conference, please remember that Call Manager assign a conference ID when they are created so you do best effort following it.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.