<!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" xmlns:st1 =
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1522" 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]--><o:SmartTagType name="PlaceType"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
name="PlaceName"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
name="place"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><!--[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 lang=EN-US vLink=blue link=blue bgColor=white>
<DIV><FONT face=Arial size=2>And the other question is....I'm assuming this
doesn't affect IPCommunicator? I ran a test in the lab and it created the PSS
according to line+device. Is this because IP communicator is <EM>not</EM> a CTI
application like Softphone? </FONT><FONT face=Arial size=2>Are my results what
you would expect?</FONT></DIV>
<BLOCKQUOTE dir=ltr
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=highspeedsnow@gmail.com href="mailto:highspeedsnow@gmail.com">Mark
Snow</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=lelio@uoguelph.ca
href="mailto:lelio@uoguelph.ca">'Lelio Fulgenzi'</A> ; <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> Sunday, December 04, 2005 4:20
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> RE: [cisco-voip] problem with
part and css (the none partition)</DIV>
<DIV><BR></DIV>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Tahoma color=blue size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma">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 face=Tahoma color=blue size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Tahoma"><o:p> </o:p></SPAN></FONT></P>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<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"> <A
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</A>
[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> <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><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 face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; 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 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=Michael_Davis@eLoyalty.com
href="mailto:Michael_Davis@eLoyalty.com">Davis, Michael</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"> Sunday,
December 04, 2005 3:02 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"> RE:
[cisco-voip] problem with part and css (the none
partition)<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">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></BLOCKQUOTE></BODY></HTML>