Tom Rymes wrote:
That's a good idea, but it does not help when the agent receives a call
from the queue. If an agent has call-waiting enabled (at least on our
7940 Ciscos...) the queue will send another incoming call while the
agent is still on the phone withthe last call sent to them from
Hello,
are you using Asteriks agents or dialing straight to extensions? because
if you are using agents for incoming calls and then you dial straight
out of Asterisk, Asterisk will not know that the agent is busy. One
possible workaround would be to make a call to the agent using a .call
Julian Lyndon-Smith wrote:
Tom Rymes wrote:
That's a good idea, but it does not help when the agent receives a
call from the queue. If an agent has call-waiting enabled (at least
on our 7940 Ciscos...) the queue will send another incoming call
while the agent is still on the phone
Using Asterisk agents.
Not recognizing that an agent has made an outgoing call IS THE PROBLEM.
Only workaround I see is to take the agent out of queue on all outgoing
(and direct dialed incoming) calls and put him back in the queue at the
completion of the call. That seems too kloodgy.
Hence the
Ah, ok, I see what you are getting at.
However, could you not run a macro on connection (to the agents device)
that then pauses the queue member so that no more calls will come
through until they are unpaused ?
Julian.
Troy Settle wrote:
Julian Lyndon-Smith wrote:
Tom Rymes wrote:
Yes, but if an agent is connected through the Agent module even on an
outboiund call, * will consider it unavailable and therefore will not
route calls to it, as if the agent was answering some inbound call.
Just my $0.02 :-)
l.
On Mon, 17 Oct 2005 14:01:27 +0200, J Thomas [EMAIL PROTECTED]
So, I'm looking into using PauseQueueMember and unpause queuemember
How the heck to you get Unpause to run, no matter what, after the call
is over?
The g argument to Dial only works when the called party hangs up.
Using the h extension appears to be doing nothing...
Is there any way we
Given the current state of queues, it does not seem possible to stop ACD
calls coming to a busy agent who has made an outgoing call.
Looks like feature request is the right way to go for this. I am going
to post this on dev mailing list too before making a feature request in
case we have missed
You must specify topqm and upqm what interface you're attempting to pause and unpause. It will not figure that out based on what interface the channel that called the app in the dial plan might have used.
On 10/17/05, Corey Frang [EMAIL PROTECTED] wrote:
So, I'm looking into using PauseQueueMember
It is possible. I do it here and at many other client installs.
Please post your configuration so we can see why it's not working for you.
On 17 Oct 2005 15:31:46 -0400, J Thomas [EMAIL PROTECTED] wrote:
Given the current state of queues, it does not seem possible to stop ACDcalls coming to a
PauseQueueMember works fine, they just never get unpaused if they hang
up the call...
BJ Weschke wrote:
You must specify topqm and upqm what interface you're
attempting to pause and unpause. It will not figure that out based on
what interface the channel that called the app in the dial plan
JT, yes.
Here's how I've done it before for other clients:
On the dialout portion I've changed the dial plan to:
exten = _1NXXNXX,1,GotoIf($[${LEN(${$[AGENTBYCALLERID_${CALLERIDNUM}]})} 2]?2:3)exten = _1NXXNXX,2,PauseQueueMember(|Agent/${$[AGENTBYCALLERID_${CALLERIDNUM}]})exten =
Have you tried the PauseQueueMember application in the dialplan ?
If the agent makes an outbound call, before the dial() call
PauseQueuemember - and UnPauseQueuemember when the call is complete. The
system should not then send any agent calls through, but all other calls
(direct / internal)
That's a good idea, but it does not help when the agent receives a
call from the queue. If an agent has call-waiting enabled (at least
on our 7940 Ciscos...) the queue will send another incoming call
while the agent is still on the phone withthe last call sent to them
from the queue.
Is
One of my friends is facing this problems and I could not find any
solution to that. Hence this post.
In her Asterisk PBX, she has programmed about 10 agents, and strategy is
rrmemory. Everything works fine. When an agent has received an ACD call,
another call is not presented to him as long as
-Users] ACD calls to busy agents
One of my friends is facing this problems and I could not find any solution
to that. Hence this post.
In her Asterisk PBX, she has programmed about 10 agents, and strategy is
rrmemory. Everything works fine. When an agent has received an ACD call,
another call
Setting incominglimit = 1 does not really solve the problem as I had
already mentioned. That practically takes away the call waiting and will
block all incoming calls including direct dialed calls. She does not
want that. Moreover, incominglimit is deprecated too.
-- jt
On Sat, 2005-10-15 at
I don't know how to make this happen, and I don't even think it is
really possible given the current Queue app, but this would be a very
nice feature to have. The queue shouldn't pass a call to an agent if
they are already on a call from the queue, but an incoming call from
another
18 matches
Mail list logo