Custom port + TLS + self-signed certificate

[lgg]

Some other SIP clients(Bria/GroundWire/MicroSIP) works fine with server.

Does Telephone support TLS + self-signed certificate on custom port(e.g. 34000)?

[brdelphus]

Bump for the win. I've tried just by curious to add ;transport=tls into my proxy settings and now everytime it loads up it crashes at the same time. I guess tls is not supported, which is a shame, i myself must agree with Igg that tls + srtp is quite mandatory nowadays.
thanks

[eofster]

@lgg do you want to have a self-signed certificate so that the server could authenticate Telephone as a client? Or do you mean self-signed certificate for the server?

[jploh]

I can confirm there's still an issue with a self-signed certificate. Would be nice to have an option to bypass certificate check validation. Alternatively, there could be an option to upload keys and trusted certificates instead.

[eofster]

TLS is supported since version 1.5, but self-signed certificates are not yet supported.

[cresh]

I would also love to see this.

[andrewhodel]

This is important, Sectigo CA signed TLS certificates are not supported in the latest MacOS causing this for Telephone on MacOS.

A way to import the Sectigo CA certificates would be a workaround, but Apple needs to add them to the CA certificates available to programs from the OS. The browsers bundle and include more CAs.