[SR-Users] TLS connection from Chrome to Kamailio fails

[Juha Heinanen]

What I wrote in below, is not correct.

(1) Pointing Chrome to

https://<sip proxy>:5061

does result in successful handshake:

Oct 17 17:53:06 lohi /usr/bin/sip-proxy[13274]: INFO: tls [tls_domain.c:751]: sr_ssl_ctx_info_callback(): SSL handshake started
Oct 17 17:53:06 lohi /usr/bin/sip-proxy[13274]: INFO: tls [tls_domain.c:751]: sr_ssl_ctx_info_callback(): SSL handshake started
Oct 17 17:53:06 lohi /usr/bin/sip-proxy[13274]: INFO: tls [tls_domain.c:763]: sr_ssl_ctx_info_callback(): SSL handshake done
Oct 17 17:53:06 lohi /usr/bin/sip-proxy[13274]: INFO: tls [tls_server.c:431]: tls_accept(): tls_accept: new connection from 192.168.43.159:43874 using TLSv1.3 TLS_AES_256_GCM_SHA384 256

(2) But when JsSIP TryIt app tries to connect to K at the same port, it does
not result in SSL handshake done, but a series of trials:

Oct 17 17:55:20 lohi /usr/bin/sip-proxy[13274]: INFO: tls [tls_domain.c:751]: sr_ssl_ctx_info_callback(): SSL handshake started
Oct 17 17:55:23 lohi /usr/bin/sip-proxy[13274]: INFO: tls [tls_domain.c:751]: sr_ssl_ctx_info_callback(): SSL handshake started
Oct 17 17:55:25 lohi /usr/bin/sip-proxy[13274]: INFO: tls [tls_domain.c:751]: sr_ssl_ctx_info_callback(): SSL handshake started
...

And if I first do (1), then also (2) succeeds.

With Firefox, (2) works without (1).

-- Juha