<div>Why would you want to do this? Seems like it would be a better design to deny as close to the user as possible (lower over head).</div>
<div> </div>
<div>scott<br><br></div>
<div class="gmail_quote">On Feb 10, 2008 9:33 AM, Lelio Fulgenzi <<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div bgcolor="#ffffff">
<div><font face="Arial" size="2">Something we were able to do on our old pbx is to match class of service across trunks, so basically we were able to map one class of service to another and have some flexibility in passing permissions across from one system to another. </font></div>
<div><font face="Arial" size="2"></font> </div>
<div><font face="Arial" size="2">Is there any way to do this with two callmanager clusters? I'd like to be able to add a simple 9.@ route pattern on one cluster and have that users class of service cross the trunk and have the final cluster deny/allow the call.</font></div>
<div><font face="Arial" size="2">--------------------------------------------------------------------------------<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ <br>"Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo buffalo." WJR<br></font></div></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>