<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>David is correct. </div><div><br></div><div>I'd like to add one thing, it's a tie only if the pattern itself is the same, otherwise, there's the issue of a more unique pattern. </div><div><br></div><div>Also, We have, what I like to call, a modified device/line approach. </div><div><br></div><div>We allow all possible PSTN access on the device based on patterns that separate calls out so that they can be filtered (blocked) on the line. For example, we allow toll free calls on the device, so blocking long distance on a line won't block toll free. We also have a '900' exception list we can administer so blocking 900 calls on a line still allows the exceptions through. </div><div><br></div><div>Then, we allow as required access to on net calls at the line. </div><div><br></div><div>In your situation Scott, if all the lines already have 911 access, I'm not sure how you're going to block it without blocking it for hard phones as well. </div><div><br></div><div><br><br>Sent from my iPad</div><div><br>On Dec 10, 2014, at 4:48 PM, David Schulz <<a href="mailto:dschulz@skyline-ats.com">dschulz@skyline-ats.com</a>> wrote:<br><br></div><blockquote type="cite"><div>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<div>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 :</div>
<div><br>
</div>
<div>1. Best match of all partitions in the resulting CSS.... The concatenation of the line and device CSS.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>Hope this helps<br>
<br>
Dave
<div><br>
</div>
</div>
<div><br>
On Dec 10, 2014, at 2:22 PM, Adam Blomfield <<a href="mailto:adman@adman.net">adman@adman.net</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">
<div> 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.<br>
<br>
</div>
-Adam<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Dec 10, 2014 at 12:09 PM, Scott Voll <span dir="ltr">
<<a href="mailto:svoll.voip@gmail.com" target="_blank">svoll.voip@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Lelio has talked about the fact that device and Line combine for a phone total CSS.
<div><br>
</div>
<div>Now which one takes over in the case of an overlap?</div>
<div><br>
</div>
<div>For instance. The line has the 911 patter, and the device has a block 911 pattern.</div>
<div><br>
</div>
<div>Will the call be blocked or placed? </div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>I want to just put a block patter on the device.</div>
<div><br>
</div>
<div>TIA</div>
<span class="HOEnZb"><font color="#888888">
<div><br>
</div>
<div>Scott</div>
<div><br>
</div>
</font></span></div>
<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" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>cisco-voip mailing list</span><br>
<span><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a></span><br>
<span><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br>
</div>
</blockquote>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>cisco-voip mailing list</span><br><span><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a></span><br><span><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br></div></blockquote></body></html>