TLS not working anymore for mobile clients since SP6

Status
Not open for further replies.
  • Did you reprovision the 3CX Client? Maybe it was still trying to connect using the old info?
  • Did you restart all services on the PBX after changing the cert?
 
reprovision - yes.
restart whole server to be sure.

Now again removed the free version. Reinstall 3CX and configure pro version with own certificate.
 

Attachments

  • Image-1.jpg
    Image-1.jpg
    70.6 KB · Views: 5
Do you have the tunnel enabled for these devices? If you do you should turn it off and reprovision the clients as TLS does not work with the tunnel.
 
turned off tunnel. Same result.

with tunnel it works with free license and 3cx fqdn
 

Attachments

  • notunnel.PNG
    notunnel.PNG
    13.5 KB · Views: 5
4 x 3CX servers. 1 server free license with 3cx domain and certificate all working fine for mobile clients. 2 servers with own certificate TLS will not work and mobile client will always say waiting for network. 1 server with own certificate the mobile client also does not work when 3cx client profile is set to "allow secure". when selecting "normal" the mobile client works fine.

This TLS issue in combination with calls dropping when switching from 4G to Wifi and vise versa makes our life not very easy. For the last weeks we spend hours and hours and hours to test many options.

TLS for fixed phones which are connected remotly works fine for all servers. (With a custom made yealink template. Template inside 3cx is wrong template with wrong phones.)

Is there a work in progress to get TLS for the mobile client working and this roaming from 4G to wifi fixed?
 
Give it a go with the latest Android Client.
 
We tried with version 15.5.345 released 12 okt. This one did not work yet.
 
Status
Not open for further replies.

Forum statistics

Threads
111,900
Messages
589,630
Members
164,765
Latest member
domi