On 2/14/07, <b class="gmail_sendername">gc</b> <<a href="mailto:garych@unidial.com">garych@unidial.com</a>> wrote:<div><span class="gmail_quote"></span><div> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff"><div><font face="Arial" size="2"><div><font face="Arial" size="2">So you have to hard code each queue name in the
dialplan for an agent to login. What about hundreds of agents login
30-40 different queues? If this is the only way to do it, I will not
use AddQueueMember at all. I do not know the reason for deprecating
AgentCallBackLogin. But I do think remove it without appropriate
replacement is bad idea.</font></div></font></div></div></blockquote><div><br>I said that mine was a contrived example; even for a scenario where one agent always logs into the same two queues each day you'd want to do some kind of database or template driven queue login. Authenticate the agent, then look up the queues they should be in and call AddQueueMember() multiple times.
<br><br>In this respect, AddQueueMember() is no different from AgentCallbackLogin(). It has to be called (via the dialplan, via AGI, via the Manager, whatever) once for each queue that an agent is logging into<br><br></div>
</div>