C. Chad Wallace cwall...@lodgingcompany.com writes:
OK, I decided to write it up in AEL. It's incomplete and untested, but
it probably gets the idea across a little better.
context agentcalls {
_2XX = {
Set(AGENT=${EXTEN}); // Assuming agent ID is extension.
if
Benny Amorsen benny+use...@amorsen.dk writes:
Would it perhaps work to simply Wait(30) if the call is rejected by the
phone? If the Queue assumes that the phone is busy for those 30 seconds,
I have accomplished my goal. It's worth a shot.
This works! Actually I tried out Wait(1000), but that
At 11:23 AM on 16 Oct 2009, Benny Amorsen wrote:
I was going in the same direction at the end of my first mail, but I
hadn't written any code. There is a problem though: The Queue
application will keep sending calls to the Local channel, which have
to be rejected, over and over.
Would it
C. Chad Wallace cwall...@lodgingcompany.com writes:
It would only be trying one agent at a time for each waiting queue
member...
Would it? Almost all our queues are on a ringall strategy.
I don't know how expensive it is to open and close a Local channel and
do a DB lookup, but I wouldn't
At 7:35 PM on 16 Oct 2009, Benny Amorsen wrote:
C. Chad Wallace cwall...@lodgingcompany.com writes:
Also, if there is another agent available, the caller would be
connected immediately, and it wouldn't have to make any more
attempts. With the Wait() solution, that caller would be
Elliot Otchet elliot.otc...@callingcircles.com writes:
Have you tried autopause=yes in your queue configuration? You can then
unpause the member by either the dialplan (e.g. having the cell phone
user log back in) or using an AMI based program to change the
paused state.
You can read more
Lenz Emilitri lenz.lo...@gmail.com writes:
You could configure them as agents and have them log off automatically
after a while they're not responding.
Agents have to log in and wait for calls though, don't they? There used
to be AgentCallbackLogin, but that has been replaced by dialplan code
That shouldn't be too hard to accomplish. If you've got the addons (and mysql)
installed you could store them in a MySQL table (timestamp, device) and have a
cron job set to run at X frequency that un-pauses the queue members via AMI.
Don't want to go to MySQL? Use system() to 'touch' files
Elliot Otchet elliot.otc...@callingcircles.com writes:
That shouldn't be too hard to accomplish. If you've got the addons
(and mysql) installed you could store them in a MySQL table
(timestamp, device) and have a cron job set to run at X frequency that
un-pauses the queue members via AMI.
At 3:37 PM on 15 Oct 2009, Benny Amorsen wrote:
Perhaps the problem could be restated in a different way: After a
queue member rejects a call (instead of just not answering), the
queue should wait X amount of time before sending the next call.
Queues.conf has a million settings, but I can't
At 11:32 AM on 15 Oct 2009, C. Chad Wallace wrote:
At 3:37 PM on 15 Oct 2009, Benny Amorsen wrote:
Perhaps the problem could be restated in a different way: After a
queue member rejects a call (instead of just not answering), the
queue should wait X amount of time before sending the
You could configure them as agents and have them log off automatically after
a while they're not responding.
l.
2009/10/14 Benny Amorsen benny+use...@amorsen.dkbenny%2buse...@amorsen.dk
We have the possibly rather unique setup where we have cell phones
posing as SIP devices. The SIP
What is the command to log off the agents ?
Thx
On Wed, Oct 14, 2009 at 6:45 PM, Lenz Emilitri lenz.lo...@gmail.com wrote:
You could configure them as agents and have them log off automatically
after a while they're not responding.
l.
2009/10/14 Benny Amorsen
Have you tried autopause=yes in your queue configuration? You can then unpause
the member by either the dialplan (e.g. having the cell phone user log back
in) or using an AMI based program to change the paused state.
You can read more about the latter here:
14 matches
Mail list logo
