I am running Chrome Version 41.0.2272.101 m on Windows 7 and checked the 888 FreeSWITCH conference yesterday, it had audio both directions. I tried it 1 or 2 weeks ago and it had no audio so it must have updated itself behind my back because I did not explicitly update Chrome. Firefox 36.0.1 did not have any audio last week and now 36.0.4 has no audio either. I am testing this on my home network using a Cisco RV042 router and the default checkboxes on the FS WebRTC page which apparently default to using STUN. Anthm has stated many times that WebRTC is a moving target so enjoy the exhilaration of these rapid developments! I believe this is why he insists that WebRTC users keep FreeSWITCH updated so that it tracks the changes in the major web browsers. Bote From: Oleg Stolyar Sent: Monday, 23 March, 2015 14:21 Subject: [Freeswitch-users] Intermittent audio issue with Chrome 40-42 and WebRTC Hi guys, Ever since my users switched to Chrome 40, 41 or 42 beta, every now and then they complain that they cannot hear audio from FreeSWITCH or send audio to FreeSWITCH. I cannot reproduce this at will but was able to catch several occurrences. It happens on both Windows and Macs. Here are some details" 1. Usually the problem is solved if we close Chrome and make sure all the Chrome processes are killed. 2. When the problem happens, FS logs this on connection: [ERR] switch_rtp.c:2976 audio DTLS packet not written 3. I tried using this WebRTC test on an affected computer: https://janus.conf.meetecho.com/echotest.html and that worked, so it is not a general WebRTC issue. 4. I tried FS WebRTC demo page https://webrtc.freeswitch.org/verto/index.html#page-main and on the affected computer the problem was still there - no audio. 5. This happened both on an old FS version from last May and on a very recent master FreeSWITCH Version 1.5.15b+git~20150316T164411Z~b32abaadd9~64bit (git b32abaa 2015-03-16 16:44:11Z 64bit) Any ideas?