<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2096" name=GENERATOR><!--[if !mso]>
<STYLE>v\:* {
BEHAVIOR: url(#default#VML)
}
o\:* {
BEHAVIOR: url(#default#VML)
}
w\:* {
BEHAVIOR: url(#default#VML)
}
.shape {
BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
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]--></HEAD>
<BODY lang=EN-US vLink=blue link=blue bgColor=white>
<DIV><SPAN class=393321421-08042005><FONT face=Arial color=#0000ff size=2>So let
say I have 2 sites with centralized CCM. </FONT></SPAN></DIV>
<DIV><SPAN class=393321421-08042005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=393321421-08042005><FONT face=Arial color=#0000ff size=2>Site A
:</FONT></SPAN></DIV>
<DIV><SPAN class=393321421-08042005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=393321421-08042005><FONT face=Arial color=#0000ff
size=2>HQ_CCS</FONT></SPAN></DIV>
<DIV><SPAN class=393321421-08042005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=393321421-08042005><FONT face=Arial color=#0000ff size=2>and
three partitions </FONT></SPAN></DIV>
<DIV><SPAN class=393321421-08042005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=393321421-08042005><FONT face=Arial color=#0000ff
size=2>BR_911_local_and_toll_free</FONT></SPAN></DIV>
<DIV><SPAN class=393321421-08042005><FONT face=Arial color=#0000ff
size=2>BR_Long_Distance</FONT></SPAN></DIV>
<DIV><SPAN class=393321421-08042005><FONT face=Arial color=#0000ff
size=2>BR_International</FONT></SPAN></DIV>
<DIV><SPAN class=393321421-08042005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=393321421-08042005><FONT face=Arial color=#0000ff size=2>Site
b:</FONT></SPAN></DIV>
<DIV><SPAN class=393321421-08042005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=393321421-08042005><FONT face=Arial color=#0000ff
size=2>Branch_CCS</FONT></SPAN></DIV>
<DIV><SPAN class=393321421-08042005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=393321421-08042005><SPAN class=393321421-08042005><FONT
face=Arial color=#0000ff size=2>and three partitions </FONT></SPAN></SPAN></DIV>
<DIV><SPAN class=393321421-08042005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=393321421-08042005>
<DIV><SPAN class=393321421-08042005><FONT face=Arial color=#0000ff size=2>BR_
911_local_and_toll_free</FONT></SPAN></DIV>
<DIV><SPAN class=393321421-08042005><FONT face=Arial color=#0000ff
size=2>BR_Long_Distance</FONT></SPAN></DIV>
<DIV><SPAN class=393321421-08042005><FONT face=Arial color=#0000ff
size=2>BR_International</FONT></SPAN></DIV>
<DIV><SPAN class=393321421-08042005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=393321421-08042005><FONT face=Arial color=#0000ff size=2>There
shouldn't be a problem with user A calling user B
right?</FONT></SPAN></DIV><SPAN class=393321421-08042005></SPAN></SPAN><FONT
face=Tahoma>
<DIV><BR> </DIV>
<DIV><FONT size=2><SPAN class=393321421-08042005> </SPAN>-----Original
Message-----<BR><B>From:</B> Voll, Scott
[mailto:Scott.Voll@wesd.org]<BR><B>Sent:</B> Friday, April 08, 2005 2:07
PM<BR><B>To:</B> cisco-voip@puck.nether.net<BR><B>Subject:</B> RE: [cisco-voip]
CCS and Partitions best practices<BR><BR></DIV></FONT></FONT></DIV>
<BLOCKQUOTE>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">To add to that we
have two different CSS in each location. One for staff so they can call
long distance and one for common area phones that can only dial local.
If you’re a larger enterprise you might look at doing it by department.
It all comes down to how you want to service people. I think it’s best
to keep your options open. More partions more CSS add complexity but they also
open up more options.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Scott<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><FONT
face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">
<HR tabIndex=-1 align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P class=MsoNormal><B><FONT face=Tahoma size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT
face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net]
<B><SPAN style="FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Lelio
Fulgenzi<BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> Friday, April
08, 2005 1:11 PM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B>
cisco-voip@puck.nether.net<BR><B><SPAN
style="FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [cisco-voip] CCS and
Partitions best practices</SPAN></FONT><o:p></o:p></P></DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt">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.<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt">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.<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt">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.<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt">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. <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<BLOCKQUOTE
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">----- Original Message -----
<o:p></o:p></SPAN></FONT></P></DIV>
<DIV style="font-color: black">
<P class=MsoNormal style="BACKGROUND: #e4e4e4"><B><FONT face=Arial
size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Arial">From:</SPAN></FONT></B><FONT
face=Arial size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> <A
title=mpedersen@touchbase.us href="mailto:mpedersen@touchbase.us">Marcello
Pedersen</A> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><B><FONT face=Arial size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Arial">To:</SPAN></FONT></B><FONT
face=Arial size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> <A
title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A>
<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><B><FONT face=Arial size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Arial">Sent:</SPAN></FONT></B><FONT
face=Arial size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> Friday,
April 08, 2005 3:59 PM<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><B><FONT face=Arial size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Arial">Subject:</SPAN></FONT></B><FONT
face=Arial size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">
[cisco-voip] CCS and Partitions best
practices<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P></DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt">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><o:p></o:p></SPAN></FONT></P></BLOCKQUOTE></DIV><BR>______________________________________________________________________<BR>This
email has been scanned by the MessageLabs Email Security System.<BR>For more
information please visit http://www.messagelabs.com/email
<BR>______________________________________________________________________<BR></BLOCKQUOTE>
<BR>
______________________________________________________________________<BR>
This email has been scanned by the MessageLabs Email Security System.<BR>
For more information please visit http://www.messagelabs.com/email <BR>
______________________________________________________________________<BR>
</BODY></HTML>