[asterisk-bugs] [Asterisk 0017007]: RTP Timestamp changes after transfer, but SSRC not and the markerbit ist not set.

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Mar 11 10:07:21 CST 2010


The following issue has been SUBMITTED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17007 
====================================================================== 
Reported By:                addix
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17007
Category:                   Channels/chan_sip/Transfers
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.29.1 
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-03-11 10:07 CST
Last Modified:              2010-03-11 10:07 CST
====================================================================== 
Summary:                    RTP Timestamp changes after transfer, but SSRC not
and the markerbit ist not set.
Description: 
On every SIP Transfer (Example: A calls B / B places A on hold / B calls C
/ A sends Transfer to Asterisk PBX) the Outing RTP Traffic from Asterisk to
the transfer target (RTP to C) is broken. The Asterisk is changing the RTP
Timestamp massivly but the SSRC stays on the old value and the timestamp
marker is also not set. As soon as the new timestamp is smaller than the
old timestamp value the transfer target rejects the RTP Packets after the
transfer (Not really, it's just not played), so i get one way audio.

I experienced that with serveral local SIP-Carriers and Funkwerk Rxxxx
BRI/PRI Mediagateways as transfer target.

Due to my limited Asterisk-Source knowledge i'am not sure that my attached
patch is the correct solution for this problem. After applying my patch the
problem seems to be solved. The Asterisk is changing the SSRC & setting the
Markerbit after the transfer for the RTP-Traffic to the transfer target.




====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-03-11 10:07 addix          New Issue                                    
2010-03-11 10:07 addix          Asterisk Version          => 1.4.29.1        
2010-03-11 10:07 addix          Regression                => No              
2010-03-11 10:07 addix          SVN Branch (only for SVN checkouts, not tarball
releases) => N/A             
======================================================================




More information about the asterisk-bugs mailing list