Not necessarily... The same agents could very well be providing support for multiple companies. You wouldn't want an announcement from company A in company B's queues. <br><br>Alex<br><br><div><span class="gmail_quote">
On 1/3/07, <b class="gmail_sendername">Joe Dennick</b> <<a href="mailto:joe@dennick.net">joe@dennick.net</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;">
Yeah, get a Business Process specialist to analyze the client's<br>environment and develop a better solution. 200 queues with only 100<br>agents sounds pretty ludicrous to me!<br><br>On Wed, 2007-01-03 at 14:22 -0600, lenz wrote:
<br>> Hello list,<br>> one of our clients is going to be deploying a system with over 200<br>> differently composed queues and 100 agents. We are going to do a full test<br>> of the viability of this solution before deployment, but I was wondering
<br>> if anyone has experience of such a setup and if there are any obvious<br>> problems or no-nos.<br>> Any suggestion welcomed,<br>> l.<br>><br><br>_______________________________________________<br>--Bandwidth and Colocation provided by
<a href="http://Easynews.com">Easynews.com</a> --<br><br>asterisk-users mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users
</a><br></blockquote></div><br><br clear="all"><br>-- <br>Alex Robar<br><a href="mailto:alex.robar@gmail.com">alex.robar@gmail.com</a>