Solved iOS PUSH Notifications Stopped

[routerconfigif]

Hello,

For a couple weeks now, we've not been receiving PUSH notifications for iOS (we don't have Google PUSH configured). We are on v14 SP3. Hosted on Windows Server 2012 R2.

There have been no updates to the configuration of either the firewall or the box it's hosted on. Checking the dialer log, I'm seeing the error below which seems to be related to SSL, but you don't configure SSL certs on v14 for PUSH. Would anyone be able to steer me in the right direction?

System.Security.Authentication.AuthenticationException: A call to SSPI failed, see inner exception. ---> System.ComponentModel.Win32Exception: The Local Security Authority cannot be contacted
   --- End of inner exception stack trace ---
   at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
   at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at Dialer.PushClient.PushApple(CallData cd, Int32 reason)

 

[routerconfigif]

So for some reason I look for hours on end to find a solution. Another random Google search leads me to the blog post below which fixed my issue. I feel like 3CX should have sent out a huge notice about this.

https://www.3cx.com/blog/news/v14-ios-client-push-certificate/

 

[YiannisH_3CX]

Hello @routerconfigif

Glad to hear that your issue is solved and thank you for your feedback.