The main problem i see with thgis is that with old-school agents, you
could easily have association with multiple queues. And that was quite
useful.
l.
2009/5/16 David Anthony O Reilly oreil...@tcd.ie
Hi Jim
Thanks for your code!! I see you use the Voicemail system to authenticate,
have you
Lenz Emilitri schrieb:
The main problem i see with thgis is that with old-school agents, you
could easily have association with multiple queues. And that was quite
useful.
2009/5/16 David Anthony O Reilly oreil...@tcd.ie
Hopefully somebody out there has managed to create an agent
Hi Carlos
Agentcallbacklogin was deprecated in Asterisk 1.4 and eliminated from
1.6 so you now need to use Dynamic Agents. Although they claim that is
is simple enough to replace that functionality with dial plan code I
have yet to see a one line example that replaces everything the
Hi Jim
Thanks for your code!! I see you use the Voicemail system to authenticate,
have you ever managed to avoid that as I don't use voicemail at all and I am
thinking if I use that solution I will need to set up a voicemail for all
the queue members just to get them to log in.
hehe What were
David Anthony O Reilly wrote:
hehe What were the developers thinking by removing the old system! It
worked perfect!! and by the looks of it nobody has ever recovered from
the command removal unless they hack around with the voicemail system.
I think the best solution is to either use an AGI
Where do you want to get the value that agent uses to validate?
You can do your own code to do the validation.
Get the value from where ever and then do a read and compare the value read
with the value you retrieved from where ever. If there is match you are
done if no match say error, maybe
