[asterisk-bugs] [Asterisk 0017348]: DTMF (info) is no longer passed through after 180 seconds

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17348 
====================================================================== 
Reported By:                jacco
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17348
Category:                   General
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.2.8-rc1 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-05-17 08:36 CDT
Last Modified:              2010-05-19 06:13 CDT
====================================================================== 
Summary:                    DTMF (info) is no longer passed through after 180
seconds
Description: 
DTMF (info) is no longer passed through after 180 seconds.
180 seconds after pickup DTMF is no longer passed trough to the other
side.
The DTMF is recieved correctly by asterisk

also SendDTMF() doesn't send any DTMF 
====================================================================== 

---------------------------------------------------------------------- 
 (0122130) jacco (reporter) - 2010-05-19 06:13
 https://issues.asterisk.org/view.php?id=17348#c122130 
---------------------------------------------------------------------- 
when I keep sending DTMF tones with an interval smaller then the 180seconds
nat timeout, actualy doing a manual NAT keep-alive bij sending SIP-info
packet, DTMF keep working perfectly even afther the 180seconds NAT
timeout.

This is because qualify timers only start on registration and so will not
send any nat keepalive to unregisterd phones.(i found this on the web
somewhere; I did not verify)

I guess the timers should also be started when an unregisterd phone makes
a call or makes a seperate timer for nat-keepalive that also works for
unregisterd phones 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-19 06:13 jacco          Note Added: 0122130                          
======================================================================