[cisco-voip] Mobile Connect and CDR's

[Ed Leatherman]

Thanks for the suggestions everyone. I noticed the follow-me bit in the CDR
guide, but it didn't seem like there is a particular search I can do on raw
CDR's to identify them as such based on the example call... i'm assuming
last redirecting DN could = the desk number in other situations besides
followme right?

On Thu, Oct 23, 2014 at 4:01 PM, Ryan Ratliff (rratliff) <rratliff at cisco.com
> wrote:

> This doc I believe has exactly what you are looking for.
>
>
> http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/9_1_1/cdrdef/CUCM_BK_C268EF1B_00_cucm-cdr-admin-guide-91/CUCM_BK_C268EF1B_00_cucm-cdr-admin-guide-91_chapter_011.html#CUCM_RF_ME367C12_00
>
> -Ryan
>
> On Oct 23, 2014, at 11:49 AM, Wes Sisk (wsisk) <wsisk at cisco.com> wrote:
>
> I see suggestions that the last redirecting number is the desk number.
>
> -Wes
>
>
>
> On Oct 23, 2014, at 10:04 AM, Ed Leatherman <ealeatherman at gmail.com>
> wrote:
>
> Hello!
>
> I'm trying to figure out how we can identify call legs from Mobile Connect
> that are going out to long distance destination numbers. We have a number
> of IT staff with home or mobile numbers that are long distance, and would
> like to start offering them the capability to use mobile connect to
> facilitate on-call and other communications needs.
>
> Unfortunately this also means I need some way to track utilization and
> provide bill-back information for internal billing.
>
> I can't find any way to identify the final called party number for the
> remote destination except that it appears to be embedded in
> OutgoingProtocolCallRef, but the docs just call this a "Globally unique
> call reference", not sure I want to rely on it.
>
> So far the best I can do to pick out these calls seems to be searching for
> records where the finalcalledpartypartition matches the unrestricted long
> distance partition name, and the originalcalledpartypartition matches our
> internal DN partition. Wish there was a cleaner way to report on these that
> included the remote destination number.
>
> Does anyone know of a better way to do this? CUCM 9.1.
>
> BTW I am using splunk right now to sift through the records - at some
> point we will probably have this as part of our real billing software
> though.
>
> --
> Ed Leatherman
> _______________________________________________
> cisco-voip mailing list
> 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
>
>


-- 
Ed Leatherman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20141028/980d27eb/attachment.html>