<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=utf-8">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
@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: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
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</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=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>We have about the same setup as Jason. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>We have a legacy Pbx and CUCM, so with all the IP phones in a PT
and the pbx phones in another, it solved the issue of looping on my PRIs. All
the vm ports and other “anti-user” access are protected in another PT.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Works great.<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>
<p class=MsoNormal><span lang=FR-CA style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>________________________________<o:p></o:p></span></p>
<p class=MsoNormal><span lang=FR-CA style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><b><span lang=FR-CA style='font-size:10.0pt;font-family:
"Calibri","sans-serif";color:#1F497D'>Sandy Lee<o:p></o:p></span></b></p>
<p class=MsoNormal><span lang=FR-CA style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Analyste<o:p></o:p></span></p>
<p class=MsoNormal><span lang=FR style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Division des infrastructures<o:p></o:p></span></p>
<p class=MsoNormal><span lang=FR style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Direction des technologies de l'information<o:p></o:p></span></p>
<p class=MsoNormal><span lang=FR-CA style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Université Laval<o:p></o:p></span></p>
<p class=MsoNormal><span lang=FR style='font-size:10.0pt;font-family:Wingdings;
color:black'>(</span><span lang=FR style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:black'> 418.656.2131, ext. 4420</span><span lang=FR
style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:blue'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><a href="mailto:Sandy.Lee@dti.ulaval.ca"><span lang=FR>Courriel</span></a></span><span
lang=FR style='font-size:8.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>
— </span><span style='font-size:9.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><a href="http://www.dti.ulaval.ca/sgc/nous_joindre"><span
lang=FR>Nous joindre</span></a></span><span lang=FR style='font-size:8.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'> — </span><span
style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a
href="http://www.rec.ulaval.ca/lce/securite/confidentialite.htm"><span lang=FR>Avis
relatif à la confidentialité</span></a></span><span lang=FR style='font-size:
9.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><span lang=FR
style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:maroon'>VEUILLEZ
PRENDRE NOTE DE MA NOUVELLE ADRESSE ÉLECTRONIQUE </span></b><span lang=FR
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>: </span><span
style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:navy'><a
href="mailto:Sandy.Lee@dti.ulaval.ca"><span lang=FR>Sandy.Lee@dti.ulaval.ca</span></a></span><span
lang=FR style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:navy'><o:p></o:p></span></p>
</div>
<p class=MsoNormal><span lang=FR style='font-size:11.0pt;font-family:"Calibri","sans-serif";
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 style='margin-left:.5in'><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>Fuermann, Jason<br>
<b>Sent:</b> Tuesday, February 09, 2010 5:04 PM<br>
<b>To:</b> 'Lelio Fulgenzi'; Go0se<br>
<b>Cc:</b> cisco-voip voyp list<br>
<b>Subject:</b> Re: [cisco-voip] partitioning system DNs and route patterns...<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>The way we’re set up is 1
partition for all DN’s, another for voice ports and then ~18 other partitions
with translations/route patterns (I designed this on CM 6 so no “local
gateways”). We have a completely permissive CSS on the phone itself and a blocking
CSS on the lines. If you want me to go into more detail, just let me know.<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";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 style='margin-left:.5in'><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 [mailto:lelio@uoguelph.ca] <br>
<b>Sent:</b> Tuesday, February 09, 2010 2:58 PM<br>
<b>To:</b> Go0se<br>
<b>Cc:</b> cisco-voip voyp list; Fuermann, Jason<br>
<b>Subject:</b> Re: [cisco-voip] partitioning system DNs and route patterns...<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>Organization plus restriction. The one drawback with fewer
partitions is that when you allow a user to call a partition, you allow them to
call all numbers in that partition (obviously). So if I have two types of
system DNs, right now, by keeping them in separate partitions, I can allow
someone to call one group without letting them be able to call the other group.
Do I need that granularity? Probably not. That's what I'm trying to find out by
asking the list. Who knows, it might serve as a template for people who are new
to CallManager and can use it as a starting point. I know I wish I had
something like that when I started.<br>
<br>
With respect to restrictions, it's more for setting expectations. For example,
by making voice mail ports not dialable, we don't have to worry about some
group on campus creating procedures which include dialing the voice mail ports
directly and having to worry about dealing with complaints/issues when we
migrate to a new set of voice mail ports when we upgrade. If they were
dialable, people could (and would) start dialing the ports directly (for
whatever godawful reason).<br>
<br>
Looking forward to what others are doing.....<br>
<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>
----- Original Message -----<br>
From: "Go0se" <me@go0se.com><br>
To: "Lelio Fulgenzi" <lelio@uoguelph.ca>, "Jason
Fuermann" <JBF005@shsu.edu><br>
Cc: "cisco-voip voyp list" <cisco-voip@puck.nether.net><br>
Sent: Tuesday, February 9, 2010 3:21:22 PM GMT -05:00 US/Canada Eastern<br>
Subject: RE: [cisco-voip] partitioning system DNs and route patterns...<br>
<br>
<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>The simpler the better… but
what other than organization are you trying to accomplish? Do you need to
restrict who can call whom? Do you have overlapping DNs? </span><span
style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'> </span><span
style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>I’ve always been partial to
putting all DNs in one flat partition and restricting internal/local/LD/Intl
calling with the overlapping line and device CSS’s… and if you are running
CM7.x I love love love the new local gateway feature – greatly reduces the
number of CCSs if you have multiple buildings/offices/locations with multiple
PSTN connections.</span><span style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'> </span><span
style='color:black'><o:p></o:p></span></p>
<div>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Thanks,</span><span
style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'> </span><span
style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Go0se</span><span
style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'> </span><span
style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>My blog: </span><span
style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><a
href="http://atc.go0se.com/" target="_blank">http://atc.go0se.com</a></span><span
style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'> </span><span
style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Help Hopegivers International
feed the orphans of India, adopt a hope home today:</span><span
style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'> <a
href="http://www.hopegivers.org/Get-Involved/Adopt-A-Hope-Home/Available-Hope-Homes.htm"
target="_blank">http://www.hopegivers.org</a></span><span style='color:black'><o:p></o:p></span></p>
</div>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'> </span><span
style='color:black'><o:p></o:p></span></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 style='margin-left:.5in'><b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif";color:black'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On
Behalf Of </b>Lelio Fulgenzi<br>
<b>Sent:</b> Tuesday, February 09, 2010 1:57 PM<br>
<b>To:</b> Jason Fuermann<br>
<b>Cc:</b> cisco-voip voyp list<br>
<b>Subject:</b> Re: [cisco-voip] partitioning system DNs and route patterns...</span><span
style='color:black'><o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal style='margin-left:.5in'><span style='color:black'> <o:p></o:p></span></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>Agreed. That's why it's something I'd like to migrate to. I'm
hoping others who have tried something similar can say either "works for
me" or present any gotchas. <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>
----- Original Message -----<br>
From: "Jason Fuermann" <JBF005@shsu.edu><br>
To: "Lelio Fulgenzi" <lelio@uoguelph.ca><br>
Cc: "cisco-voip voyp list" <cisco-voip@puck.nether.net>,
"Jeff Garvas" <jeff@cia.net><br>
Sent: Tuesday, February 9, 2010 2:34:11 PM GMT -05:00 US/Canada Eastern<br>
Subject: RE: [cisco-voip] partitioning system DNs and route patterns...</span><span
style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>I would go with keep it as
simple as possible. Otherwise, it will look good now, but in two years it’ll be
so messed from all the mistakes that the organization won’t matter.</span><span
style='color:black'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'> </span><span
style='color:black'><o:p></o:p></span></p>
<div>
<div style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0in 0in 0in;
border-color:-moz-use-text-color'>
<p class=MsoNormal style='margin-left:.5in'><b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif";color:black'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On
Behalf Of </b>Lelio Fulgenzi<br>
<b>Sent:</b> Tuesday, February 09, 2010 1:18 PM<br>
<b>To:</b> Jeff Garvas<br>
<b>Cc:</b> cisco-voip voyp list<br>
<b>Subject:</b> Re: [cisco-voip] partitioning system DNs and route patterns...</span><span
style='color:black'><o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal style='margin-left:.5in'><span style='color:black'> <o:p></o:p></span></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>It's not now, but I wanted to be more descriptive. <br>
<br>
Plus, the 1024 character limit is not the only reason, simplifying is also
another reason. Right now, we have to think about which partition a system DN
belongs to, and even then, mistakes are made because of how the partitions are
listed.<br>
<br>
<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>
----- Original Message -----<br>
From: "Jeff Garvas" <jeff@cia.net><br>
To: "Lelio Fulgenzi" <lelio@uoguelph.ca><br>
Cc: "cisco-voip voyp list" <cisco-voip@puck.nether.net><br>
Sent: Tuesday, February 9, 2010 2:15:04 PM GMT -05:00 US/Canada Eastern<br>
Subject: Re: [cisco-voip] partitioning system DNs and route patterns...<br>
<br>
Lelio,<br>
<br>
How are you running out of characters? Is your naming convention
substantially detailed?</span><span style='color:black'><o:p></o:p></span></p>
<div>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'>On Tue, Feb 9, 2010 at 2:05 PM,
Lelio Fulgenzi <<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>>
wrote:</span><span style='color:black'><o:p></o:p></span></p>
<div>
<div>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif";color:black'><br>
When we first deployed our dial-plan we took a very compartmentalized approach
and created different partitions for system DN/Patterns based on their role/use
and then assigned the partitions appropriately. Assuming the max chars in PSS
still being 1024 characters, I'm re-thinking things and am hoping to get some
feedback from the group.</span><span style='color:black'><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>