<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
color:black;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Interesting method…<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>I have a lab SIP trunk.. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>We’ll give this a test run and see what happens, but it will be week after next before I come back to this.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>I’ll update you after testing..<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Thanks for the idea Wes!<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Jim<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> Wes Sisk [mailto:wsisk@cisco.com] <br><b>Sent:</b> Thursday, February 17, 2011 8:21 AM<br><b>To:</b> Jim McBurnett<br><b>Cc:</b> Lelio Fulgenzi; cisco-voip@puck.nether.net<br><b>Subject:</b> Re: [cisco-voip] CDR for a Translation pattern<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have not tested this but the concepts are sound.<br><br>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:<br>DN: 1XXX<br>forward destination: XX<br><br>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.<br><br>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.<br><br>I'd be interested to hear about your results.<br><br>Regards,<br>Wes<br><br>On 2/16/2011 10:38 PM, Jim McBurnett wrote: <o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'>You hit the proverbial nail…</span><o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'>Long term analysis..</span><o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'>I have a customer with over 100 toll free numbers gathered over the years.</span><o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'>Some get lots of calls and some none.. BUT to see what is happening we need those statistics.</span><o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'>Thanks!</span><o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'>Jim</span><o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p><div><div style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0in 0in 0in;border-color:-moz-use-text-color -moz-use-text-color'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Lelio Fulgenzi [<a href="mailto:lelio@uoguelph.ca">mailto:lelio@uoguelph.ca</a>] <br><b>Sent:</b> Wednesday, February 16, 2011 8:13 PM<br><b>To:</b> Jim McBurnett<br><b>Cc:</b> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><b>Subject:</b> Re: [cisco-voip] CDR for a Translation pattern</span><o:p></o:p></p></div></div><p class=MsoNormal> <o:p></o:p></p><div><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>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.<br><br>It will help with troubleshooting, but not sure about any long term analysis.<br><br>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)<br><br><br></span><o:p></o:p></p><div class=MsoNormal align=center style='text-align:center'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><hr size=2 width="100%" align=center></span></div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>From: </span></b><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>"Jim McBurnett" <a href="mailto:jim@tgasolutions.com"><jim@tgasolutions.com></a><br><b>To: </b><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><b>Sent: </b>Wednesday, February 16, 2011 8:08:22 PM<br><b>Subject: </b>[cisco-voip] CDR for a Translation pattern<br><br><br><br></span><o:p></o:p></p><p class=MsoNormal>Hey folks,<o:p></o:p></p><p class=MsoNormal>Got a quick one..<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>I know we can’t check CDR for a Translated number..<o:p></o:p></p><p class=MsoNormal>IE 800’s coming into an LD trunk going to a call center queue number… or AA..<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>So besides creating a # for every 800 # and forwarding that on, is there any way to show a translation pattern is actually being used?<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Ideas??<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Thanks,<o:p></o:p></p><p class=MsoNormal>Jim<o:p></o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><o:p></o:p></p></div><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>_______________________________________________<o:p></o:p></pre><pre>cisco-voip mailing list<o:p></o:p></pre><pre><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><o:p></o:p></pre><pre><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></pre></div></body></html>