Apps not working since 3CX 16.0.5.619 update

[D Garfield]

Hi,
I've found that now we have upgraded to version 16.0.5.619, none of my users can connect with their apple or android devices. We have a number of users using a variety of apps depending on the age of their device, i.e. old android app, new android app, old iOS and new iOS app.
If i rollback the server snapshot before upgrade, it all works fine again up until, and including 16.0.4.504. As soon as I go past this point, to 16.05.612 OR 16.0.5.619, all devices stop working, and are stuck on 'connecting...' OR 'waiting for network' depending on the app version.
I've double checked all of the ports are open here: https://www.3cx.com/docs/ports/.

Any help would be greatly appreciated.

Thanks,
DG

 

[Saqqara]

What operating system is the 3cx server running on

 

[D Garfield]

What operating system is the 3cx server running on

Thanks for taking the time to reply. Windows Server 2016 v1607.
Thanks,
DG

 

[dnadmin]

Same here. Our support provider updated our server version to 16.0.5.612 (also running on Server 16) on Friday evening. Was thinking I was having a quiet day but it's because no one can call each other! As everyone is remote working this is a major issue!

 

[D Garfield]

Same here. Our support provider updated our server version to 16.0.5.612 (also running on Server 16) on Friday evening. Was thinking I was having a quiet day but it's because no one can call each other! As everyone is remote working this is a major issue!

Hi, I ended up reverting back to 16.0.4.504 using a VM snapshot. I will wait until I see some meaningful release notes on any further updates to see if they have fixed the issue before trying again. Unless someone here has any ideas to try in the meantime! The only issue with that is the users that have updated to the new iOS app cannot receive calls, but they can still make calls. This is due to 3CX updating the iOS app for secure calls I believe. Annoying!

 

[dnadmin]

Hi, I ended up reverting back to 16.0.4.504 using a VM snapshot. I will wait until I see some meaningful release notes on any further updates to see if they have fixed the issue before trying again. Unless someone here has any ideas to try in the meantime! The only issue with that is the users that have updated to the new iOS app cannot receive calls, but they can still make calls. This is due to 3CX updating the iOS app for secure calls I believe. Annoying!

I can't believe they broke app compatibility NOW of all times Good call on rolling back the VM, maybe we should roll it all the way back to Cisco

 

[D Garfield]

I can't believe they broke app compatibility NOW of all times Good call on rolling back the VM, maybe we should roll it all the way back to Cisco

Hi, did you ever get this working? I've heard rumours that further devices will lose functionality at the end of the month.
Thanks,
DG

 

[JohnS_3CX]

Hi all,

As we have publicly stated before, Apple is shutting down their old PUSH API and we are moving to the new PUSH API.

Your OS and PBX are compatible, but you must make sure you are not blocking outgoing SSL/TLS traffic to port 443 towards Apple's PUSH range 17.0.0.0/8.

Also if you had performed cipher hardening (and thus removed certain ciphers from Windows Server) you will have to ensure that you allow the ciphers tha Apple's PUSH API servers are using.

Run a capture from your PBX, call an iOS extension, and then end the call (after it fails).
Download the capture and filter for the IP range above to see what happens when your PBX sends tries to establish a connection there. Depending on what you find, you will have to take the appropriate measures.