[asterisk-bugs] [Asterisk 0014643]: Segfaults if queue name is wrong

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Mar 11 09:28:42 CDT 2009


The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=14643 
====================================================================== 
Reported By:                alecdavis
Assigned To:                mmichelson
====================================================================== 
Project:                    Asterisk
Issue ID:                   14643
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     resolved
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!): 179219 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-03-11 04:59 CDT
Last Modified:              2009-03-11 09:28 CDT
====================================================================== 
Summary:                    Segfaults if queue name is wrong
Description: 
Dialplan typo can crash asterisk if queue names don't exist, due to a typo
or a missed change.

queues are really 'itg_queue' and 'itg_queue2'
type is in priority 3.

;Incoming calls to queue 1
exten => 8301,1,Answer()
exten => 8301,2,Queue(itgqueue,hH,,,60)
exten => 8301,3,NoOp(QUEUE1STATUS=${QUEUESTATUS})
exten => 8301,4,Queue(itg_queue2,hH,,,60)
exten => 8301,5,NoOp(QUEUE2STATUS=${QUEUESTATUS})
exten => 8301,6,Voicemail(${EXTEN},u)

====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-11 09:28 svnbot         Status                   assigned => resolved
2009-03-11 09:28 svnbot         Resolution               open => fixed       
======================================================================




More information about the asterisk-bugs mailing list