[asterisk-bugs] [Asterisk 0012683]: Queue timeout not overided by the timeout parameter on the Queue command

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12683 
====================================================================== 
Reported By:                daren
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   12683
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.19 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             05-19-2008 07:33 CDT
Last Modified:              05-20-2008 02:45 CDT
====================================================================== 
Summary:                    Queue timeout not overided by the timeout parameter
on the Queue command
Description: 
Hello, 

I didn't find such issue, neither in mantis, neither in changelog, so i
hope i don't create a duplicate request.

I'm actually using an asterisk 1.4.19.1 on the one i found a very little
bug. In fact the timeout option of the "Queue" command doesn't override the
value set in the config file...

Example:

In one of my scenari, the timeout parameter in 
"exten => s,5,Queue(service-clients|n||sc/sc-scstellatelecom|180)" is
ignored, the timeout value used is the one found in the queues.conf

Here are the extract of the config files.

; queues.conf extract
[service-clients]

musiconhold = default
strategy = ringall

member => SIP/mt1
member => SIP/mt4
member => SIP/mt5

timeout = 180
retry = 5

;extensions.conf extract

[sc_menu_principal]
exten => s,1,GotoIfTime(20:01-7:59|mon-sat|*?sc_ferme_rappel,s,1)
exten => s,2,NoOp()
exten => s,3,GotoIfTime(*|sun|*?sc_ferme_rappel,s,1)
exten => s,4,PlayBack(sc/veuillezpatienter)
exten => s,5,Queue(service-clients|n||sc/sc-scstellatelecom|180)
exten => s,6,Queue(bureau|n||sc/sc-scstellatelecom|90)
exten => s,7,PlayBack(sc/aucundispo)
exten => s,8,BackGround(sc/rappel)
exten => s,9,WaitExten()
exten => 1,1,Macro(id-mail,Service commercial particuliers)
exten => 2,1,PlayBack(sc/aurevoir)
exten => 2,2,Hangup()


Thanks a lot!

Daren
====================================================================== 

---------------------------------------------------------------------- 
 daren - 05-20-08 02:45  
---------------------------------------------------------------------- 
Oups, it's true, i knew the difference, i made a mistake in the
understanding of my problem.

If, now, i'm right, the normal "global" timeout is queues.conf timeout by
the retry ( global_timeout = conf_timeout*conf_retry if
cmd_timeout>=global_timeout else global_timeout=cmd_timeout ).

But davidw seems to be right, the first queue was heavily used when it was
leaved. So it might be related to that, but are you ok to tell that it's
not normal; that the queue shouldn't be left before its end?

Do you have an idea on how to force asterisk to use the queue until the
cmd_timeout or until the end of the conf_timeout*conf_retry ? 

What do you think of adding a special queue member with a infinite
wait/ring through a LOCAL extension?

I'll try, who knows... 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-20-08 02:45  daren          Note Added: 0087054                          
======================================================================