Avaya Workplace on iOS stopped working through SBCE

[pontim]

Hi Everyone,

I've been dealing with a issue on the workplace app for iOS.
I deployed a solution with an Ip Office Server Edition + Session Border Controller, and everything worked fine until around one or two weeks the users that have iOS stopped registering and have a certificate warning.
The same happens when i try to auto-configure a new device. "invalid certificate" comes up. Meanwhile everything works fine on Android.

Some years ago i had a similar problem where Apple decided to lower the accepted certificate logevity to a maximum of 820 days... But back then i found a document that clearified that. Now i can´t find anything similar.

Is anyone else experiencing the same issue?

Thanks in advance.

 

[derfloh]

Maybe the certificate is outdated? Or sundering in the IPO configuration changed? Or the phone loads the wrong CA certificate?

 

[sizbut]

Google may be your friend. I just entered "iOS certificate changes 2025".

• https://developer.apple.com/news/upcoming-requirements/?id=02242025a
  
  
• https://learn.microsoft.com/en-ie/answers/questions/2152047/app-store-apns-certificate-update

Yes, would be nice for Avaya to have spotted this coming and posted a warning and steps about what to do.

 

[derfloh]

But neither IPO nor Workplace Client nor the SBC directly connected to Apple‘s Push service. The connection is made to Avaya Spaces and Avaya Spaces connected to Apple‘s push service.

If Avaya Spaces wouldn’t trust the new Apple certificate, all IPO users with Apple Push would have been affected.

For me it looks more like on of the issues mentioned in my previous answer.

 

[sizbut]

? In which universe do iOS Workplace clients not connect to APN in order to use APN ?

iOS devices make outgoing connections to push.apple.com and receive incoming notifications from that service.

So its not beyond the bounds of possibilities that some iOS devices, and services on those devices, have not loaded an update that contained the new certificate. Apple changed the certificate required for APN two weeks ago and that coincides with the OPs suspected timescale for their issue.

Your entitled to your guesses but I don't how min is any less likely than "Maybe the certificate is outdated"?