We had the same problem with FS 1.10.1 on Windows. I found a compiler switch: HAVE_OPENSSL_DTLSv1_2_method. Adding this to the FreeSwitchCore project file for Visual Studio, and recompiling, fixed the problem. It tells FS to use DTLS v1.2. I have never compiled FS on Linux, but I guess there are Makefiles that can be modified, possibly after some configure procedure. Best regards, Jaan From: FreeSWITCH-users <freeswitch-users-bounces@lists.freeswitch.org> On Behalf Of MARAND, Remi Sent: den 28 februari 2020 13:32 To: freeswitch-users@lists.freeswitch.org Subject: [Freeswitch-users] Help for Google Chrome version 81 & FS. We use Freeswitch in the case of a SIP to WebRTC application and it is a solid and reliable solution. When we test calls with the sipjs.js library (V0.15.10) and Freeswitch (FreeSWITCH Version 1.8.5-6-31281a0bf1~64bit (-6-31281a0bf1 64bit) + Debian 9, with the beta version of Chrome, Version 81.0.4044.17 (Official Build) beta (64-bit), we observe a notification on the javascript console : "[Deprecation] Your partner is negotiating an obsolete (D)TLS version. Support for this will be removed in M81, around March 2020. Please check with your partner to have this fixed. » The Wireshark trace shows that the DTLS-SRTP exchange is done with DTLSv1.0. What would be the version update to do on the Freeswitch side (or Debian) to avoid this deprecation ? Is there a configuration to do in our current version? Best regards. Rémi Marand Odigo France | Issy les Moulineaux Tel.: +33 1 46 84 12 77 / +33 6 87 72 53 25. www.odigo.com<https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.odigo.com%2F&data=02%7C01%7CJaan.Kaja%40enghouse.com%7Cb17e0557eaee4489f5d708d7bc5de9ab%7C427e40023c0240489e280eba58b331f4%7C1%7C1%7C637184983846595904&sdata=VbGH0VnjoyW5QlLi6iainkNhZqGwRAyIbHuyZo9g%2B2E%3D&reserved=0> This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.