[asterisk-bugs] [JIRA] (ASTERISK-21383) STUN Binding Requests Not Being Sent Back from Asterisk to Chrome

[James Mortensen (JIRA)]

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

James Mortensen commented on ASTERISK-21383:
--------------------------------------------

I just verified that this same bug exists in Asterisk 12.0.0-beta1.  

If I try to call out, or in, without the patch, the RTCP port is incorrect and Asterisk is unable to process the audio. So audio flows from the carrier to Chrome and from Chrome back to Asterisk, but since Asterisk gave Chrome a bad RTCP port, the audio isn't processed correctly.

I applied the https://issues.asterisk.org/jira/secure/attachment/46983/chansip_11-4-rc1_21383_2013_4_14.patch patch and rebuilt Asterisk and have verified the patch still works. With the patch in place, I can hear audio on both ends.

Hope this helps!
                
> STUN Binding Requests Not Being Sent Back from Asterisk to Chrome
> -----------------------------------------------------------------
>
>                 Key: ASTERISK-21383
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21383
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_http_websocket
>    Affects Versions: 11.3.0, 11.4.0
>            Reporter: Shaun Clark
>         Attachments: capture.pcap, chansip_11-4-rc1_21383_2013_4_12.patch, chansip_11-4-rc1_21383_2013_4_14.patch, chrome_debug_good_call-21383.log, onewaycapture.pcap, Screen Shot 2013-04-05 at 8.10.27 AM.png, stuncap.pcap
>
>
> When placing an outbound call from jssip/webrtc we get a one way audio situation that produces an error in Chrome that states:
> [1794:9495:0403/134116:VERBOSE1:port.cc(289)] Jingle:Port[audio:1:0::Net[en0:10.0.1.3/32]]: Received non-STUN packet from unknown address (198.61.XX.XX:11036)
> Asking the WebRTC group they say the error relates to RFC Spec 5245 section 17, where it talks about sending back stun bind requests from in this case Asterisk to the client. They believe that the bind request is not being properly returned. (https://groups.google.com/forum/?fromgroups=#!topic/discuss-webrtc/GKtrfMir2sE)

--
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