The answer is to create linked AC hunt groups with the first being circular and the second being top down<br><br>members of first hunt group<br>AC user 1<br>AC user 2<br>AC user 3<br>pilot of AC-HUNT2<br><br>members of second hunt group
<br>AC user 1<br>AC user 2<br>AC user 3<br>voicemail<br><br><br>Justin<br><br><div><span class="gmail_quote">On 7/13/07, <b class="gmail_sendername">Carter, Bill</b> <<a href="mailto:bcarter@sentinel.com">bcarter@sentinel.com
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div><font face="Tahoma" size="2">I have Attendant Console setup with the 3 users
listed (by username not DN) and then an "always route" member for a Unity Call
Handler.</font></div>
<div> </div>
<div><font face="Tahoma" size="2">Reading the documentation, it says I can't do
longest idle because the "always route member" maybe the longest idle.
</font></div>
<div> </div>
<div><font face="Tahoma" size="2">Documentation does not say the same for
circular. Do I still have the same restriction with the "always route"
member still potentially getting calls when AC users are logged
in??</font></div>
<div> </div>
<div> </div></div>
<br>_______________________________________________<br>cisco-voip mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" 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>