Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Avaya Workplace on iOS stopped working through SBCE

Status
Not open for further replies.
pontim

pontim

Programmer
Aug 18, 2021
31
AR
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.
 
Sort by date Sort by votes
Maybe the certificate is outdated? Or sundering in the IPO configuration changed? Or the phone loads the wrong CA certificate?
 
Upvote 0 Downvote
Last edited:
Upvote 0 Downvote
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.
 
Upvote 0 Downvote
? 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"?
 
Upvote 0 Downvote
I can’t imagine this os the reason as it would affect all services on iPhone then like WhatsApp, Facebook, LinkedIn that all get push notifications through Apples APN. As the OP only is affected (or seems to), I would see it as an issue between the client and the IPO.
 
Upvote 0 Downvote
What's the emoticon for clearing one's throat to draw attention, and then merrily whistling as one turns and walks away...


I suspect that the frequency with which Avaya's part of the APN service keeps breaking may be why it hasn't been reported by more people. They're just used to it.

I wouldn't be holding my breath for the IP Office version of the support notice appearing soon, so worth trying to manually create and upload the new certificate yourself if you have this issue (see the Aura section of the PSN).
 
Upvote 1 Downvote
Thanks for sharing.

I was told by one from avaya that the extra step through Avaya Spaces as push service ‚proxy‘ instead of using a direct connection is intended to be able to react to adjustments in Apples push service without having to adjust the IPOs. But for me it feels like if the IPOs have to be adjusted to be able to connect to Avaya‘s Push service much more often than Apple changes their service.
 
Upvote 0 Downvote
"the extra step through Avaya Spaces as push service ‚proxy‘ instead of using a direct connection is intended to be able to react to adjustments in Apples push service without having to adjust the IPOs" - Nice theory, except it assumed that there would be some live body at Avaya regularly reading Apple developer bulletins and finding ways to handle changes or at least warn the downstream teams (its not just IPO that is affected by this as the PSN shows). I think we can all guess with Avaya's headcount changes what has happened to that idea.
 
Upvote 1 Downvote
The PSN for IP Office systems has now been released: https://support.avaya.com/css/public/documents/101092613

Much as expected, copy the text for the certificates* to a file, then upload that file to the IP Office system's trusted certificate store.

*The PSN says 2 certificates but then provides text for 3 certificates?
 
Upvote 0 Downvote
All of my IPOSE with SBC and Workplace iOS are still working - and I have several customers with hundreds of Users. The PSN stated that it will not change until April 1st.
I don't believe that is the issue... Now I am not saying that it is not something Apple-related and specific to @pontim, but the PSN issue doesn't jive as my phone and email would be blowing up.
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

William C290
  • Locked
  • Solved
Avaya SBCE for SIP Trunk & Workplace 2
Replies
13
Views
1K
derfloh
derfloh
William C290
  • Locked
  • Question
Avaya SBCE & Workplace / TLS
Replies
3
Views
746
derfloh
derfloh
finest
  • Locked
  • Question
Workplace/Mac and iOS - 46xxsettings.txt
Replies
1
Views
481
Shaun E
Shaun E
Scuzzie2k
  • Locked
  • Question
IP Office 500 and Avaya Workplace 1
Replies
6
Views
563
derfloh
derfloh
finest
  • Locked
  • Question
Workplace iOS 3.38.1 released yesterday to app store.
Replies
0
Views
507
finest
finest

Part and Inventory Search

Sponsor

Back
Top