[cisco-voip] Device CSS vs Line CSS -- Which takes priority?

[David Schulz]

The Line CSS takes precedence only in the case of a TIE. Otherwise, it always uses the best match, regardless of the order. In the line/device approach ... Class of service restrictions are placed on the line CSS, so this would be true..... But again.... The rules are :

1. Best match of all partitions in the resulting CSS.... The concatenation of the line and device CSS.

2. In the event of a tie..... The order of partitions in the resulting CSS becomes the tie breaker. Therefore. Line partitions will take precedence but only in the case of a tie.

Hope this helps

Dave


On Dec 10, 2014, at 2:22 PM, Adam Blomfield <adman at adman.net<mailto:adman at adman.net>> wrote:

 A block will always override a route, regardless of which is on the device and which is on the line. In the case of overlap where both route the line will take precedence over the device.

-Adam

On Wed, Dec 10, 2014 at 12:09 PM, Scott Voll <svoll.voip at gmail.com<mailto:svoll.voip at gmail.com>> wrote:
Lelio has talked about the fact that device and Line combine for a phone total CSS.

Now which one takes over in the case of an overlap?

For instance.  The line has the 911 patter, and the device has a block 911 pattern.

Will the call be blocked or placed?

we are moving to EM so we are placing everyones CSS on the Line, but I have Softphones that I don't want to dial 911 because we can not provide the correct location as they are all at there personal homes.

I want to just put a block patter on the device.

TIA

Scott


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


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto: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/20141210/879af92e/attachment.html>