<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>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...<br><br>
<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: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-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]-->
<div class="Section1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">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></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"> </span></p>
<div>
<div style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<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";">
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></p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal" style="margin-bottom: 12pt;"><span style="font-size: 10pt; 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></p>
<div>
<p class="MsoNormal"><span style="font-size: 10pt; 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></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 10pt; 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></p>
</div>
</div>
</div>
</div>
</div>
</div></body></html>