[cisco-voip] CDR for a Translation pattern

[Jim McBurnett]

Interesting method…
I have a lab SIP trunk..
We’ll give this a test run and see what happens, but it will be week after next before I come back to this.

I’ll update you after testing..
Thanks for the idea Wes!

Jim

From: Wes Sisk [mailto:wsisk at cisco.com]
Sent: Thursday, February 17, 2011 8:21 AM
To: Jim McBurnett
Cc: Lelio Fulgenzi; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CDR for a Translation pattern

I have not tested this but the concepts are sound.

CTI Route points, ports, etc. can have wildcards such as 1XXX (reference IPMA)  They can be configured with CFUnreg or CFAll with a forwarding calling search space.  Forwarding actually also supports masks so you can do something like:
DN: 1XXX
forward destination: XX

dialing 1234 would match the DN.  The XX in the forward destination are treated as a mask to digits 34 become the forward destination. This is mostly trivia.  I believe you can achieve what you need with a DN of 18XXXXXXXXX and forward destination of 18XXXXXXXXX but with a different forwarding search space.

If the phone endpoints have CSS that can reach a dummy cti route point configured with 18XXXXXXXXX as first step then it should be recorded in CDR.  Then use the forward all or forward unregistered and associated CSS to reach the translation pattern to do the number modification and route the call.  In my mental math this may give you what you need in the original and final called party numbers in CDR.

I'd be interested to hear about your results.

Regards,
Wes

On 2/16/2011 10:38 PM, Jim McBurnett wrote:
You hit the proverbial nail…
Long term analysis..

I have a customer with over 100 toll free numbers gathered over the years.
Some get lots of calls and some none.. BUT to see what is happening we need those statistics.
Thanks!

Jim

From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca]
Sent: Wednesday, February 16, 2011 8:13 PM
To: Jim McBurnett
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] CDR for a Translation pattern

Not sure if this helps or not, but I know there is a system parameter that enables complex digit analysis and will add all translations into the trace files.

It will help with troubleshooting, but not sure about any long term analysis.

---
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: "Jim McBurnett" <jim at tgasolutions.com><mailto:jim at tgasolutions.com>
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Sent: Wednesday, February 16, 2011 8:08:22 PM
Subject: [cisco-voip] CDR for a Translation pattern



Hey folks,
Got a quick one..

I know we can’t check CDR for a Translated number..
IE 800’s coming into an LD trunk going to a call center queue number… or AA..

So besides creating a # for every 800 # and forwarding that on, is there any way to show a translation pattern is actually being used?

Ideas??

Thanks,
Jim

_______________________________________________
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110217/e092a639/attachment.html>