The goal is to get “ringinuse=no” working as stated in the documentation.
tripwires:
“servicelevel” was one setting that exacerbates the situation, but eliminating it does not solve the problem.
hacky workaround with side effects
call-limit=1
works, but breaks call hold, a vital feature
servicelevel=90
a feature designed to beep agents who are currently on a call, when other are waiting. It might be unexpected, or disliked by a group of queue agents.
also:
call-limit needs to have a definition according to various reports
One system had it’s sip.conf erased by mistake and replaced. This apparently caused the queues to misbehave.
( totally incorrect observations by one user )
An agent is on a call, and new incoming queue calls now initiate a beeping sound that the agent hears.
Nothing was changed in the queues.conf, and I made sure that:
ringinuse=no
also in sip.conf:
type=friend
canreinvite=yes
qualify=yes
Are there any other settings that could be causing this error? There should not be any reason that agents are hearing a beep.
OrderlyQ have been working on this and similar problems:
Are your agents’ phones still ringing when they are already on a call?
If so you might want to read this.
Following reports from several Asterisk users that they’re having
problems with ringinuse=no not working when Local Channels are used to
provide hot-desking support within the Asterisk Queue() function, we
have developed a very easy fix for this that is now documented in our
popular Asterisk Queues Tutorial.
You don’t need to do anything fancy with STATEINTERFACE to get this to
work, and it also works with all Asterisk phone types, including SIP and
DAHDI channels.