Solved V16 Update 5 iOS App issues - does not signal incoming calls

[Uncle Doctor]

Our iOS users have had an automatic update installed (16.1.1.323) since yesterday that requires the new 3CX version.
Therefore we have updated to V16 Update 5.
The status of the App is again good, but incoming calls aren't displayed anymore.
If the user gets a call he won't notice that in the App. When the caller hangs up there's a "missed call" notification.
Calling is possible with the iOS App.
The user could theoretically pick up the call, which in practice is rather difficult.
3CX is installed on Win Server 2016 Datacenter.
There was no problem before the update.

This reminds me of the Android App without Google Push.
Since the update, the iOS app uses http/2, is it possible that something needs to be adjusted manually?
I could not find any information about this in the documentation.
Maybe open up some ports? The firewall test is running successfully.

Are there any others who have the same problem?

Greetz

 

[bro]

We, too, have experienced the exact same issue and now our whole business is out of action for calls except for the one person on Android.

AFAIK, no inbound ports were changed, and all outbound traffic is allowed.

EDIT: We had to migrate to a Raspberry Pi as after our staffs' iOS clients auto-updated we had literally zero choice but to move our 3CX server off of the older hardware we had and onto a Pi.

 

[TCWT]

I have a similar issue.
Android phones are OK, but IOS iphones are not receiving calls, as they were yesterday.
It appears an update of some sort has gone thru. There is one particular iPhone 6 handset that is not receiving calls, but can make calls out. Any update on this issue ??

 

[Roland.P]

Same issue here with the new iOS App and latest 3cx server updates on Debian.

 

[Vali_3CX]

Important:
https://www.3cx.com/community/threa...-v16-u5-to-restore-push-to-ios-devices.74027/

 

[Uncle Doctor]

Important:
https://www.3cx.com/community/threa...-v16-u5-to-restore-push-to-ios-devices.74027/

Is there a known issue for Windows Server?

I tried a config backup and reinstall, reinstall the apps, windows updates, server reboot.
The config is the same like before the update. I also tried a config backup out of march to make sure its not a config issue.

 

[Uncle Doctor]

We are running on Windows and have the problem with iPhones
Everything was running fine until the iPhones started to update the App to 16.1.1.323
(We have several different: 8, X, XS, 11 with IOS 13.5, 13.5.1 and 13.5.5 all have the same behavior)

It does not matter if WiFi or LTE

On an incoming call, In the App, under Status you see a change from “available” to “in call”, but there is no ring. After that you have a missed call in your list.

Our 3CX runs on Windows Server 2016 Datacenter. We have installed the latest 3CX Version (16.0.5.619)

Outgoing is no problem

 

[JohnS_3CX]

@Uncle Doctor have you made changes to the default security ciphers the server uses? Perhaps someone else maybe when setting it up? Server 2016 should work out of the box but one thing that can stop it from working with the new Apple PUSH server is if there is an incompatibility during the SSL negotiation stage.

 

[Uncle Doctor]

@JohnS_3CX just updated manually and the issue was there. Tought I took a mistake so I rebuild a snapshot in an new vm an installed the update with the auto update fuction. before the update it worked fine.

I uninstalled 3CX, downloaded it again, installed it and mounted my config backup. Same issue.

Now I've installed a new VM Win Server 2019 DC, installed 3CX ans mounted the config backup.
Firewall is fine. Issue still there.
Im out of idears.

 

[cobaltit]

@Uncle Doctor

Probably not your preferred solution or else you would have done it already but if you need the system up now I'd look at restoring to a Debian VM.

 

[JohnS_3CX]

Just to be clear, did you install anything else beyond only Windows Server 2019 and only 3CX?

And I do mean only those, so no antivirus, no extra software for monitoring etc.

Was the VM done in Hyper V or some other hypervisor environment?

If you want to run a very quick test, you can install Wireshark on the machine (to enable captures from the management console) and then I can explain to you how to run a capture and see if the system can communicate with the Apple servers.

 

[ccs1]

Has anyone got this working successfully on windows were getting a few angry customers now that cannot use there iPhones while being forced to work from home.

why is this no longer working since the update ?

 

[bro]

I installed the hotfix. Calls come in on iOS now, but answering a call glitches the system and just says "connecting". No one else can take the call because my device has technically taken it. This is a bit of a mess, and now we've got clients getting upset. We could cope when it was just us.

 

[Uncle Doctor]

Hello,

the problem has been located. There were problems with the handshake with the Apple Push servers.
Before iOS Push was running TCP 2195 and 2196 and now only over 443.
The error was also found via Wireshark. Start, call extension with iOS App and hang up.
You should see something like this there:

664 10.491608 17.188.132.155 192.168.X.Y TLSv1.2 828 Application Data
665 10.491610 17.188.132.155 192.168.X.Y TLSv1.2 85 Encrypted Alert
666 10. 491635 192.168.X.Y 17.188.132.155 TCP 54 60105 → 443 [ACK] Seq=333 Ack=5543 Win=2101504 Len=0
667 10.491649 17.188.132.155 192.168.X. Y TCP 60 443 → 60105 [FIN, ACK] Seq=5543 Ack=333 Win=30336 Len=0
668 10.491671 192.168.X.Y 17.188.132.155 TCP 54 60105 → 443 [ACK] Seq=333 Ack=5544 Win=2101504 Len=0
669 10. 492699 192.168.X.Y 17.188.132.155 TLSv1.2 85 Encrypted Alert
670 10.493012 192.168.X.Y 17.188.132.155 TCP 54 60105 → 443 [RST, ACK] Seq=364 Ack=5544 Win=0 Len=0

The address range 17.0.0.0/8 belongs to Apple.

If you have problems with the handshake please check if the HTTPS traffic to Apple is affected in any way (proxy, web filter, firewall, etc).
If it goes through, then Push should also work.

Greetz

 

[JohnS_3CX]

Glad to hear you were able to isolate the issue, I imagine once you allowed the traffic through your firewall it stated to work correctly?

 

[Uncle Doctor]

Yes, if the traffic is allowed it works immediately.
However, I had the support of the German 3CX support for troubleshooting.

 

[JohnS_3CX]

Thanks for updating the thread, I will mark it as solved then