[cisco-voip] CDR and billing questions

[Lelio Fulgenzi]

I would be interested in hearing about this as well. 

I also believe that transfers to internal parties behave the same way. 

For example: Extension A calls an offnet long distance number then transfers to extension B after 1 minute. 

In this case, your CDR will only show a 1 minute LD call from extension A. I _think_ the CDR will show the transfer as a call from the LD number to extension B which doesn't show up as a billable call. 

I believe some CDR processing companies can catch this by using the call leg identifiers, but it's not easy. 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 



From: "Sandy Lee" <Sandy.Lee at dti.ulaval.ca> 
To: cisco-voip at puck.nether.net 
Sent: Tuesday, October 5, 2010 9:55:59 AM 
Subject: [cisco-voip] CDR and billing questions 




Hi everyone, 



In UCM 7.1(5) we’re not able to identify from which extension the call was made when it’s a transfer between external parties. For example, I receive an external call from (A) and I transfer/conference with another external LD number (B). The call from A to B appears in the CDR, but there is no way our billing app can “match” with my extension, so the billing app can’t bill back my extension for the call. Is there a parameter somewhere to solve this issue? 



In CUCM 4.1(3) we couldn’t do it either but we could live with it because we didn’t have a lot of those. We have a legacy PBX and from its CDR, the billing app can do it. Until this summer, our main number was going through the legacy PBX, so we could match the DNs. But now, our main number has been transferred on the IP telephony side and we have to be able to bill back. 



I can’t block offnet to offnet transfers, this is not an option for me. 



Thanks for any input on this. 



Sandy. 


_______________________________________________ 
cisco-voip mailing list 
cisco-voip at puck.nether.net 
https://puck.nether.net/mailman/listinfo/cisco-voip 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20101005/d08d27e1/attachment.html>