<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>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>
<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;}
@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-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);">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></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">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></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"> </span></p>
<div>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">Thanks,</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">Go0se</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">My blog: </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><a href="http://atc.go0se.com/" target="_blank">http://atc.go0se.com</a></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">Help Hopegivers International feed the orphans of India, adopt a
hope home today:</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"> <a href="http://www.hopegivers.org/Get-Involved/Adopt-A-Hope-Home/Available-Hope-Homes.htm" target="_blank">http://www.hopegivers.org</a></span></p>
</div>
<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: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></p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal"><span style="font-size: 10pt; 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...<br>
<br>
<br>
</span></p>
<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><span style="color: black;"></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"> </span><span style="color: black;"></span></p>
<div>
<div style="border-style: solid none none; border-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"; color: black;">From:</span></b><span style="font-size: 10pt; 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;"></span></p>
</div>
</div>
<p class="MsoNormal"><span style="color: black;"> </span></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><span style="color: black;"></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><span style="color: black;"></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><span style="color: black;"></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div></body></html>