Posted: Tue Oct 18, 2005 4:35 am Post subject: SV: [Asterisk-Users] Queues and call waiting indication
Hi,
This issue has been discussed probably a million times on every asterisk forum in the world and I have the same problem too. Another problem you would have with the agents is that when they make an outgoing call they are not regarded as "busy" by asterisk and it sends more calls to the agent if it has call waiting enabled.
This behaviour is totally senseless since the whole purouse of queues is to _queue_ the callers until the agent is available. "available" usually means "not on the phone" -- whether or not it's an incoming or outgoing call.
I "solved" this problem by using single-line clients and phones where you can turn off call wating.
I have 3 queues with 10 operators, and I'm running into some trouble because when all the operators are busy answering call asterisk still sends them more, resulting in a "beep beep" (call waiting) over and over again in Xlite audio.
An easy solution woud be the use of a "single line" user agent, like firefly, still this behaviour does not make any sense to me.
I tried using incominglimit and outgoinglimit in my sip.conf, even if they are deprecated: no luck.
Here is a sample from my queues.conf, something wrong in my setup maybe ?
Posted: Tue Oct 18, 2005 4:48 am Post subject: SV: [Asterisk-Users] Queues and call waiting indication
Quote:
This behaviour is totally senseless since the whole purouse of queues is > to _queue_ the callers until the agent is available. "available" usually > means "not on the phone" -- whether or not it's an incoming or outgoing > call.
Agree!
Quote:
I "solved" this problem by using single-line clients and phones where > you can turn off call wating.
Can you suggest me a SIP or IAX phone with just one line that can also open url's passed by asterisk ?
I have 3 queues with 10 operators, and I'm running into some trouble > because when all the operators are busy answering call asterisk still > sends them more, resulting in a "beep beep" (call waiting) over and over > again in Xlite audio.
An easy solution woud be the use of a "single line" user agent, like > firefly, still this behaviour does not make any sense to me.
I tried using incominglimit and outgoinglimit in my sip.conf, even if > they are deprecated: no luck.
Here is a sample from my queues.conf, something wrong in my setup maybe > ?
This issue has been discussed probably a million times on every asterisk forum in the world and I have the same problem too. Another problem you would have with the agents is that when they make an outgoing call they are not regarded as "busy" by asterisk and it sends more calls to the agent if it has call waiting enabled.
This behaviour is totally senseless since the whole purouse of queues is to _queue_ the callers until the agent is available. "available" usually means "not on the phone" -- whether or not it's an incoming or outgoing call.
I "solved" this problem by using single-line clients and phones where you can turn off call wating.
Actually this can simply be solved in your dialplan.... Just use the
setgroup/checkgroup values, and use the AgentCallbackLogin instead of
AgentLogin ....
This is what I used, and it seems to work quite well so far... well, I
haven't actually added the bits for the outbound calls yet on my own
system, but I've done it on others, and they seem to be quite happy with
it...
> Hi,
>
> This issue has been discussed probably a million times on every
> asterisk forum in the world and I have the same problem too.
> Another problem you would have with the agents is that when they
> make an outgoing call they are not regarded as "busy" by asterisk
> and it sends more calls to the agent if it has call waiting enabled.
>
> This behaviour is totally senseless since the whole purouse of
> queues is to _queue_ the callers until the agent is available.
> "available" usually means "not on the phone" -- whether or not
> it's an incoming or outgoing call.
>
> I "solved" this problem by using single-line clients and phones
> where you can turn off call wating.
>
Actually this can simply be solved in your dialplan.... Just use the
setgroup/checkgroup values, and use the AgentCallbackLogin instead of
AgentLogin ....
This is what I used, and it seems to work quite well so far... well, I
haven't actually added the bits for the outbound calls yet on my own
system, but I've done it on others, and they seem to be quite happy
with
it...
Can you provide some more specifics? Maybe an example for the
dialplan? Does this keep the queue from sending multiplecalls to
agents who have call waiting enabled?
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum