[cisco-voip] partitioning system DNs and route patterns...

[Lelio Fulgenzi]

It's not now, but I wanted to be more descriptive. 

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. 



--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 


----- Original Message ----- 
From: "Jeff Garvas" <jeff at cia.net> 
To: "Lelio Fulgenzi" <lelio at uoguelph.ca> 
Cc: "cisco-voip voyp list" <cisco-voip at puck.nether.net> 
Sent: Tuesday, February 9, 2010 2:15:04 PM GMT -05:00 US/Canada Eastern 
Subject: Re: [cisco-voip] partitioning system DNs and route patterns... 

Lelio, 

How are you running out of characters? Is your naming convention substantially detailed? 


On Tue, Feb 9, 2010 at 2:05 PM, Lelio Fulgenzi < lelio at uoguelph.ca > wrote: 





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. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100209/a77463b2/attachment.html>