On 9/7/07, <b class="gmail_sendername">Atis</b> <<a href="mailto:atis@best.eu.org">atis@best.eu.org</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Well, for that case i have a RemoveQueueMember() after Dial, in case<br>of ${DIALSTATUS}!="ANSWERED". That works great, except for agent<br>complaints - that they are logged out from queue :D Would be a bit<br>
better to be able to set agent's status to "Unavailable".<br></blockquote></div><br>This only works if you're using Local channels to bridge calls to agents.<br><br>It doesn't work if you're using AddQueueMember with SIP channels, because the Dial() is implicit, so you have no control over what happens after that implicit Dial() finishes.
<br><br>And yes, I have good reason for using SIP channels. We have externally driven automatic pausing (because the built-in wrapuptime is per-queue and therefore broken for any agent who is assigned to more than one queue), and neither form of Local (with or without /n) perform properly under this configuration.
<br><br>It would be great if you could define arbitrary states in queues.conf, then have dialplan logic to set an agent to given state. If you could indicate in the definition what things a state means (able to take a call, counted as part of ${QUEUE_MEMBER_COUNT()}, etc. that would truly be useful.
<br><br>-- <br>j.