[Home]

Summary:ASTERISK-27292: Multiple RTP Stream Created Breaking RFC2833 (SSRC Changes)
Reporter:Ross Beer (rossbeer)Labels:patch
Date Opened:2017-09-25 12:34:12Date Closed:2017-09-28 06:23:11
Priority:MajorRegression?
Status:Closed/CompleteComponents:Resources/res_rtp_asterisk
Versions:GIT Frequency of
Occurrence		Constant
Related
Issues:
Environment:Fedora 23Attachments:( 0) jira_asterisk_27292_v13.patch
( 1) Wireshark_1_clean.jpg
( 2) Wireshark_2_clean.jpg
Description:When making a call multiple RTP streams (SSRC Changes) are created on answer causing DTMF to be sent on the incorrect stream.

I think this could be related to the following commit https://gerrit.asterisk.org/#/c/6410/

Rolling back to Asterisk GIT-13-13.15.0-rc1-351-gf75f7b7M resolves the issue
Comments:By: Asterisk Team (asteriskteam) 2017-09-25 12:34:13.636-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].
By: Joshua C. Colp (jcolp) 2017-09-25 12:44:06.212-0500

Can we get the Asterisk console output as well to see the precise flow of things and when learning occurred?
By: Ross Beer (rossbeer) 2017-09-25 12:53:44.785-0500

I have sent the log and the full wireshark to George Joseph to attach to the internal ticket due to the sensitive information contain in both.
By: Richard Mudgett (rmudgett) 2017-09-25 14:37:02.549-0500

[~rossbeer] The asterisk_output.txt file only has verbose 3.  We'd need verbose 4 to see RTP learning messages and debug 1 to see learning packet by packet rejection messages.
By: Richard Mudgett (rmudgett) 2017-09-25 16:40:14.687-0500

Both c4f201cd738bacc0cabd29cc75ab29103ed8a84b and 3608f96ea378d6b37bcf26e6ca182077140a7b90 together are causing your problem.  They also caused the crash when you enabled debug 1.
By: Richard Mudgett (rmudgett) 2017-09-25 17:07:34.371-0500

[^jira_asterisk_27292_v13.patch] - One of the things this patch fixes should resolve the issue.  I had created this patch earlier for another reason but hadn't had a chance to test it.

Please test and report back.
By: Ross Beer (rossbeer) 2017-09-26 05:03:36.224-0500

The patch has resolved the DTMF issue and the segfault when enabling debugging.

Thank you for finding the solution.
By: Friendly Automation (friendly-automation) 2017-09-28 06:23:12.722-0500

Change 6603 merged by Jenkins2:
res_rtp_asterisk.c: Fix bridge_p2p_rtp_write() reentrancy potential.

[https://gerrit.asterisk.org/6603|https://gerrit.asterisk.org/6603]
By: Friendly Automation (friendly-automation) 2017-09-28 06:49:41.475-0500

Change 6604 merged by Jenkins2:
res_rtp_asterisk.c: Fix bridge_p2p_rtp_write() reentrancy potential.

[https://gerrit.asterisk.org/6604|https://gerrit.asterisk.org/6604]
By: Friendly Automation (friendly-automation) 2017-09-28 06:51:45.925-0500

Change 6605 merged by Jenkins2:
res_rtp_asterisk.c: Fix bridge_p2p_rtp_write() reentrancy potential.

[https://gerrit.asterisk.org/6605|https://gerrit.asterisk.org/6605]
By: Friendly Automation (friendly-automation) 2017-09-28 07:10:48.028-0500

Change 6606 merged by Joshua Colp:
res_rtp_asterisk.c: Fix bridge_p2p_rtp_write() reentrancy potential.

[https://gerrit.asterisk.org/6606|https://gerrit.asterisk.org/6606]