[asterisk-bugs] [Asterisk 0016788]: [regression] Realtime agents Device state always Not in use

[Asterisk Bug Tracker]

The following issue requires your FEEDBACK. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16788 
====================================================================== 
Reported By:                sum
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16788
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.2.2 
JIRA:                        
Regression:                 Yes 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-02-08 19:16 CST
Last Modified:              2010-02-09 08:49 CST
====================================================================== 
Summary:                    [regression] Realtime agents Device state always Not
in use
Description: 
I have SIP realtime agents that are always in use, this dind't happend on
previous SVN and RC versions 
====================================================================== 

---------------------------------------------------------------------- 
 (0117885) lmadsen (administrator) - 2010-02-09 08:49
 https://issues.asterisk.org/view.php?id=16788#c117885 
---------------------------------------------------------------------- 
Please provide the information required to reproduce this issue, including
the queues.conf, sip.conf, and extensions.conf files (relevant parts).

It may also be useful to see the console output with debugging enabled;
please provide the output for a working version (and specify which version
worked, and which one doesn't) and a non-working version.

You may be able to look at the SVN log to determine where this may have
gotten broken as well. Take the last working version, then you can look
through the logs and step forward in revisions from subversion to test
specific revisions.

If you can track down the exact commit that causes this issue, then it is
likely to get fixed a lot faster.

Thanks! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-09 08:49 lmadsen        Note Added: 0117885                          
2010-02-09 08:49 lmadsen        Status                   new => feedback     
======================================================================