<div dir="ltr">Sorry guys, I jumped the gun here.<div><br></div><div>ChromeOS 36 beta started working for me when I switched from ethernet connection to wifi. Perhaps somehow ChromeOS 36 gets confused about which IP to use for media.</div>
<div><br></div><div>Strangely everything still worked fine on WebRTC non-FreeSWITCH demos, so perhaps it's something to look into at some point.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jun 9, 2014 at 3:29 PM, Oleg Stolyar <span dir="ltr"><<a href="mailto:olegstolyar@gmail.com" target="_blank">olegstolyar@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi FreeSWITCH team,<div><br></div><div>it seems that WebRTC on ChromeOS 36 beta does not work with FreeSWITCH.</div>
<div><br></div><div>I tried to go to <a href="https://webrtc.freeswitch.org/sipjs/index.html" target="_blank">https://webrtc.freeswitch.org/sipjs/index.html</a> and with default settings call into ext 9664 to listen to hold music. It works fine on Windows and Mac all versions of Chrome and on ChromeOS versions 34 and 35 but does not seem to work on ChromeOS beta 36. I am not sure why.</div>
<div><br></div><div>I am using JsSip client in my own app and see the same problem there. I don't think the problem is with JsSip or its offshot sipjs which <a href="http://webrtc.freeswitch.org" target="_blank">webrtc.freeswitch.org</a> uses since jssip's own demo seems to work fine <a href="http://tryit.jssip.net/" target="_blank">http://tryit.jssip.net/</a></div>
<div><br></div></div>
</blockquote></div><br></div>