[asterisk-bugs] [JIRA] (ASTERISK-21920) IAX trunk timestamps set to zero when it's bridged SIP channel wraps RTP timestamps

[Rusty Newton (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-21920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207876#comment-207876 ] 

Rusty Newton commented on ASTERISK-21920:
-----------------------------------------

@Gerhard

bq. Any idea as to how soon this might be resolved?

Nope. There are hundreds of issues in the queue and priorities jump around weekly depending on what is affecting the most people, whether issues are security related, etc.

bq.  And would the resolution of the issue result in a patch being issued for Asterisk 1.8.22.0? (I don't know how the process of issue resolution works)

A patch would be committed to trunk plus any branch where the issue occurs. You would see the patch come down into the latest release version of your branch. So that would be a 1.8.X version released after the patch was committed.

Right now a patch doesn't exist. The issue is waiting for any developer to take a look at it, when they are able. Someone could jump on it tomorrow or it could be months. If you can submit a patch, that could make things easier (depending on whether the patch is accurate to the issue and whether it has side-effects or not).
                
> IAX trunk timestamps set to zero when it's bridged SIP channel wraps RTP timestamps
> -----------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21920
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21920
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_iax2
>    Affects Versions: 1.8.22.0
>            Reporter: Gerhard
>         Attachments: iax.conf, issue_21920_full_log, rtpwrapiaxissue-bothrtpandiaxstreams.pcap, rtpwrapiaxissue_logB.pcap, sip.conf
>
>
> I have a Asterisk 1.8.22.0 box, with a SIP trunk to a Voip provider, and an IAX trunk (trunked, trunktimestamps enabled) to a client's PBX.
> The client places a call that arrives at Asterisk via IAX, and then the call goes via SIP to the telco. A RTP stream is now being received from the telco. 
> When this RTP stream's (from the telco) timestamp wraps (at 4 294 967 295), the IAX trunk timestamp transmitted from Asterisk is ZERO from then on, until the end of the call.
> I suspect this is done by the following code lines, which tries to prevent timestamps with negative values from being inserted in the IAX tx stream, without checking for RTP timestamp wrapping:
> chan_iax2.c :
> {noformat}
> Line 5940:
> 		if (ms < 0) {
> 			ms = 0;
> 		}
> Line 5947
> 		if (ms < 0)
> 			ms = 0;
> {noformat}
> See the tcpdump capture file supplied (the 1.8.22.0 Asterisk box has IP 192.168.200.222, the telco has IP 192.168.200.10, and the client has IP 192.168.200.5):
> At 12.854s into the capture, the RTP timestamp wraps. 
> Correspondingly in the IAX trunk packet at 12.867s into the capture, the trunk timestamp is 0, and stays 0 (in the previous trunk packet the timestamp was still 10132)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira