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

[Lelio Fulgenzi]

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. 

Aside from being able to dial numbers they shouldn't, I see there's really only two reasons to separate system numbers: variable length DNs/patterns and preventing routing loops. 

So, I'm thinking of reclassifying system DNs/patterns into the following: 

    • User Dialable (phantom lines, etc) 
    • System Dialable Only (voice ports) 
    • PSTN Trunk Dialable Only (variable length translations) 
    • User Dialable Via Trunk (to prevent loops between systems) 
    • System Dialable Only Via Trunk (to prevent loops between systems) 

I could consider breaking it down further to user dialable and forwardable, but I would rather say if you can dial it, you can forward to it and just handle problems as they come up. 

Just wondering what others are using as a partitioning schema and/or if they see anything wrong with this simplified approach. 







--- 
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) 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100209/bc555ec0/attachment.html>