<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1491" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV>There is a fundamental restriction with the number of 'characters' a
calling search space can contain in it's partition list - I'm pretty sure that
number is 512 characters. That means there is no limit to the number of
partitions in a calling search space per se, but the list of partitions,
including the semi-colon seperator can not exceed 512 characters.</DIV>
<DIV> </DIV>
<DIV>That being said, devices of a similar nature/purpose should be grouped
together in their own partition, allowing you to control access to those
devices. Voicemail is a good example of one where you really don't want people
to access the ports directly, you want them to access a pilot and the pilot
number is a translation to the first voicemail port which rings busy/noanswer to
the next voicemail port. Coincedentally, this structure has changed in 4.0,
voicemail ports no longer have a ring busy/noanswer destination. However, this
still doesn't change the principle behind 'hiding' the voicemail ports.</DIV>
<DIV> </DIV>
<DIV>It also depends on the dialplan strategy you take with respect to off-net
access. We've taken an approach where the device has access to all offnet
patterns and the line's CSS included route patterns that block access.</DIV>
<DIV> </DIV>
<DIV>Something to remember, is to keep the <none> partition empty. Since
by default, the <none> partition is searched, there is no easy way to
block a CSS from searching the <none> partition for a DN to match other
than explicitly adding route patterns that block it. It is handy to have an
emergency number there so a phone, even misconfigured, can still call the
emergency number. </DIV>
<DIV> </DIV>
<DIV> </DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=mpedersen@touchbase.us href="mailto:mpedersen@touchbase.us">Marcello
Pedersen</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, April 08, 2005 3:59
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> [cisco-voip] CCS and Partitions
best practices</DIV>
<DIV><BR></DIV>Hey Everyone,<BR><BR>I am wondering what are the best practices
for implanting CCS and partitions. Should each site have its own partition and
CCS? How about VM ports should they be in a in its own partition. <BR><BR>also
can I forward a DN to the VM pilot number so user can access centralized VM
from the
road?<BR><BR><BR>Regards,<BR>Marcello<BR><BR>______________________________________________________________________<BR>This
email has been scanned by the MessageLabs Email Security System.<BR>For more
information please visit <A
href="http://www.messagelabs.com/email">http://www.messagelabs.com/email</A>
<BR>______________________________________________________________________<BR><BR>_______________________________________________<BR>cisco-voip
mailing list<BR><A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR></BLOCKQUOTE></BODY></HTML>