AddQueueMember Best Paractice for Dynamic agent logins

[perlmaster]

What is the best practice/approach to dynamically login agents (to multiple queues) AND have their real name show up in the 'Agent' field of Realtime Monitoring as is done when using AgentCallbackLogin?

I've done a little searching through the archives, and have seen a few similar questions, but haven't found a solution that fully meets my needs.

I'm running 2 call centers where agents can roam and login from any extension.

Asterisk 1.4.24  (preparing to upgrad to 1.6)
Queumetrics (2 installations) 1.5.1 and 1.5.4
mysql 4.1.20 (I know, it's a little old)

[QueueMetrics]

i think that the best approach would be to simulate agentcallbacklogins through a context and storing the actual extension used in AstDB.

Like:
- when you log in, you keep track that agent 103 is at extension SIP/202
- you add Local/103@agents as a member to the queue
- when you dial Local/103@agents, it looks up agent 103 in astdb and finds that he is at SIP/202, so he dials it

[perlmaster]

Thanks, that sounds like a good suggestion.

I'm not in the office today, but will run a few tests tomorrow.  However, I'm not sure how to do the astdb calls.

I'm currently testing the example from here, which might be more complex than I need.
http://etel.wiki.oreilly.com/wiki/index.php/Asterisk_Queues_using_AddQueueMember

Can you show me how I would adjust that to do what you suggest, or maybe a more simplified example?

[QueueMetrics]

There is work going on here: http://groups.google.com/group/agentcallbacklogin-replacement

[perlmaster]

There is work going on here: http://groups.google.com/group/agentcallbacklogin-replacement

Thanks, but not much help there, at least not at the moment.

I haven't had time to try your idea...I've been busy installing a new asterisk system in one of our stores.

[QueueMetrics]

Yes unfortunately there is still not a complete and general purpose solution.

[perlmaster]

Is the lack of a general purpose solution due to queuemetrics lagging in updating the application, or due to asterisk itself?

[QueueMetrics]

QM fully supports any Asterisk login - the problem is that nobody has yet prepared a standard drop-in replacement for AgentCallBackLogin to be used with Asterisk 1.6's, so everybody is programming their own call-center differently.

If you look at the support files that come with Asterisk they basically teach you how to brew your own solution.

[QueueMetrics]

See also. http://forum.queuemetrics.com/index.php?topic=728.0