[asterisk-bugs] [Asterisk 0019173]: RTP timestamp skewed after call transfer or call unhold

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=19173 
====================================================================== 
Reported By:                xxot
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   19173
Category:                   Core/RTP
Reproducibility:            sometimes
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.8.3.3 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-04-23 18:50 CDT
Last Modified:              2011-04-26 05:33 CDT
====================================================================== 
Summary:                    RTP timestamp skewed after call transfer or call
unhold
Description: 
During incoming call from outside on asterisk after call transfer (which is
performed on asterisk) to another extension remote party lost incoming
audio channel (one way audio). We find out that the reason is connected
with RTP timestamp which is jumped to huge abnormal values after transfer
or putting call on hold. This issue was described here
https://issues.asterisk.org/view.php?id=11491
and I believe here: https://issues.asterisk.org/view.php?id=17007
But there was bug in version 1.4. In 1.8.3.3 we have the same: timestamps
skewed to crazy values. In documentation to RTP there is an information
that RTP Marker should be set if RTP source is changed. It is really set
here, but many phones use timestamps for counting jitter and don't pay
attention on RTP Marker. This is documented bug in phones Cisco 7960 and it
is still not fixed. Is there any chance to fix this issue in asterisk and
keep RTP timestamps stable even after call transfer?
====================================================================== 

---------------------------------------------------------------------- 
 (0134110) davidw (reporter) - 2011-04-26 05:33
 https://issues.asterisk.org/view.php?id=19173#c134110 
---------------------------------------------------------------------- 
We've noticed this on earlier versions, but the only impact appeared to be
on Wireshark's interpretation.

At the time, my feeling was that the real problem was a failure to change
the source ID, but I can't remember if we fully checked the RFCs. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-04-26 05:33 davidw         Note Added: 0134110                          
======================================================================