[asterisk-bugs] [Asterisk 0005374]: [patch] Asynchronous generation of outgoing frames when timing device available

[Asterisk Bug Tracker]

The following issue has been set as RELATED TO issue 0015932. 
====================================================================== 
https://issues.asterisk.org/view.php?id=5374 
====================================================================== 
Reported By:                cmantunes
Assigned To:                oej
====================================================================== 
Project:                    Asterisk
Issue ID:                   5374
Category:                   Core/General
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     closed
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): trunk 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2005-10-03 21:25 CDT
Last Modified:              2009-11-19 09:28 CST
====================================================================== 
Summary:                    [patch] Asynchronous generation of outgoing frames
when timing device available
Description: 
One common complain from Asterisk users is its inability to generate
outgoing RTP packets when incoming packets stop arriving, due to silence
supression, for example. This is due to the fact that Asterisk generates
outgoing frames in the same function where incoming frames are processed
(ast_read). When this routine isn't called, outgoing framnes aren't
generated either (well, unless a CNG frame arrives, which served as
inspiration for this patch.)

This patch basically forces Asterisk to always generate outgoing frames
asynchronously when a timing device is available (zaptel). On the other
end, if a timing device isn't available, Asterisk will fall back to
generate outgoing frames synchronously, in ast_read.

This patch was only tested for a few hours with a couple of SIP clients.
As such, I cannot guarantee in any way, shape of form that it will work for
everybody. It is my hope, however, that people test this patch and report
any possible issues.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0005184 [request] RFC3389 Support requested. (w...
related to          0004252 Increasing delay over time on non-Zap c...
related to          0015932 Make internal_timing on by default
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-11-19 09:28 lmadsen        Relationship added       related to 0015932  
======================================================================