[asterisk-bugs] [Asterisk 0011498]: RINGNOANSWER queue_log without a member name

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11498 
====================================================================== 
Reported By:                hloubser
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   11498
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           1.4.15  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!): 90163 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             12-10-2007 02:53 CST
Last Modified:              12-20-2007 18:55 CST
====================================================================== 
Summary:                    RINGNOANSWER queue_log without a member name
Description: 
Some RINGNOANSWER events in the queue_log are missing member names in
around 10% of the calls to rna() in app_queue.c . SVN 90163, OS Ubuntu
7.10.
====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 12-20-07 18:55  
---------------------------------------------------------------------- 
I thought I'd give an update regarding this.

This bug has pointed out a basic deficiency in the queue application. To
put things quite simply, the reason that no membername is printed on those
particular RINGNOANSWER situations is that the queue has no way of knowing
what the membername should be. If you want a longer explanation as to why,
I can provide it, but it'll be rather long and I might not make any sense
when I explain it.

That being said, logically you would think that the queue SHOULD know
exactly which member it was that it tried to ring and who did not pick up.
I THINK I may have a fix which will not be too invasive, but I will need to
test quite extensively before I can say for sure that my idea for a fix
will work.

I'd also like to point out for the record that this bug has called my
attention to the fact that when using the "ringall" strategy, it is
completely random which member's name will show up in the RINGNOANSWER
queue log entry if no one picks up the phone. My solution to the reported
bug would also fix this deficiency as well. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-20-07 18:55  putnopvut      Note Added: 0075777                          
======================================================================