[asterisk-bugs] [JIRA] (ASTERISK-25360) chan_sip:wrong ice candidate fails html5client on mobile connection
Fabrizio Lombardozzi (JIRA)
noreply at issues.asterisk.org
Mon Sep 7 09:58:32 CDT 2015
[ https://issues.asterisk.org/jira/browse/ASTERISK-25360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=227505#comment-227505 ]
Fabrizio Lombardozzi edited comment on ASTERISK-25360 at 9/7/15 9:57 AM:
-------------------------------------------------------------------------
Hi Rusty,
here are more infos.
Dialplan can be simply a simple echo test
exten => _.,1,Answer
exten => _.,2,echo
exten => _.,3,wait(600)
exten => _.,4,Hangup
Let me know if I missed something
Thanks
Fabrizio
was (Author: fabrizio_lombardozzi):
dialplan can be simply a simple echo test
exten => _.,1,Answer
exten => _.,2,echo
exten => _.,3,wait(600)
exten => _.,4,Hangup
> chan_sip:wrong ice candidate fails html5client on mobile connection
> -------------------------------------------------------------------
>
> Key: ASTERISK-25360
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-25360
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Channels/chan_sip/WebSocket, Resources/res_pjsip
> Affects Versions: 13.4.0, 13.5.0
> Environment: server: Centos 6.7
> client: Ubuntu, Windows, Android with Chrome 44 and Firefox 40, sipML5, SIP.js
> Reporter: Fabrizio Lombardozzi
> Assignee: Unassigned
> Attachments: full_bad, rtp.conf, sip.conf, sip.log
>
>
> Scenario:
> {noformat}
> asterisk server <--nat--> internet <--nat--> html5client
> {noformat}
> Systematically, when using webrtc, chan_sip.c:add_ice_to_sdp() chooses only LAN_ADDRESS of the server, so the SDP INVITE reply reports only candidate addresses that the client can't reach (see log)
> "sip show settings" cli command reports that PUBLIC_ADDRESS specified sip.conf and local subnets, are set properly, even media_address is set to PUBLIC_ADDRESS.
> Tcpdump running on the server reports no traffic to the stun server specified in rtp.conf
> In addition is to consider that the issue becomes actual only if the client uses a mobile connection (or is a mobile device using mobile connection), in all the other cases (pc with adsl router, mobile device with wifi-adsl) the client "understand" (don't know how or why) that is better to use the address specified in the sip header (or maybe where the traffic comes from).
> Brutely forcing PUBLIC_ADDRESS in add_ice_to_sdp() of chan_sip.c source code made the call possible from 3g mobile also.
> Multiple clients tested with sipML5, SIP.js in Firefox 40, Chrome44, on linux, windows and android with identical results.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list