[cisco-voip] problem with part and css (the none partition)

[Mark Snow]

Guys,

 

The <none> partition is actually a real partition, it is there by default
and is assigned to the very bottom of every CSS.

 

So if you had a RP of '91X' in the INTERAL_PT belonging to the HQ_911_CSS
and Phone 1 at HQ had this CSS assigned,  but you also had a RP of '911' in
in the <none> Partition (PT) and the user at Phone 1 at HQ dialed 911, he
would actually be routed to the 911 RP in the <none> PT due to the fact that
it appears last in the HQ_911_CSS and is a longer match.

 

It is similar to the <null> MRG, which belongs at the very bottom of every
MRGL.

 

MTC and HTH some :-)

 

-Mark Snow

CCIE Voice # 14073

 

  _____  

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
Sent: Sunday, December 04, 2005 12:19 PM
To: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] problem with part and css (the none partition)

 

Oh yeah, and don't forget the <None> partition. It's not really a partition,
but it encompasses as DNs and patterns that have not been assigned to a
partition. There is no easy way to block access to these DNs unless you
create duplicate entries in another partition and block those (which we have
done). I can't remember the search algorithm and whether the <None>
partition is simply placed last in the ordered list and searched accordingly
or if it is searched only after no match is made in the other partitions. A
search on CCO docs could tell you this probably.

 

We've moved towards a dialplan model that has next to no DNs in the <None>
partition. The only ones we have in there are our campus emergency number
and our helpline number. In the event that a phone goes out misconfigured,
chances are very high they will be able to call these numbers.

 

----- Original Message ----- 

From: Lelio Fulgenzi <mailto:lelio at uoguelph.ca>  

To: James Grace <mailto:jgrace at digitelusa.net>  ; cisco-voip at puck.nether.net


Sent: Sunday, December 04, 2005 1:13 PM

Subject: Re: [cisco-voip] problem with part and css 

 

Think of it this way, a calling search space is simply an ordered list of
partitions which the line or device searches through for a match of the
dialed digits. If you look through the traces, you will see the term PSS
which I believe stands for Phone Search Space. This is made up of the line's
ordered list of partitions and then the device's ordered list of partitions.
For example:

 

CSS1=PartA,PartB,PartC

CSS2=PartX,PartY,PartZ

Device assigned CSS1

Line assigned CSS2

the PSS would be: PartX,PartY,PartZ,PartA,PartB,PartC

 

So the idea you propose is a valid one. We use it here. Assign the device
access to everything and then deny the line access to particular services.
We isolate the 'everything' to PSTN access and actually allow oncampus
access through the line's partition.

 

You have to make sure that the denies are at least as specific as the
allows. And by denies, I mean, creating a route pattern that has the 'block'
option checked.

 

Post back if you need more...

 

 

 

----- Original Message ----- 

From: James Grace <mailto:jgrace at digitelusa.net>  

To: cisco-voip at puck.nether.net 

Sent: Sunday, December 04, 2005 12:35 PM

Subject: [cisco-voip] problem with part and css 

 

we have a cm 4.1.2 es 41   

i was just told by a tac rep that 4.1. and higher uses both css on line and
device.

what does this mean????

 

i have my device as unrestricted and all of the part in it.  and then i have
my line configure with a customize css, ie maybe no int calls or LD calls.  

the problem im having is that when i make a ld or int call,  uses the
device.  and when i make a ipphone call ( 4 dgit dialing between sites) it
uses the line. I dont understand this.  nore do i understand  the statement
IT USES BOTH LINE AND DEVICE.   can someone Please clear this up for me.
Thanks in advance


  _____  


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


  _____  


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20051204/9210c698/attachment-0001.html