Your message dated Thu, 03 Jan 2019 17:22:21 +0100
with message-id <[email protected]>
and subject line Closing bugs reported against unsupported versions
has caused the Debian Bug report #744745,
regarding queuerules doesen't work as expected after upgrade
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
744745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744745
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: asterisk
Version: 1:1.6.2.9-2+squeeze12
Don't know when this happened, but some of the last updates has changed how
asterisk behaves with queue-rules.
Previous this worked as following:
The members with penalty 1 rang for 20 secounds, then members with penalty 1+2
rang for the next 60 secounds, then 1+2+3 rang and so on.
How it works now:
The members with penalty 1 are ringing until timeout (about 120 secounds), then
only members with penalty 2 are ringing etc.
It doesen't seem that the queuerules works at all.
MMP2*CLI> queue show rules
Rule: nyteknisktest
After 20 seconds, adjust QUEUE_MAX_PENALTY to 2 and adjust
QUEUE_MIN_PENALTY to 1
After 60 seconds, adjust QUEUE_MAX_PENALTY to 3 and adjust
QUEUE_MIN_PENALTY to 1
After 120 seconds, adjust QUEUE_MAX_PENALTY to 4 and adjust
QUEUE_MIN_PENALTY to 1
MMP2*CLI> queue show nyteknisktest
nyteknisktest has 0 calls (max unlimited) in 'ringall' strategy (39s holdtime,
177s talktime), W:0, C:18, A:0, SL:0.0% within 0s
Members:
SIP/xxxxxx07 with penalty 1 (Not in use) has taken 15 calls (last was
6720 secs ago)
SIP/xxxxxx05 with penalty 2 (Not in use) has taken 3 calls (last was
334594 secs ago)
SIP/xxxxxx10 with penalty 3 (Not in use) has taken no calls yet
SIP/xxxxxx03 with penalty 4 (Not in use) has taken no calls yet
SIP/xxxxxx02 with penalty 4 (Not in use) has taken no calls yet
SIP/xxxxxx04 with penalty 3 (In use) has taken no calls yet
SIP/xxxxxx06 with penalty 3 (Not in use) has taken no calls yet
SIP/xxxxxx08 with penalty 4 (Not in use) has taken no calls yet
SIP/xxxxxx09 with penalty 4 (Not in use) has taken no calls yet
SIP/xxxxxx12 with penalty 3 (Not in use) has taken no calls yet
No Callers
extentions.conf
exten => 1,1,Verbose(Teknisk)
exten => 1,n,Set(QUEUE_MIN_PENALTY=1)
exten => 1,n,Set(QUEUE_MAX_PENALTY=1)
exten => 1,n,Queue(nyteknisktest)
exten => 1,n,Hangup()
queuerules.conf
[nyteknisktest]
penaltychange => 20,2,1
penaltychange => 60,3,1
penaltychange => 120,4,1
queues.conf
[nyteknisktest]
musiconhold = ourmoh
defaultrule = nyteknisktest
strategy = ringall
periodic-announce = ringetilbake
periodic-announce-frequency = 0
announce-frequency = 0
announce-holdtime = no
announce-position = no
context = tekniskcallback
timeout = 240
timeoutrestart = no
retry = 0
member => SIP/xxxxxx07,1
member => SIP/xxxxxx05,2
member => SIP/xxxxxx10,3
member => SIP/xxxxxx03,4
member => SIP/xxxxxx02,4
member => SIP/xxxxxx04,3
member => SIP/xxxxxx06,3
member => SIP/xxxxxx08,4
member => SIP/xxxxxx09,4
member => SIP/xxxxxx12,3
--- End Message ---
--- Begin Message ---
Dear user,
thanks for helping us making Debian better by reporting this bug.
Unfortunately it could not be dealt with in time. We lack the manpower
to check all currently open bugs whether they still apply for the
current version. Therefor we are closing old issues hoping that the
documented problem has already been resolved.
If you can still reproduce this issue with a supported version of
Debian/Asterisk
- 13.14 in Debian Stretch
- 13.23.1 in Debian Buster/Sid (right now)
- 16.1.0 in Experimental (soon in buster/sid I hope)
please feel free to reopen this bug.
Thanks,
Bernhard
--- End Message ---
