<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'><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.<br><br>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.<br><br>So, I'm thinking of reclassifying system DNs/patterns into the following:<br><ul><li>User Dialable (phantom lines, etc)<br></li><li>System Dialable Only (voice ports)</li><li>PSTN Trunk Dialable Only (variable length translations)</li><li>User Dialable Via Trunk (to prevent loops between systems)<br></li><li>System Dialable Only Via Trunk (to prevent loops between systems)</li></ul>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.<br><br>Just wondering what others are using as a partitioning schema and/or if they see anything wrong with this simplified approach.<br><br><br><br><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></div></body></html>