<html dir="ltr"><head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style>@font-face {
        font-family: Cambria Math;
}
@font-face {
        font-family: Calibri;
}
@font-face {
        font-family: Tahoma;
}
@font-face {
        font-family: Lucida Sans;
}
@page Section1 {margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
        FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
LI.MsoNormal {
        FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
DIV.MsoNormal {
        FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
A:link {
        COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
        COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
        COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
        COLOR: purple; TEXT-DECORATION: underline
}
P {
        FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman","serif"
}
P.MsoAcetate {
        FONT-SIZE: 8pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"
}
LI.MsoAcetate {
        FONT-SIZE: 8pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"
}
DIV.MsoAcetate {
        FONT-SIZE: 8pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"
}
SPAN.BalloonTextChar {
        FONT-FAMILY: "Tahoma","sans-serif"
}
SPAN.EmailStyle19 {
        COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"
}
SPAN.EmailStyle22 {
        COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"
}
.MsoChpDefault {
        FONT-SIZE: 10pt
}
DIV.Section1 {
        
}
</style>
<meta content="MSHTML 6.00.2800.1605" name="GENERATOR">
<style title="owaParaStyle">P {
        MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body lang="EN-US" vlink="purple" link="blue" ocsi="x">
<div dir="ltr"><font face="Tahoma" color="#000000" size="2">I had this question on this alias a couple of months ago and Mike Lydick provided the following workaround.
</font></div>
<div dir="ltr"><font face="tahoma" size="2"></font> </div>
<div dir="ltr"><font face="tahoma" size="2">Use CTI route points with a call forward set with a wild card mask. So in your case have a CTI route point with the following characteristics:</font></div>
<div dir="ltr"><font face="tahoma" size="2"></font> </div>
<div dir="ltr"><font face="tahoma" size="2">DN = 80XX</font></div>
<div dir="ltr"><font face="tahoma" size="2">CFA = 73180XX</font></div>
<div dir="ltr"><font face="tahoma" size="2"></font> </div>
<div dir="ltr"><font face="tahoma" size="2">The call is seen as a call forward and you may have to wait for the interdigit timer to expire before the call is placed, but it works a treat and gets around the translation urgent priority issue.</font></div>
<div dir="ltr"><font face="tahoma" size="2"></font> </div>
<div dir="ltr"><font face="tahoma" size="2"></font> </div>
<div dir="ltr"><font face="tahoma" size="2"></font>cheers,</div>
<div dir="ltr"><font face="times new roman">Wil</font></div>
<div dir="ltr"><font face="times new roman"></font> </div>
<div dir="ltr">
<hr tabindex="-1">
</div>
<div dir="ltr"><font face="Tahoma" size="2"><b>From:</b> cisco-voip-bounces@puck.nether.net [cisco-voip-bounces@puck.nether.net] On Behalf Of Jason Aarons (US) [jason.aarons@us.didata.com]<br>
<b>Sent:</b> Tuesday, 2 December 2008 12:02 AM<br>
<b>To:</b> Ryan Ratliff; cisco-voip@puck.nether.net<br>
<b>Subject:</b> Re: [cisco-voip] Calling Search Space<br>
</font><br>
</div>
<div></div>
<div>
<div class="Section1">
<p class="MsoNormal"><span style="COLOR: #1f497d">Any workaround? Not clear how I can expand local calls to the 7-digit number.
</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d"></span> </p>
<div>
<div style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<p class="MsoNormal"><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</span></b><span style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> Ryan Ratliff [mailto:rratliff@cisco.com]
<br>
<b>Sent:</b> Monday, December 01, 2008 9:41 AM<br>
<b>To:</b> Jason Aarons (US); cisco-voip@puck.nether.net<br>
<b>Subject:</b> RE: [cisco-voip] Calling Search Space</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida Sans','sans-serif'">Think of a translation pattern like a route pattern with urgent priority set. This means as soon as it is matched it will be used to route the call, regardless
of potential matches. The first four digits of 8063104 match 80XX thus the call is routed using the translation pattern.</span><span style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"></span></p>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"></span> </p>
</div>
<p><span style="FONT-SIZE: 10pt">-Ryan </span></p>
<div>
<p class="MsoNormal"><span style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"></span> </p>
</div>
<p class="MsoNormal"><span style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"></span> </p>
<div class="MsoNormal" style="TEXT-ALIGN: center" align="center"><span style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'">
<hr align="center" width="100%" size="2">
</span></div>
<p class="MsoNormal" style="MARGIN-BOTTOM: 12pt"><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</span></b><span style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net]
<b>On Behalf Of </b>Jason Aarons (US)<br>
<b>Sent:</b> Monday, December 01, 2008 9:01 AM<br>
<b>To:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> [cisco-voip] Calling Search Space</span><span style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"></span></p>
<p class="MsoNormal">CallManager 6.1.2-1002-1</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">CallingSearchSpaceA</p>
<p class="MsoNormal"> Internal_PT has phone with DN=8063104</p>
<p class="MsoNormal"> Translations_PT has Translation Pattern 80XX to 73180XX</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">When dialing 8063104 the number is translated to 7318063.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I’m trying to find the documentation on cisco.com that shows the CallManager logic. I expected the match in Partition to be found first and completed, not translated. I’m deploying Variable-Length On-Net Dial Plans with Flat Addressing.
You 7-digit dial another office, but can 4 digit locally which expands to 7-digit.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<div class="MsoNormal" style="TEXT-ALIGN: center" align="center"><span style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'">
<hr align="center" width="100%" size="1">
</span></div>
<p><strong>Disclaimer: This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you
have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message
and deleting it from your computer. Thank you. </strong></p>
</div>
<p></p>
<hr size="1">
<p></p>
<p><strong>Disclaimer: This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you
have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message
and deleting it from your computer. Thank you. </strong></p>
</div>
</body>
</html>