TLS 1.3

Nuno

Nuno

New Member
Hi Max does SIP Flashphoner already support TLS 1.3 ? because in the newer version chrome default is already 1.3 and if flashphoner still using dtls 1.2 will cause dtls error like on new chrome now..

Regard
Nuno S
 
Max

Max

Administrator
Staff member
Good day.
We tested the latest WCS build 5.3.163 with Chrome 140. DTLS negotiation passes without any issues, WebRTC publishing/playback works. So you can use latest Chrome with latest WCS builds.
 
Nuno

Nuno

New Member
Max said:
Good day.
We tested the latest WCS build 5.3.163 with Chrome 140. DTLS negotiation passes without any issues, WebRTC publishing/playback works. So you can use latest Chrome with latest WCS builds.
Click to expand...
hi max ,

already try with the latest version, the issue is when recieving call .... got this message when call rings than hangup :

User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36; alert level: 2; alert description: 47; message: null

Trace:
java.lang.Exception
at com.flashphoner.sip.D.G$1.onDtlsAlert(Unknown Source)
at com.flashphoner.media.B.B.onAlert(Unknown Source)
at com.flashphoner.B.C.A.notifyAlertReceived(Unknown Source)
at org.bouncycastle.tls.DTLSRecordLayer.receive(Unknown Source)
at org.bouncycastle.tls.DTLSReliableHandshake.receiveMessage(Unknown Source)
at org.bouncycastle.tls.DTLSServerProtocol.serverHandshake(Unknown Source)
at org.bouncycastle.tls.DTLSServerProtocol.accept(Unknown Source)
at com.flashphoner.media.B.B.dtlsKeyAgrementWithStunSocket(Unknown Sourc e)
at com.flashphoner.media.B.B.D(Unknown Source)
at com.flashphoner.media.B.B.initSessionAndPlayer(Unknown Source)
at com.flashphoner.media.B.C.J(Unknown Source)
at com.flashphoner.media.B.C$_A.propertyChange(Unknown Source)
at org.ice4j.ice.Agent.fireStateChange(Unknown Source)
at org.ice4j.ice.Agent.setState(Unknown Source)
at com.flashphoner.ice.IceAgent.setState(Unknown Source)
at com.flashphoner.ice.B.A.B(Unknown Source)
at java.base/java.lang.Thread.run(Thread.java:829)

Reason: SIP;cause=200;text="Failed by DTLS error"

can you please max try the incoming test to the flashphone sip from new chrome ok it keeps failing, but when doing outgoing its fine...

Regard
Nuno
 
Max

Max

Administrator
Staff member
We reproduced the issue with SIP calls and raised the ticket WCS-4631.
 
C

clounixltd

New Member
Hello,

i confirm, same problem here.
Call Outbound no problem, call inbound [Reason: SIP;cause=200;text="Failed by DTLS error"].

It seems that still working with Safari and some old version of Google Chrome, but fail when i install the latest version.

Thanks
Andrea
 
Nuno

Nuno

New Member
Good day Max, it works with the new version many thx, will continue monitoring, can you tell us what is the root cause?
 
You must log in or register to reply here.
Top