<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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.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";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@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 lang=EN-US link=blue vlink=purple>
<div class=WordSection1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I agree with using the device CSS. However, it sounds like
you are trying to implement AAR in the event of a WAN outage (if you have all
phones registered to a centralized CUCM cluster). If that is the case,
then there is configuration on the gateway that u need to do for when folks at
the remote site dial 4 or 5 digit numbers back at the main site (which won’t
work if the WAN is down) so that it is prefixed with the 1 (if it is long
distance) and the required prefix digits. Also, you would need to create
AAR groups for the remote site(s) as well as the main site so that when the WAN
is down, and a phone from the main site or other remote sites try to call the
remote site, AAR will prefix it with numbers set in AAR. You also have to
ensure either the phone line is configured with the correct phone mask for the
line or configure the AAR mask for the phone…if AAR mask is configured, I
believe it overrides the External Phone mask configuration when AAR kicks in.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Here are some links on AAR.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><a
href="http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/6_1_1/ccmcfg/b03aar.html">http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/6_1_1/ccmcfg/b03aar.html</a><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><a
href="http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/6_1_1/ccmsys/a03rp.html#wpxref40267">http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/6_1_1/ccmsys/a03rp.html#wpxref40267</a><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><a
href="http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00807f8b32.shtml">http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00807f8b32.shtml</a><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:black'>Bill
</span><span style='font-family:"Calibri","sans-serif";color:gray'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<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"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <b>On Behalf Of </b>Scott Voll<br>
<b>Sent:</b> Thursday, October 21, 2010 12:25 PM<br>
<b>To:</b> Dan Letkeman<br>
<b>Cc:</b> cisco-voip<br>
<b>Subject:</b> Re: [cisco-voip] Trying to understand partitions,calling and
called transformations<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>The route pattern should have a partition. the route
pattern should point to the RL --> RG (get the transformation mask) -->
VGW.<o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Now I would use the CSS on the phone rather then just the DP
CSS. as more info as you move forward there is a CSS on both the phone
device and Line. The two combine to give you an over all CSS.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>What are you trying to do with your transformation mask?
is this to prefix going out? or is this the caller ID going out?<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>you can see on the voice gateway what it's doing going out
by doing a debug isdn q931. This might help in troubleshooting.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>Scott<o:p></o:p></p>
<div>
<p class=MsoNormal>On Thu, Oct 21, 2010 at 8:51 AM, Dan Letkeman <<a
href="mailto:danletkeman@gmail.com">danletkeman@gmail.com</a>> wrote:<o:p></o:p></p>
<p class=MsoNormal>Its' starting to make sense.<br>
<br>
So my goal here is to assign a different Calling Party Translation<br>
Mask to the 3 different groups of phones I have.<br>
<br>
1 - Create a route group (assign the gateway to this, as I only have 1<br>
gateway for everyone)<br>
2 - Create a route list (add the route group i just created, then<br>
click on the route list details and assign the calling party<br>
transformation mask (1015551234) )<br>
3 - Create a device pool for each location and assign the route group<br>
to the respective device pool (local route group option)<br>
<br>
So if a device is assigned to the correct device pool, the calling<br>
party transformation mask should apply accordingly.<br>
<br>
Only problem is it doesn't work. Am I missing something?<br>
<br>
Thanks,<br>
<span style='color:#888888'>Dan.</span><o:p></o:p></p>
<div>
<div>
<p class=MsoNormal><br>
On Thu, Oct 21, 2010 at 8:52 AM, Scott Voll <<a
href="mailto:svoll.voip@gmail.com">svoll.voip@gmail.com</a>> wrote:<br>
> Dan--<br>
> Think of Partitions as cups. inside the cups you put phone lines and
Route<br>
> patterns etc. Think of Calling search spaces as the buckets that
have all<br>
> the cups in them.<br>
> If you have all your partitions in a single Calling Search Space and you<br>
> have access to use that CSS you will be able to call anything in the
bucket.<br>
> Meaning any cup (partition) with anything in them.<br>
> Now take it a step further. You Don't want them to call a specific
phone<br>
> line. you would put it in a partition that is not in the bucket
(CSS).<br>
> Then if you have the CSS without the partition, you can no longer
call it.<br>
> The same is true of route patterns, translation patterns, etc.<br>
> Hope that helps.<br>
><br>
><br>
> On Wed, Oct 20, 2010 at 4:22 PM, Dan Letkeman <<a
href="mailto:danletkeman@gmail.com">danletkeman@gmail.com</a>> wrote:<br>
>><br>
>> Hello,<br>
>><br>
>> I'm new to CUCM and I'm trying to understand how to configure calling<br>
>> and called transformations with partitions and device pools.<br>
>><br>
>> I currently have a cluster at the head office, with a PRI and some<br>
>> test phones connect. I have three remote offices that will also<br>
>> connect over fiber to the head office CUCM cluster, and will only fail<br>
>> over to SRST via there local router when the wan is down.<br>
>><br>
>> I need to create some kind of group for each of the remote
offices as<br>
>> well as the main office, so when they are calling in and out of the<br>
>> PRI they have there own number assigned to there group of phones.<br>
>> Just like they have it down with there individual PBX's.<br>
>><br>
>> I have it working so far that I can call out of the PRI. So I
have a<br>
>> small understanding of the route pattern's, route groups and route<br>
>> Lists. I'm just not sure how I can apply a calling
transformation<br>
>> mask to each of the locations, all while allowing them to call each<br>
>> other, and call in and out of the PRI.<br>
>><br>
>> Any help would be appreciated.<br>
>><br>
>> Thanks,<br>
>> Dan.<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"
target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>
><o:p></o:p></p>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</body>
</html>