[asterisk-bugs] [Asterisk 0013814]: Music On Hold stops sending outbound RTP after first inbound RTP packet is lost

[Asterisk Bug Tracker]

The following issue has been SUBMITTED. 
====================================================================== 
http://bugs.digium.com/view.php?id=13814 
====================================================================== 
Reported By:                funky
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13814
Category:                   Resources/res_musiconhold
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           Older 1.4 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-10-30 15:12 CDT
Last Modified:              2008-10-30 15:12 CDT
====================================================================== 
Summary:                    Music On Hold stops sending outbound RTP after first
inbound RTP packet is lost
Description: 
When the music on hold application is playing music, the outbound RTP
(containing the music) stops after the first incoming packet is lost. Even
if a single packet is lost out of a 30-minute call, the music will stop as
soon as the first packet is lost.

Obviously this is a problem for anyone with a PBX that has music on hold
with long wait times and uses VoIP. Even using a high-quality Internet
connection at our datacenter, we would get our first lost packet after 20
minutes on average. Our application uses a lot of hold music, so this is a
real problem for us.

We have created a patch, which we will post to this bug, which uses
ztdummy to trigger the outbound RTP packets rather than using the inbound
packets to trigger them.

Note that we tested this problem using the very latest version of
Asterisk, and the problem is still there.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-30 15:12 funky          Asterisk Version          => Older 1.4       
2008-10-30 15:12 funky          SVN Branch (only for SVN checkouts, not tarball
releases) => N/A             
======================================================================