<div dir="ltr"><div>i tried to use wss-binding and now it works, i have no idea why it's not working with ws-binding, could someone figure this </div><div><br></div><div>out.</div><div><br></div><div>there's another problem tho i think it may not be suitable to post here:</div>
<div><br></div><div>when i make a call between 2 parties, the i can hear the echo voice clearly (one party uses laptop without headset), isn't </div><div><br></div><div>AEC enabled by default for chrome? should i try firefox or is there anything i can do with FS configuration?</div>
<div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/12/1 Vincent Xia <span dir="ltr"><<a href="mailto:gmangudai@gmail.com" target="_blank">gmangudai@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div><b>has anybody ever tested freeswitch 1.4 with webrtc support under windows platform?</b></div><div><b>i tried to build and run fs 1.4 in windows 7 and windows server 2008 as the webrtc server but no success, i simply uncommented <param name="ws-binding" value=":5066"/> and had the jssip client connect to it, but nothing happened on the fs console, the log from chrome said it's "Connecting to WebSocket URI </b></div>
<div><b><br></b></div><div><b>ws://fs_host_ip:5066 jssip-0.2.1.js:619", </b></div><div><b><br></b></div><div><b>i did netstat -ano and saw freeswitch is already listening to 5066 and chrome is connecting to is</b></div>
<div><b>TCP local_ip:59687 fs_host_ip:5066 ESTABLISHED 12316</b></div><div><b>(fs uses 5066, chrome uses 12316)</b></div><div><b><br></b></div><div><b>so did i miss something to have freeswitch up for webrtc in windows?</b></div>
<div><b><br></b></div><div><b>ps:the firewall is off and the same issue happens with <a href="http://tryit.jssip.net" target="_blank">tryit.jssip.net</a>.</b></div><div><b><br></b></div><div><b>Regards,</b></div></div>
</blockquote></div><br></div>