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

[Shaun Clark (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-21383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shaun Clark updated ASTERISK-21383:
-----------------------------------

    Attachment: Screen Shot 2013-04-05 at 8.10.27 AM.png

Chrome Error Log
                
> 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: onewaycapture.pcap, Screen Shot 2013-04-05 at 8.10.27 AM.png
>
>
> 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