[cisco-voip] CDR and billing questions

[Wes Sisk]

You can follow the transfer in CDRs to identify the original leg and the 
consult leg.  It is possible and done.  Kudos to the CDR billing 
partners who work through the logic to make it happen.

/wes

sashank wrote:
>
> What happens if the c alls are transferred to auto attendant on unity 
> connection. A call comes from outside and the welcome prompt comes up 
> and if the user will dial an internal extension the call will be 
> routed to the extension. Here is the thing, when you see the CDR's fpr 
> incoming calls, the it shows that all the incoming calls are routed to 
> the auto attendant pilot number, even if they dial the internal 
> extension. So I don't think that any work around is there for this.
>
>  
>
> Warm Regards,
>
> Venkata Sasanka.pathi(-91 950 265 2290)
>
> Consultant | unified communications
>
> Locuz Enterprise Solutions Ltd. (A Subsidiary of 3i-Infotech)
>
> (office:914066115656)
>
>  sasanka.pathi at locuz.com <mailto:sasanka.pathi at locuz.com>
>
> www.locuz.com <http://www.locuz.com>
>
>  
>
> *From:* cisco-voip-bounces at puck.nether.net 
> [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf Of *Ryan Ratliff
> *Sent:* Tuesday, October 05, 2010 8:05 PM
> *To:* Lelio Fulgenzi
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] CDR and billing questions
>
>  
>
> The information is all there in the CDR records it's up to the 3rd 
> party to use it.
>
> http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/service/8_0_2/cdrdef/cdrex.html#wp1245778
>
>  
>
> -Ryan
>
>  
>
> On Oct 5, 2010, at 10:01 AM, Lelio Fulgenzi wrote:
>
>
>
> 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 
> <mailto:Sandy.Lee at dti.ulaval.ca>>
> *To: *cisco-voip at puck.nether.net <mailto: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 <mailto:cisco-voip at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>  
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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/20101006/7184f8c5/attachment.html>