| Summary: | ASTERISK-25467: chan_sip/webrtc Asterisk + Chrome M47 consistent 0.9s ice handshake delay since commit 1ad827 | ||||
| Reporter: | Nicole McIntosh (atna99) | Labels: | |||
| Date Opened: | 2015-10-14 12:22:20 | Date Closed: | 2015-12-08 16:48:29.000-0600 | ||
| Priority: | Major | Regression? | Yes | ||
| Status: | Closed/Complete | Components: | Resources/res_rtp_asterisk | ||
| Versions: | 11.19.0 | Frequency of Occurrence | Constant | ||
| Related Issues: |
| ||||
| Environment: | Ubuntu 14.04.2 LTS , asterisk version 11.19 updated to trunk, last commit: b4535b0 | Attachments: | |||
| Description: | There was a change introduced in Commit # 1ad827327a,
(ChangeId:Ib75ea2546f29d6efc3d2d37c58df6986c7bd9b91) This affected ICE/DTLS SSL behavior. The problem appears when comparing ICE negotiation delay, and differences in delay depending on version of chrome, as well as Asterisk version. Testing with Asterisk 11.19 and latest chrome (Canary M47) there is a significantly longer ICE negotiation delay. But, with same chrome on asterisk Before Commit 1ad827327a , no longer delay is present. (See external chromium issue linked in external issue ID) One possible solution may be to have Asterisk handle incoming DTLS packets as soon as ICE is connected, even if the signalling is delayed. This issue is for the behavior of asterisk when handling the ICE/DTLS handshake and signalling. reproducable everytime. To reproduce, compare webrtc asterisk ICE signalling delay between versions of asterisk after the commit(latest version) and Chrome Canary, and previous versions of Asterisk before aforementioned commit and Chrome Canary. | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2015-10-14 12:22:22.048-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: Rusty Newton (rnewton) 2015-12-08 16:48:29.298-0600 Okay to avoid confusion let us use the new issue that you have opened since you said the description is more accurate. | ||||