similar to: Using Dynamic Groups instead of AgentCallbackLogin - how to log which agent took the call?

I am developing an ACD front end using Asterisk 1.2.14. I heard that AgentCallBackLogin will be deprecated in future version of *. Is this true? If it is, how can I use AddQueueMember to replace AgentCallBackLogin? I mean to login an agent in multiple queues at once. I have multiple queues and a lot of agents defined in queues.conf and agents.conf. Each agent may login more than one queue. It

Hi i have problem with AddQueueMember logic. I need login Agent(Member) in asterisk. use this option: for example: AddQueueMember(queuetest,SIP/ekiga,10,,Agent/13) and now i want to call to this Agent: exten => _1XX,1,Dial(Agent/${EXTEN:1}) call to 113 and asterisk should call to Agent => 13 on interface SIP/ekiga. This doesn't work, How can i do this on Asterisk 1.4(not

Hi, I'm currently migrating to 1.4 and have problems changing deprecated AgentCallbackLogin to AddQueueMember. I have dynamic queues and dynamic agents (MySQL Realtime), and pseudo-dynamic agents.conf (with huge amount of possible agent numbers). Agent login is done trough manager API: * AgentCallbackLogin * QueueAdd In 1.4 seems AddQueueMember can do all the same, but there is no such

Hi All, I'm having trouble setting up a queue: I'm using AgentCallBackLogin to login in the queue, but: 1 - When an agent answer the call and another call arrive his phone rings again. 2 - When no there are no one answer the queue the system goes to voicemail of agent 1234 I'm using asterisk-1.2.0-beta1. My configuration is below, Any ideas? Many thanks, Joao Antunes

sorry, was only for users list... Hi Kevin, Hi list, you are right, acting now is not needed, when callbacklogin will be removed anywhere in future... But thinking how to realice alternatives can't be so wrong. Callbacklogin gives a very simple way to use more queues for one agent, which only has to logon to only one system. No need to make dbs or tables for saving, where the agent has to be

As I understand it, you'd enter the extension at which you wish to be called back at, your 9665 has nothing to do with it. Instead of dialling 28 you could dial 9665 and that would add that SIP phone as an agent to the cytelcs queue. Steve -----Original Message----- From: Harold Workman [mailto:hworkman@cytelcom.com] Sent: 22 June 2004 18:54 To: asterisk-users@lists.digium.com Subject:

Good morning?... I'm?using?Asterisk?1.4.40?AgentCallbackLogin?in?a?Call Center.?What?is?happening?isthat?when the?Call?Center?has more?than 15?simultaneous calls?the?login application?isextremely?slow to?fall into?the?low?priority,?ie, the?agent?can?log in,?but?takes about 1minute to?drop?in?priority?below.?.. I've tried?to recompile?the?asterisk, I

Hi all! My problem is that calls being placed in the queue, and are waiting while the agents are busy, when an agents is then free they gets connected to the agent but there is silence (no voice). If a caller has not to wait in the queue, there is no problem. My agents have an iax2 client, and imcoming calls are over SIP. queue.conf: persistentmembers=yes autofill=yes ringinuse=no

When I use AgentCallbackLogin() function to login an agent, I got following warning message saying the agent is not valid for auto login while my other extensions work fine for this function. Does anybody know why? This extension has the same settings as the other ones like agents.conf and queues.conf. Here is the message from asterisk: -- Executing

I've been working on setting up a few queues and agents for use in our upcoming call center. Agents can log in and customers can call in and be routed properly, but I've run into one strange issue. When an agent dials 98 to login the "agent-incorrect" file is played, then the agent can login as normal. Searching the archives I found this issue brought up in Feb '04 :

Hello all, I've seen that the application AgentCallbackLogin()has been set to deprecated in version 1.4. So I've done some tests based on the tutorial "queues-with-callback-members.txt" coming with version 1.4. What's not clear for me is what is happening to agents.conf, it seems that it's no longer needed, and I have to define my agents using variables in

When a caller in the queue is connected to an agent, the call is placed to the extension and context specified using Agentcallbacklogin. This allows for me to add extra things to the diaplan *before* calling the agent. Now, I want to be able to use a device, rather than agents. So I can use addQueueMember and add my SIP device. However, I still want to do a couple of things before the device

First off this is not my work for extensions.conf it is modified from http://leifmadsen.wordpress.com/2009/07/15/migrating-from-agentcallbackl ogin-to-standard-dialplan-methods-part-1/ So credit to Leif Madsen <http://www.leifmadsen.com> But as to my question [AgentLogin] ;A replaced version of AgentCallbackLogin() using a GoSub() ; exten =>

Hi, I'm confused with agents and queues in Asterisk. If I use AddQueueMember() then "show queues" shows the agents that I have logged into the queue... however the agent ID has to be the extension the agent is sitting at ... kinda useless for stats tracking. If I use AgentCallbackLogin() then "show queues" shows no agents logged in, but it works and "show

Can anyone confirm that the feature listed below works? I'm using AgentCallbackLogin and it never seems to log the agent off if they don't answer. /etc/asterisk/agents.conf ; Define autologoff times if appropriate. This is how long ; the phone has to ring with no answer before the agent is ; automatically logged off (in seconds) ; autologoff=15 -- Go to

Has anyone observed a problem where using Local channels with AddQueueMember results in missing TRANSFER events? Right now I'm using straight SIP channels when I call AddQueueMember(). I'm contemplating moving to Local channels because the non-state-based wrapuptime blows when you have a channel in multiple queues (they can hang up and get a call immediately so long as it's from a

I am using AgentCallbacklogin to logon agents. I am trying to avoid agents being logged in more than once in different extensions (is this a bug?) by passing the callerid to the AgentCallbacklogin funtcion as an option. The problem is that by doing this, agents are not asked for an extension and they cannot logoff (by pressing the #). Any ideas how can agents logoff? -------------- next part

Hello everyone! I am currently in the middle of writing an article on converting from AgentCallbackLogin() dialplan application (which is deprecated as of 1.4, and removed in the 1.6.x series of Asterisk) to using the AddQueueMember(), and other dialplan based methods of performing the same functionality. However, after looking at the AgentCallbackLogin() application, it seems there is a

Can someone tell me why this is not valid... [start] exten => 1000,1,Answer exten => 1000,2,Wait,1 exten => 1000,3,AgentcallbackLogin(1000||2000@Local) exten => 2000,1,Macro(DialProxy,115551212) exten => 3000,1,Queue(testq||||45) while this is: [start] exten => 1000,1,Answer exten => 1000,2,Wait,1 exten => 1000,3,AgentcallbackLogin(1000||2000@start) exten =>

Which kind of transfer do you use? Try using the # transfer. Hope that helps.. Guido Hecken -----Urspr?ngliche Nachricht----- Von: Diego Magalh?es [mailto:diego@redetaho.com.br] Gesendet: Mittwoch, 2. Februar 2005 17:21 An: asterisk-users@lists.digium.com Betreff: [Asterisk-Users] AgentLogin / AgentCallbackLogin transfer problem Hello guys, I?m running Asterisk CVS-HEAD-02/01/05-12:22:46 and