[asterisk-bugs] [Asterisk 0017545]: [regression] DTMF transfers stop working for queue agents idle > 5 minutes

[Asterisk Bug Tracker]

The following issue requires your FEEDBACK. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17545 
====================================================================== 
Reported By:                maxochoa
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17545
Category:                   Applications/app_queue
Reproducibility:            sometimes
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.33 
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-06-22 11:33 CDT
Last Modified:              2010-06-23 11:16 CDT
====================================================================== 
Summary:                    [regression] DTMF transfers stop working for queue
agents idle > 5 minutes
Description: 
Starting in asterisk 1.4.31 and reproducible with asterisk 1.4.33, if an
agent logs into a queue, takes at least one call, and then sits idle for 5
minutes, most of the time, on the next call taken, DTMF to transfer the
call or hangup the call no longer works. 
====================================================================== 

---------------------------------------------------------------------- 
 (0123757) lmadsen (administrator) - 2010-06-23 11:16
 https://issues.asterisk.org/view.php?id=17545#c123757 
---------------------------------------------------------------------- 
I think we're going to have to get someone else to verify this happens,
because it seems quite improbable for this to have happened (not
impossible, just improbable).

If you go back to 1.4.30 on the exact same machine, does the problem go
away? Can you track down which commit may have introduced this?

I'm hesitant to move this forward unless someone else can verify this
behaviour. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-06-23 11:16 lmadsen        Note Added: 0123757                          
2010-06-23 11:16 lmadsen        Status                   acknowledged =>
feedback
======================================================================