IMHO, one of the major advantages of ACBL is that the set of queues is statically defined, so at the dialplan level you do not have to keep track of the set of queues an agent is enabled on. l.
2009/11/3 Mariano Lecuona <[email protected]> > My mental plan orginilly was: > > 1.- Creating a macro that acceps ARGs like. > a.- agent > b.- queue/s > > In the macro we could have the voice respose for the loging. I am using on > 1.4 the following procedure. > > * the agents call to 21<Agentid> to loging, and it is promt just for the > passwd > * the agents call to 22<Agentid> to logoff > > using the same philosofy we could implement some easy marco that only ask > for the password and: > > 1.- sets the astdb > 2.- sets the globals "AGENTBYCALLERID_XXXXX=XXXX" > 3.- adds the agent to the queues. > > > Let me work deeper on this idea and see what comes up. > > ML > > 2009/11/2 Lenz Emilitri <[email protected]> > >> We were thinking about doing something similar as well. A lot of people >> are asking for this. If there is anybody else interested, we could share the >> load.... >> >> I was thinking about creating a context like @agents, so that when you do >> the log-on you basically add Local/1...@agents as a member of the queue. >> When you ring it, it basically looks up for the actual device in AstDB and >> dials it like: >> >> Queue -> (member) Local/1...@agents -> (astdb) SIP/234 >> >> I think that we should be able to forward channel state as well (using >> hints? I've never done it) so that app_queue does not try dialling agents >> that are busy. >> >> I was thinking about storing queue-agent associations into config strings, >> and/or AstDB, and/or http over curl. And yes, ideally it should work fine on >> 1.4's as well.... >> >> Things that should be working from version one: >> - logging compatible with older asterisk's >> - authentication using Voicemail >> -.plug and play on most systems >> - channel states >> - pause/unpause with pause codes >> - ...you tell me.... >> >> Anybody interested? >> l. >> >> >> 2009/10/30 Mariano Lecuona <[email protected]> >> >>> Hi all, >>> >>> I would like to know if there is any application replacement for the >>> AgentCallBackLogin() from asterisk 1.4 on asterisk 1.6. I know, from what >>> I've read that the call back login agent can be done using a smart dialplan >>> as showed on the docs. But I cannot thinks a flexible dialplan for a dinamic >>> reassignation of agents to different queues every day. >>> >>> Thanks in advance. >>> >>> Mariano >>> >>> _______________________________________________ >>> -- Bandwidth and Colocation Provided by http://www.api-digital.com -- >>> >>> asterisk-users mailing list >>> To UNSUBSCRIBE or update options visit: >>> http://lists.digium.com/mailman/listinfo/asterisk-users >>> >> >> >> >> -- >> Loway - home of QueueMetrics - http://queuemetrics.com >> >> >> _______________________________________________ >> -- Bandwidth and Colocation Provided by http://www.api-digital.com -- >> >> asterisk-users mailing list >> To UNSUBSCRIBE or update options visit: >> http://lists.digium.com/mailman/listinfo/asterisk-users >> > > > _______________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > -- Loway - home of QueueMetrics - http://queuemetrics.com
_______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
