Sponsor: VoiceMeUp - Corporate & Wholesale VoIP Services

VoIP Mailing List Archives
Mailing list archives for the VoIP community
 SearchSearch 

[Freeswitch-users] HELP DTLS HANDSHAKE to FAIL chromeV87


 
Post new topic   Reply to topic    VoIP Mailing List Archives Forum Index -> freeSWITCH Users
View previous topic :: View next topic  
Author Message
Jazmin.Marino at on24.com
Guest





PostPosted: Fri Dec 04, 2020 2:18 pm    Post subject: [Freeswitch-users] HELP DTLS HANDSHAKE to FAIL chromeV87 Reply with quote

Hi
I have a verto client trying to connect to FS using Chrome V87 but we have DTLS problems.
The openssl version we are using on FS side is OpenSSL 1.0.2k-fips
FreeSWITCH (Version 1.8.4 64bit)


FS LOG - Chrome V87 FAILED CONNECTION

2020-12-03 11:23:06.762291 [ERR] switch_rtp.c:3199 video Handshake failure 1
2020-12-03 11:23:06.762291 [INFO] switch_rtp.c:3200 Changing video DTLS state from HANDSHAKE to FAIL
2020-12-03 11:23:06.832295 [ERR] switch_rtp.c:3199 audio Handshake failure 1
2020-12-03 11:23:06.832295 [INFO] switch_rtp.c:3200 Changing audio DTLS state from HANDSHAKE to FAIL
2020-12-03 11:23:06.852295 [NOTICE] switch_rtp.c:3181 Hangup verto.rtc/3520 [CS_EXECUTE] [DESTINATION_OUT_OF_ORDER]
2020-12-03 11:23:06.852295 [DEBUG] switch_core_media.c:7470 verto.rtc/3520 Video thread ended
2020-12-03 11:23:06.872305 [INFO] conference_loop.c:1670 Channel leaving conference, cause: DESTINATION_OUT_OF_ORDER
2020-12-03 11:23:06.872305 [DEBUG] switch_core_session.c:2639 verto.rtc/3520 skip receive message [DISPLAY] (channel is hungup already)
2020-12-03 11:23:06.872305 [DEBUG] mod_conference.c:2467 verto.rtc/3520 skip receive message [TRANSFER] (channel is hungup already)
2020-12-03 11:23:06.872305 [DEBUG] switch_core_media.c:12220 verto.rtc/3520 skip receive message [BITRATE_REQ] (channel is hungup already)
2020-12-03 11:23:06.872305 [DEBUG] switch_core_codec.c:248 verto.rtc/3520 Restore previous codec opus:116.
2020-12-03 11:23:06.872305 [DEBUG] switch_core_session.c:2886 verto.rtc/3520 skip receive message [PHONE_EVENT] (channel is hungup already)
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:650 (verto.rtc/3520) State EXECUTE going to sleep
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:584 (verto.rtc/3520) Running State Change CS_HANGUP (Cur 1 Tot 3)
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:847 (verto.rtc/3520) Callstate Change ACTIVE -> HANGUP
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:849 (verto.rtc/3520) State HANGUP
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:60 verto.rtc/3520 Standard HANGUP, cause: DESTINATION_OUT_OF_ORDER
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:849 (verto.rtc/3520) State HANGUP going to sleep

The weird thing is the connection works ok when the version of chrome is V86. Some weeks ago chrome was updated and we detected this issue.

FS LOG - ChromeV86 CONNECTION OK

2020-12-03 11:19:19.622294 [INFO] switch_rtp.c:3206 Changing video DTLS state from HANDSHAKE to SETUP
2020-12-03 11:19:19.672317 [INFO] switch_rtp.c:3113 video Fingerprint Verified.
2020-12-03 11:19:19.672317 [INFO] switch_rtp.c:4104 Activating video Secure RTP SEND
2020-12-03 11:19:19.672317 [INFO] switch_rtp.c:4082 Activating video Secure RTP RECV
2020-12-03 11:19:19.672317 [DEBUG] switch_core_sqldb.c:2617 Secure Type: srtp:dtls:AES_CM_128_HMAC_SHA1_80
2020-12-03 11:19:19.672317 [INFO] switch_rtp.c:3155 Changing video DTLS state from SETUP to READY
2020-12-03 11:19:19.672317 [DEBUG] switch_rtp.c:1890 rtcp_stats_init: video ssrc[2719546543] base_seq[1999]
2020-12-03 11:19:19.672317 [DEBUG] switch_core_sqldb.c:2617 Secure Type: srtp:dtls:AES_CM_128_HMAC_SHA1_80
2020-12-03 11:19:19.702298 [INFO] switch_rtp.c:3206 Changing audio DTLS state from HANDSHAKE to SETUP
2020-12-03 11:19:19.702298 [INFO] switch_rtp.c:3113 audio Fingerprint Verified.
2020-12-03 11:19:19.702298 [INFO] switch_rtp.c:4104 Activating audio Secure RTP SEND
2020-12-03 11:19:19.702298 [INFO] switch_rtp.c:4082 Activating audio Secure RTP RECV
2020-12-03 11:19:19.702298 [DEBUG] switch_core_sqldb.c:2617 Secure Type: srtp:dtls:AES_CM_128_HMAC_SHA1_80
2020-12-03 11:19:19.702298 [INFO] switch_rtp.c:3155 Changing audio DTLS state from SETUP to READY
2020-12-03 11:19:19.702298 [DEBUG] switch_core_sqldb.c:2617 Secure Type: srtp:dtls:AES_CM_128_HMAC_SHA1_80
Back to top
kaduww at gmail.com
Guest





PostPosted: Fri Dec 04, 2020 2:21 pm    Post subject: [Freeswitch-users] HELP DTLS HANDSHAKE to FAIL chromeV87 Reply with quote

Update to 1.10.5... I had the same problem and worked fine with the lastest

Em sex., 4 de dez. de 2020 às 15:09, Jazmin Marina Florez Marino <Jazmin.Marino@on24.com (Jazmin.Marino@on24.com)> escreveu:

Quote:

Hi
I have a verto client trying to connect to FS using Chrome V87 but we have DTLS problems.
The openssl version we are using on FS side is OpenSSL 1.0.2k-fips
FreeSWITCH (Version 1.8.4  64bit)
 
 
FS LOG - Chrome V87  FAILED CONNECTION
 
2020-12-03 11:23:06.762291 [ERR] switch_rtp.c:3199 video Handshake failure 1
2020-12-03 11:23:06.762291 [INFO] switch_rtp.c:3200 Changing video DTLS state from HANDSHAKE to FAIL
2020-12-03 11:23:06.832295 [ERR] switch_rtp.c:3199 audio Handshake failure 1
2020-12-03 11:23:06.832295 [INFO] switch_rtp.c:3200 Changing audio DTLS state from HANDSHAKE to FAIL
2020-12-03 11:23:06.852295 [NOTICE] switch_rtp.c:3181 Hangup verto.rtc/3520 [CS_EXECUTE] [DESTINATION_OUT_OF_ORDER]
2020-12-03 11:23:06.852295 [DEBUG] switch_core_media.c:7470 verto.rtc/3520 Video thread ended
2020-12-03 11:23:06.872305 [INFO] conference_loop.c:1670 Channel leaving conference, cause: DESTINATION_OUT_OF_ORDER
2020-12-03 11:23:06.872305 [DEBUG] switch_core_session.c:2639 verto.rtc/3520 skip receive message [DISPLAY] (channel is hungup already)
2020-12-03 11:23:06.872305 [DEBUG] mod_conference.c:2467 verto.rtc/3520 skip receive message [TRANSFER] (channel is hungup already)
2020-12-03 11:23:06.872305 [DEBUG] switch_core_media.c:12220 verto.rtc/3520 skip receive message [BITRATE_REQ] (channel is hungup already)
2020-12-03 11:23:06.872305 [DEBUG] switch_core_codec.c:248 verto.rtc/3520 Restore previous codec opus:116.
2020-12-03 11:23:06.872305 [DEBUG] switch_core_session.c:2886 verto.rtc/3520 skip receive message [PHONE_EVENT] (channel is hungup already)
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:650 (verto.rtc/3520) State EXECUTE going to sleep
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:584 (verto.rtc/3520) Running State Change CS_HANGUP (Cur 1 Tot 3)
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:847 (verto.rtc/3520) Callstate Change ACTIVE -> HANGUP
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:849 (verto.rtc/3520) State HANGUP
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:60 verto.rtc/3520 Standard HANGUP, cause: DESTINATION_OUT_OF_ORDER
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:849 (verto.rtc/3520) State HANGUP going to sleep
 
The weird thing is the connection works ok when the version of chrome is V86. Some weeks ago chrome was updated and we detected this issue.
 
FS LOG - ChromeV86 CONNECTION OK
 
2020-12-03 11:19:19.622294 [INFO] switch_rtp.c:3206 Changing video DTLS state from HANDSHAKE to SETUP
2020-12-03 11:19:19.672317 [INFO] switch_rtp.c:3113 video Fingerprint Verified.
2020-12-03 11:19:19.672317 [INFO] switch_rtp.c:4104 Activating video Secure RTP SEND
2020-12-03 11:19:19.672317 [INFO] switch_rtp.c:4082 Activating video Secure RTP RECV
2020-12-03 11:19:19.672317 [DEBUG] switch_core_sqldb.c:2617 Secure Type: srtp:dtls:AES_CM_128_HMAC_SHA1_80
2020-12-03 11:19:19.672317 [INFO] switch_rtp.c:3155 Changing video DTLS state from SETUP to READY
2020-12-03 11:19:19.672317 [DEBUG] switch_rtp.c:1890 rtcp_stats_init: video ssrc[2719546543] base_seq[1999]
2020-12-03 11:19:19.672317 [DEBUG] switch_core_sqldb.c:2617 Secure Type: srtp:dtls:AES_CM_128_HMAC_SHA1_80
2020-12-03 11:19:19.702298 [INFO] switch_rtp.c:3206 Changing audio DTLS state from HANDSHAKE to SETUP
2020-12-03 11:19:19.702298 [INFO] switch_rtp.c:3113 audio Fingerprint Verified.
2020-12-03 11:19:19.702298 [INFO] switch_rtp.c:4104 Activating audio Secure RTP SEND
2020-12-03 11:19:19.702298 [INFO] switch_rtp.c:4082 Activating audio Secure RTP RECV
2020-12-03 11:19:19.702298 [DEBUG] switch_core_sqldb.c:2617 Secure Type: srtp:dtls:AES_CM_128_HMAC_SHA1_80
2020-12-03 11:19:19.702298 [INFO] switch_rtp.c:3155 Changing audio DTLS state from SETUP to READY
2020-12-03 11:19:19.702298 [DEBUG] switch_core_sqldb.c:2617 Secure Type: srtp:dtls:AES_CM_128_HMAC_SHA1_80

_________________________________________________________________________

The FreeSWITCH project is sponsored by SignalWire https://signalwire.com
Enhance your FreeSWITCH install with disruptive priced SMS and PSTN services.
Build your next product on our scalable cloud platform.

Join our online community to chat in real time https://signalwire.community

Professional FreeSWITCH Services
sales@freeswitch.com (sales@freeswitch.com)
https://freeswitch.com

Official FreeSWITCH Sites
https://freeswitch.com/oss
https://freeswitch.org/confluence
https://cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org (FreeSWITCH-users@lists.freeswitch.org)
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
https://freeswitch.com



--
Carlos E. Wagner
Tecnólogo em Telecomunicações, Opensips Certified Professional

[b]Fone: +55 48 99981-0894
[/b]
E-mail: kaduww@gmail.com (kaduww@gmail.com)

LinkedIn: https://www.linkedin.com/in/carlos-eduardo-wagner-96bbb433/

Back to top
guenther.eberl at besh...
Guest





PostPosted: Fri Dec 04, 2020 2:38 pm    Post subject: [Freeswitch-users] HELP DTLS HANDSHAKE to FAIL chromeV87 Reply with quote

Hi,

I guess it is the freeswitch bug were TLS V 1.0 for audio streams is hardcoded in older versions.

You should see it on your data traces on the audio ports.

Bye
Gunther


Von: FreeSWITCH-users <freeswitch-users-bounces@lists.freeswitch.org> Im Auftrag von Jazmin Marina Florez Marino
Gesendet: Freitag, 4. Dezember 2020 18:24
An: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org>; freeswitch-dev@lists.freeswitch.org; freeswitch-users-request@lists.freeswitch.org
Betreff: [Freeswitch-users] HELP DTLS HANDSHAKE to FAIL chromeV87



Hi
I have a verto client trying to connect to FS using Chrome V87 but we have DTLS problems.
The openssl version we are using on FS side is OpenSSL 1.0.2k-fips
FreeSWITCH (Version 1.8.4 64bit)


FS LOG - Chrome V87 FAILED CONNECTION

2020-12-03 11:23:06.762291 [ERR] switch_rtp.c:3199 video Handshake failure 1
2020-12-03 11:23:06.762291 [INFO] switch_rtp.c:3200 Changing video DTLS state from HANDSHAKE to FAIL
2020-12-03 11:23:06.832295 [ERR] switch_rtp.c:3199 audio Handshake failure 1
2020-12-03 11:23:06.832295 [INFO] switch_rtp.c:3200 Changing audio DTLS state from HANDSHAKE to FAIL
2020-12-03 11:23:06.852295 [NOTICE] switch_rtp.c:3181 Hangup verto.rtc/3520 [CS_EXECUTE] [DESTINATION_OUT_OF_ORDER]
2020-12-03 11:23:06.852295 [DEBUG] switch_core_media.c:7470 verto.rtc/3520 Video thread ended
2020-12-03 11:23:06.872305 [INFO] conference_loop.c:1670 Channel leaving conference, cause: DESTINATION_OUT_OF_ORDER
2020-12-03 11:23:06.872305 [DEBUG] switch_core_session.c:2639 verto.rtc/3520 skip receive message [DISPLAY] (channel is hungup already)
2020-12-03 11:23:06.872305 [DEBUG] mod_conference.c:2467 verto.rtc/3520 skip receive message [TRANSFER] (channel is hungup already)
2020-12-03 11:23:06.872305 [DEBUG] switch_core_media.c:12220 verto.rtc/3520 skip receive message [BITRATE_REQ] (channel is hungup already)
2020-12-03 11:23:06.872305 [DEBUG] switch_core_codec.c:248 verto.rtc/3520 Restore previous codec opus:116.
2020-12-03 11:23:06.872305 [DEBUG] switch_core_session.c:2886 verto.rtc/3520 skip receive message [PHONE_EVENT] (channel is hungup already)
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:650 (verto.rtc/3520) State EXECUTE going to sleep
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:584 (verto.rtc/3520) Running State Change CS_HANGUP (Cur 1 Tot 3)
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:847 (verto.rtc/3520) Callstate Change ACTIVE -> HANGUP
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:849 (verto.rtc/3520) State HANGUP
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:60 verto.rtc/3520 Standard HANGUP, cause: DESTINATION_OUT_OF_ORDER
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:849 (verto.rtc/3520) State HANGUP going to sleep

The weird thing is the connection works ok when the version of chrome is V86. Some weeks ago chrome was updated and we detected this issue.

FS LOG - ChromeV86 CONNECTION OK

2020-12-03 11:19:19.622294 [INFO] switch_rtp.c:3206 Changing video DTLS state from HANDSHAKE to SETUP
2020-12-03 11:19:19.672317 [INFO] switch_rtp.c:3113 video Fingerprint Verified.
2020-12-03 11:19:19.672317 [INFO] switch_rtp.c:4104 Activating video Secure RTP SEND
2020-12-03 11:19:19.672317 [INFO] switch_rtp.c:4082 Activating video Secure RTP RECV
2020-12-03 11:19:19.672317 [DEBUG] switch_core_sqldb.c:2617 Secure Type: srtp:dtls:AES_CM_128_HMAC_SHA1_80
2020-12-03 11:19:19.672317 [INFO] switch_rtp.c:3155 Changing video DTLS state from SETUP to READY
2020-12-03 11:19:19.672317 [DEBUG] switch_rtp.c:1890 rtcp_stats_init: video ssrc[2719546543] base_seq[1999]
2020-12-03 11:19:19.672317 [DEBUG] switch_core_sqldb.c:2617 Secure Type: srtp:dtls:AES_CM_128_HMAC_SHA1_80
2020-12-03 11:19:19.702298 [INFO] switch_rtp.c:3206 Changing audio DTLS state from HANDSHAKE to SETUP
2020-12-03 11:19:19.702298 [INFO] switch_rtp.c:3113 audio Fingerprint Verified.
2020-12-03 11:19:19.702298 [INFO] switch_rtp.c:4104 Activating audio Secure RTP SEND
2020-12-03 11:19:19.702298 [INFO] switch_rtp.c:4082 Activating audio Secure RTP RECV
2020-12-03 11:19:19.702298 [DEBUG] switch_core_sqldb.c:2617 Secure Type: srtp:dtls:AES_CM_128_HMAC_SHA1_80
2020-12-03 11:19:19.702298 [INFO] switch_rtp.c:3155 Changing audio DTLS state from SETUP to READY
2020-12-03 11:19:19.702298 [DEBUG] switch_core_sqldb.c:2617 Secure Type: srtp:dtls:AES_CM_128_HMAC_SHA1_80
Back to top
ciprian.dosoftei at gm...
Guest





PostPosted: Fri Dec 04, 2020 5:16 pm    Post subject: [Freeswitch-users] HELP DTLS HANDSHAKE to FAIL chromeV87 Reply with quote

Check the length of the dtls-srtp.pem key, if its length is short (< 4096) you can run into handshake issues.

You can also remove the pem file and allow FreeSWITCH to create a fresh one upon restart.


On Fri, 4 Dec 2020 at 14:36, Eberl Guenther <guenther.eberl@besharp.at (guenther.eberl@besharp.at)> wrote:

Quote:

Hi,
 
I guess it is the freeswitch bug were TLS V 1.0 for audio streams is hardcoded in older versions.
 
You should see it on your data traces on the audio ports.
 
Bye
Gunther
 
 
Von: FreeSWITCH-users <freeswitch-users-bounces@lists.freeswitch.org (freeswitch-users-bounces@lists.freeswitch.org)> Im Auftrag von Jazmin Marina Florez Marino
Gesendet: Freitag, 4. Dezember 2020 18:24
An: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org (freeswitch-users@lists.freeswitch.org)>; freeswitch-dev@lists.freeswitch.org (freeswitch-dev@lists.freeswitch.org); freeswitch-users-request@lists.freeswitch.org (freeswitch-users-request@lists.freeswitch.org)
Betreff: [Freeswitch-users] HELP DTLS HANDSHAKE to FAIL chromeV87


 
Hi
I have a verto client trying to connect to FS using Chrome V87 but we have DTLS problems.
The openssl version we are using on FS side is OpenSSL 1.0.2k-fips
FreeSWITCH (Version 1.8.4  64bit)
 
 
FS LOG - Chrome V87  FAILED CONNECTION
 
2020-12-03 11:23:06.762291 [ERR] switch_rtp.c:3199 video Handshake failure 1
2020-12-03 11:23:06.762291 [INFO] switch_rtp.c:3200 Changing video DTLS state from HANDSHAKE to FAIL
2020-12-03 11:23:06.832295 [ERR] switch_rtp.c:3199 audio Handshake failure 1
2020-12-03 11:23:06.832295 [INFO] switch_rtp.c:3200 Changing audio DTLS state from HANDSHAKE to FAIL
2020-12-03 11:23:06.852295 [NOTICE] switch_rtp.c:3181 Hangup verto.rtc/3520 [CS_EXECUTE] [DESTINATION_OUT_OF_ORDER]
2020-12-03 11:23:06.852295 [DEBUG] switch_core_media.c:7470 verto.rtc/3520 Video thread ended
2020-12-03 11:23:06.872305 [INFO] conference_loop.c:1670 Channel leaving conference, cause: DESTINATION_OUT_OF_ORDER
2020-12-03 11:23:06.872305 [DEBUG] switch_core_session.c:2639 verto.rtc/3520 skip receive message [DISPLAY] (channel is hungup already)
2020-12-03 11:23:06.872305 [DEBUG] mod_conference.c:2467 verto.rtc/3520 skip receive message [TRANSFER] (channel is hungup already)
2020-12-03 11:23:06.872305 [DEBUG] switch_core_media.c:12220 verto.rtc/3520 skip receive message [BITRATE_REQ] (channel is hungup already)
2020-12-03 11:23:06.872305 [DEBUG] switch_core_codec.c:248 verto.rtc/3520 Restore previous codec opus:116.
2020-12-03 11:23:06.872305 [DEBUG] switch_core_session.c:2886 verto.rtc/3520 skip receive message [PHONE_EVENT] (channel is hungup already)
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:650 (verto.rtc/3520) State EXECUTE going to sleep
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:584 (verto.rtc/3520) Running State Change CS_HANGUP (Cur 1 Tot 3)
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:847 (verto.rtc/3520) Callstate Change ACTIVE -> HANGUP
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:849 (verto.rtc/3520) State HANGUP
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:60 verto.rtc/3520 Standard HANGUP, cause: DESTINATION_OUT_OF_ORDER
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:849 (verto.rtc/3520) State HANGUP going to sleep
 
The weird thing is the connection works ok when the version of chrome is V86. Some weeks ago chrome was updated and we detected this issue.
 
FS LOG - ChromeV86 CONNECTION OK
 
2020-12-03 11:19:19.622294 [INFO] switch_rtp.c:3206 Changing video DTLS state from HANDSHAKE to SETUP
2020-12-03 11:19:19.672317 [INFO] switch_rtp.c:3113 video Fingerprint Verified.
2020-12-03 11:19:19.672317 [INFO] switch_rtp.c:4104 Activating video Secure RTP SEND
2020-12-03 11:19:19.672317 [INFO] switch_rtp.c:4082 Activating video Secure RTP RECV
2020-12-03 11:19:19.672317 [DEBUG] switch_core_sqldb.c:2617 Secure Type: srtp:dtls:AES_CM_128_HMAC_SHA1_80
2020-12-03 11:19:19.672317 [INFO] switch_rtp.c:3155 Changing video DTLS state from SETUP to READY
2020-12-03 11:19:19.672317 [DEBUG] switch_rtp.c:1890 rtcp_stats_init: video ssrc[2719546543] base_seq[1999]
2020-12-03 11:19:19.672317 [DEBUG] switch_core_sqldb.c:2617 Secure Type: srtp:dtls:AES_CM_128_HMAC_SHA1_80
2020-12-03 11:19:19.702298 [INFO] switch_rtp.c:3206 Changing audio DTLS state from HANDSHAKE to SETUP
2020-12-03 11:19:19.702298 [INFO] switch_rtp.c:3113 audio Fingerprint Verified.
2020-12-03 11:19:19.702298 [INFO] switch_rtp.c:4104 Activating audio Secure RTP SEND
2020-12-03 11:19:19.702298 [INFO] switch_rtp.c:4082 Activating audio Secure RTP RECV
2020-12-03 11:19:19.702298 [DEBUG] switch_core_sqldb.c:2617 Secure Type: srtp:dtls:AES_CM_128_HMAC_SHA1_80
2020-12-03 11:19:19.702298 [INFO] switch_rtp.c:3155 Changing audio DTLS state from SETUP to READY
2020-12-03 11:19:19.702298 [DEBUG] switch_core_sqldb.c:2617 Secure Type: srtp:dtls:AES_CM_128_HMAC_SHA1_80

_________________________________________________________________________

The FreeSWITCH project is sponsored by SignalWire https://signalwire.com
Enhance your FreeSWITCH install with disruptive priced SMS and PSTN services.
Build your next product on our scalable cloud platform.

Join our online community to chat in real time https://signalwire.community

Professional FreeSWITCH Services
sales@freeswitch.com (sales@freeswitch.com)
https://freeswitch.com

Official FreeSWITCH Sites
https://freeswitch.com/oss
https://freeswitch.org/confluence
https://cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org (FreeSWITCH-users@lists.freeswitch.org)
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
https://freeswitch.com



--
Best Regards,
Ciprian Dosoftei

The information transmitted is intended only for the addressee and may contain privileged and/or confidential material. If you are not the intended recipient, kindly contact the sender and delete the message.

Any disclosure, distribution or copying of this message is strictly prohibited without the expressed permission of the sender.
Back to top
Alexander.Haugg at c4b.de
Guest





PostPosted: Mon Dec 07, 2020 1:52 am    Post subject: [Freeswitch-users] HELP DTLS HANDSHAKE to FAIL chromeV87 Reply with quote

Hi,

I think your problem is solved if your freeswitch works with DTLS version 1.2 instead of 1.0
https://freeswitch.org/jira/browse/FS-11730

Regards
Alex



Von: FreeSWITCH-users <freeswitch-users-bounces@lists.freeswitch.org> Im Auftrag von Jazmin Marina Florez Marino
Gesendet: Freitag, 4. Dezember 2020 18:24
An: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org>; freeswitch-dev@lists.freeswitch.org; freeswitch-users-request@lists.freeswitch.org
Betreff: [Freeswitch-users] HELP DTLS HANDSHAKE to FAIL chromeV87



Hi
I have a verto client trying to connect to FS using Chrome V87 but we have DTLS problems.
The openssl version we are using on FS side is OpenSSL 1.0.2k-fips
FreeSWITCH (Version 1.8.4 64bit)


FS LOG - Chrome V87 FAILED CONNECTION

2020-12-03 11:23:06.762291 [ERR] switch_rtp.c:3199 video Handshake failure 1
2020-12-03 11:23:06.762291 [INFO] switch_rtp.c:3200 Changing video DTLS state from HANDSHAKE to FAIL
2020-12-03 11:23:06.832295 [ERR] switch_rtp.c:3199 audio Handshake failure 1
2020-12-03 11:23:06.832295 [INFO] switch_rtp.c:3200 Changing audio DTLS state from HANDSHAKE to FAIL
2020-12-03 11:23:06.852295 [NOTICE] switch_rtp.c:3181 Hangup verto.rtc/3520 [CS_EXECUTE] [DESTINATION_OUT_OF_ORDER]
2020-12-03 11:23:06.852295 [DEBUG] switch_core_media.c:7470 verto.rtc/3520 Video thread ended
2020-12-03 11:23:06.872305 [INFO] conference_loop.c:1670 Channel leaving conference, cause: DESTINATION_OUT_OF_ORDER
2020-12-03 11:23:06.872305 [DEBUG] switch_core_session.c:2639 verto.rtc/3520 skip receive message [DISPLAY] (channel is hungup already)
2020-12-03 11:23:06.872305 [DEBUG] mod_conference.c:2467 verto.rtc/3520 skip receive message [TRANSFER] (channel is hungup already)
2020-12-03 11:23:06.872305 [DEBUG] switch_core_media.c:12220 verto.rtc/3520 skip receive message [BITRATE_REQ] (channel is hungup already)
2020-12-03 11:23:06.872305 [DEBUG] switch_core_codec.c:248 verto.rtc/3520 Restore previous codec opus:116.
2020-12-03 11:23:06.872305 [DEBUG] switch_core_session.c:2886 verto.rtc/3520 skip receive message [PHONE_EVENT] (channel is hungup already)
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:650 (verto.rtc/3520) State EXECUTE going to sleep
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:584 (verto.rtc/3520) Running State Change CS_HANGUP (Cur 1 Tot 3)
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:847 (verto.rtc/3520) Callstate Change ACTIVE -> HANGUP
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:849 (verto.rtc/3520) State HANGUP
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:60 verto.rtc/3520 Standard HANGUP, cause: DESTINATION_OUT_OF_ORDER
2020-12-03 11:23:06.872305 [DEBUG] switch_core_state_machine.c:849 (verto.rtc/3520) State HANGUP going to sleep

The weird thing is the connection works ok when the version of chrome is V86. Some weeks ago chrome was updated and we detected this issue.

FS LOG - ChromeV86 CONNECTION OK

2020-12-03 11:19:19.622294 [INFO] switch_rtp.c:3206 Changing video DTLS state from HANDSHAKE to SETUP
2020-12-03 11:19:19.672317 [INFO] switch_rtp.c:3113 video Fingerprint Verified.
2020-12-03 11:19:19.672317 [INFO] switch_rtp.c:4104 Activating video Secure RTP SEND
2020-12-03 11:19:19.672317 [INFO] switch_rtp.c:4082 Activating video Secure RTP RECV
2020-12-03 11:19:19.672317 [DEBUG] switch_core_sqldb.c:2617 Secure Type: srtp:dtls:AES_CM_128_HMAC_SHA1_80
2020-12-03 11:19:19.672317 [INFO] switch_rtp.c:3155 Changing video DTLS state from SETUP to READY
2020-12-03 11:19:19.672317 [DEBUG] switch_rtp.c:1890 rtcp_stats_init: video ssrc[2719546543] base_seq[1999]
2020-12-03 11:19:19.672317 [DEBUG] switch_core_sqldb.c:2617 Secure Type: srtp:dtls:AES_CM_128_HMAC_SHA1_80
2020-12-03 11:19:19.702298 [INFO] switch_rtp.c:3206 Changing audio DTLS state from HANDSHAKE to SETUP
2020-12-03 11:19:19.702298 [INFO] switch_rtp.c:3113 audio Fingerprint Verified.
2020-12-03 11:19:19.702298 [INFO] switch_rtp.c:4104 Activating audio Secure RTP SEND
2020-12-03 11:19:19.702298 [INFO] switch_rtp.c:4082 Activating audio Secure RTP RECV
2020-12-03 11:19:19.702298 [DEBUG] switch_core_sqldb.c:2617 Secure Type: srtp:dtls:AES_CM_128_HMAC_SHA1_80
2020-12-03 11:19:19.702298 [INFO] switch_rtp.c:3155 Changing audio DTLS state from SETUP to READY
2020-12-03 11:19:19.702298 [DEBUG] switch_core_sqldb.c:2617 Secure Type: srtp:dtls:AES_CM_128_HMAC_SHA1_80
Back to top
Display posts from previous:   
Post new topic   Reply to topic    VoIP Mailing List Archives Forum Index -> freeSWITCH Users All times are GMT - 5 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group

VoiceMeUp - Corporate & Wholesale VoIP Services