<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[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]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceType"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PlaceName"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:"MS Mincho";
        panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:"\@MS Mincho";
        panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman";}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:blue;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:Tahoma;
        color:blue;
        font-weight:normal;
        font-style:normal;
        text-decoration:none none;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.25in 1.0in 1.25in;}
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 bgcolor=white lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=blue face=Tahoma><span style='font-size:
10.0pt;font-family:Tahoma;color:blue'>The answer probably lies with the PM, but
I don’t know why or when …<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Tahoma><span style='font-size:
10.0pt;font-family:Tahoma;color:blue'><o:p> </o:p></span></font></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;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> Sunday, December 04, 2005
2:04 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] problem
with part and css (the none partition)</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Is there any particular reason why they've gone this way
with the CTIs? Are they eventually going to change it?</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<blockquote style='border:none;border-left:solid black 1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>
<div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
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 size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial;font-weight:bold'>From:</span></font></b><font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'> <a
href="mailto:Michael_Davis@eLoyalty.com" title="Michael_Davis@eLoyalty.com">Davis,
Michael</a> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><b><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial;font-weight:bold'>To:</span></font></b><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'> <a
href="mailto:cisco-voip@puck.nether.net" title="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 size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial;font-weight:bold'>Sent:</span></font></b><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'> Sunday, December
04, 2005 3:02 PM<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><b><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial;font-weight:bold'>Subject:</span></font></b><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'> RE: [cisco-voip]
problem with part and css (the none partition)<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>I don't have a whole lot of experience with 3.1, but I have recently
been "burnt" by forgetting the CTI vs non-CTI search order. :-)<br>
<br>
-----Original Message----- <br>
From: Mark Snow [mailto:highspeedsnow@gmail.com] <br>
Sent: Sun 12/4/2005 1:47 PM <br>
To: Davis, Michael; <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<br>
Cc: <br>
Subject: RE: [cisco-voip] problem with part and css (the none partition)<br>
<br>
<br>
<br>
Good Point!<br>
<br>
For those of you out there running versions prior to 3.1 when it was still<br>
'Call Mangler'.<br>
<br>
Also if you are running those previous versions, try Forwarding your phone<br>
to it's own DN and then calling it from another phone - just for fun! ;)<br>
<br>
> -----Original Message-----<br>
> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>
[mailto:cisco-voip-<br>
> <a href="mailto:bounces@puck.nether.net">bounces@puck.nether.net</a>] On
Behalf Of Davis, Michael<br>
> Sent: Sunday, December 04, 2005 1:36 PM<br>
> To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> Subject: RE: [cisco-voip] problem with part and css (the none partition)<br>
><br>
> Also,<br>
> Prior to CCM 3.1, Device Level CSS were placed ahead of Line Level CSS.<br>
As of<br>
> 3.1, Line Level CSSes are placed ahead of Device Level, EXCEPT for CTI<br>
devices<br>
> (Softphone, <st1:place w:st="on"><st1:PlaceName w:st="on">CTI</st1:PlaceName>
<st1:PlaceType w:st="on">Ports</st1:PlaceType></st1:place>, Route Points,
etc,) which use the old method.<br>
><br>
> Mike<br>
><br>
><br>
> -----Original Message-----<br>
> From: <a
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>
on behalf of Mark Snow<br>
> Sent: Sun 12/4/2005 1:13 PM<br>
> To: 'Lelio Fulgenzi'; <a
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> Cc:<br>
> Subject: RE: [cisco-voip] problem with
part and css (the none<br>
partition)<br>
><br>
><br>
><br>
> Guys,<br>
><br>
><br>
><br>
> The <none> partition is actually
a real partition, it is there by<br>
default and<br>
> is assigned to the very bottom of every CSS.<br>
><br>
><br>
><br>
> So if you had a RP of '91X' in the
INTERAL_PT belonging to the<br>
> HQ_911_CSS and Phone 1 at HQ had this CSS assigned, but you also had
a RP<br>
of<br>
> '911' in in the <none> Partition (PT) and the user at Phone 1 at HQ
dialed<br>
911, he<br>
> would actually be routed to the 911 RP in the <none> PT due to the
fact<br>
that it<br>
> appears last in the HQ_911_CSS and is a longer match.<br>
><br>
><br>
><br>
> It is similar to the <null> MRG,
which belongs at the very bottom of<br>
every<br>
> MRGL.<br>
><br>
><br>
><br>
> MTC and HTH some :-)<br>
><br>
><br>
><br>
> -Mark Snow<br>
><br>
> CCIE Voice # 14073<br>
><br>
><br>
><br>
><br>
> _____<br>
><br>
><br>
> From: <a
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>
[mailto:cisco-voip-<br>
> <a href="mailto:bounces@puck.nether.net">bounces@puck.nether.net</a>] On
Behalf Of Lelio Fulgenzi<br>
> Sent: Sunday, December 04, 2005 12:19
PM<br>
> To: <a
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> Subject: Re: [cisco-voip] problem with
part and css (the none<br>
partition)<br>
><br>
><br>
><br>
> Oh yeah, and don't forget the
<None> partition. It's not really a<br>
partition,<br>
> but it encompasses as DNs and patterns that have not been assigned to a<br>
> partition. There is no easy way to block access to these DNs unless you<br>
create<br>
> duplicate entries in another partition and block those (which we have<br>
done). I<br>
> can't remember the search algorithm and whether the <None> partition
is<br>
simply<br>
> placed last in the ordered list and searched accordingly or if it is<br>
searched only<br>
> after no match is made in the other partitions. A search on CCO docs could<br>
tell<br>
> you this probably.<br>
><br>
><br>
><br>
> We've moved towards a dialplan model
that has next to no DNs in the<br>
> <None> partition. The only ones we have in there are our campus
emergency<br>
> number and our helpline number. In the event that a phone goes out<br>
> misconfigured, chances are very high they will be able to call these<br>
numbers.<br>
><br>
><br>
><br>
>
----- Original Message -----<br>
><br>
>
From: Lelio Fulgenzi <<a href="mailto:lelio@uoguelph.ca">mailto:lelio@uoguelph.ca</a>><br>
><br>
>
To: James Grace <<a href="mailto:jgrace@digitelusa.net">mailto:jgrace@digitelusa.net</a>>
; cisco-<br>
> <a href="mailto:voip@puck.nether.net">voip@puck.nether.net</a><br>
><br>
>
Sent: Sunday, December 04, 2005 1:13 PM<br>
><br>
>
Subject: Re: [cisco-voip] problem with part and css<br>
><br>
><br>
><br>
>
Think of it this way, a calling search space is simply an<br>
ordered<br>
> list of partitions which the line or device searches through for a match<br>
of the<br>
> dialed digits. If you look through the traces, you will see the term PSS<br>
which I<br>
> believe stands for Phone Search Space. This is made up of the line's<br>
ordered list of<br>
> partitions and then the device's ordered list of partitions. For example:<br>
><br>
><br>
><br>
>
CSS1=PartA,PartB,PartC<br>
><br>
>
CSS2=PartX,PartY,PartZ<br>
><br>
>
Device assigned CSS1<br>
><br>
>
Line assigned CSS2<br>
><br>
>
the PSS would be: PartX,PartY,PartZ,PartA,PartB,PartC<br>
><br>
><br>
><br>
>
So the idea you propose is a valid one. We use it here.<br>
Assign the<br>
> device access to everything and then deny the line access to particular<br>
services.<br>
> We isolate the 'everything' to PSTN access and actually allow oncampus<br>
access<br>
> through the line's partition.<br>
><br>
><br>
><br>
>
You have to make sure that the denies are at least as<br>
specific as<br>
> the allows. And by denies, I mean, creating a route pattern that has the<br>
'block'<br>
> option checked.<br>
><br>
><br>
><br>
>
Post back if you need more...<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
>
----- Original Message -----<br>
><br>
>
From: James Grace <<a href="mailto:jgrace@digitelusa.net">mailto:jgrace@digitelusa.net</a>><br>
><br>
>
To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
><br>
>
Sent: Sunday, December 04, 2005 12:35 PM<br>
><br>
>
Subject: [cisco-voip] problem with part and css<br>
><br>
><br>
><br>
>
we have a cm 4.1.2 es 41<br>
><br>
>
i was just told by a tac rep that 4.1. and higher<br>
uses both<br>
> css on line and device.<br>
><br>
>
what does this mean????<br>
><br>
><br>
><br>
>
i have my device as unrestricted and all of the part<br>
in it.<br>
> and then i have my line configure with a customize css, ie maybe no int<br>
calls or LD<br>
> calls.<br>
><br>
>
the problem im having is that when i make a ld or<br>
int call,<br>
> uses the device. and when i make a ipphone call ( 4 dgit dialing
between<br>
sites) it<br>
> uses the line. I dont understand this. nore do i understand
the<br>
statement IT<br>
> USES BOTH LINE AND DEVICE. can someone Please clear this up
for me.<br>
> Thanks in advance<br>
><br>
><br>
> _____<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>
><br>
><br>
> _____<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>
><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>
<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>
</div>
</body>
</html>