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

out.

there's another problem tho i think it may not be suitable to post here:

when i make a call between 2 parties, the i can hear the echo voice clearly (one party uses laptop without headset), isn't

AEC enabled by default for chrome? should i try firefox or is there anything i can do with FS configuration?

2013/12/1 Vincent Xia <gmangudai@gmail.com>

has anybody ever tested freeswitch 1.4 with webrtc support under windows platform?
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

ws://fs_host_ip:5066 jssip-0.2.1.js:619",

i did netstat -ano and saw freeswitch is already listening to 5066 and chrome is connecting to is

TCP local_ip:59687 fs_host_ip:5066 ESTABLISHED 12316
(fs uses 5066, chrome uses 12316)

so did i miss something to have freeswitch up for webrtc in windows?

ps:the firewall is off and the same issue happens with tryit.jssip.net.

Regards,