Trio 8800 Unable to login to SFBO when upgraded to 5.9.1.10419

[SR_MCSE]

I have recently upgraded my fleet of Trio 8800 units, some with Visual+ pairing and others with not, from 5.9.0.11398 to 5.9.1.10419. 

All units took the upgrade and upgraded sucessfully, however I have a few units that will not log into SFBO using the same configuration issued from RPRM when it was working on the 5.9.0 release. 

My workaround at this time is to downgrade the affected units to 5.9.0.11398 to get them to log in and work with SFBO again. 

All devices are logging into the same O365 Tenant. The only upcoming change I can see is the upcoming OAuth 2.0 via 3rd part Azue Application ID, however this isn't required until Jan 15, 2020. 

I have 17 units that are working just fine, however 4 of them cannot log into SFBO when on on 5.9.1.10419.

Has anyone else experienced this issue? 

[SteffenBaierUK]

Hello @SR_MCSE ,

Welcome back to the Poly community.

Some or a couple of your old post(s) or reply(s) to them => here <= are still open/pending as you have not marked these as "Accept as a solution" or at least provide some form of feedback or answer.

If they are in this state nobody finding them via a community search will know if an answer or advice provided was useful and has maybe helped you.

Could you therefore kindly go over them and mark or answer as appropriate?

If they are marked as "Accept as a solution" other users can find these easier and it helps them to utilise the community more efficiently. Please do not simply mark them without any type of feedback.

For your new issue:

Jan 17, 2017 Question: How can I troubleshoot simple Skype for Business, Office365 or Teams issues?

Resolution: Have a look => here <=

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

[mshu]

Hi @SR_MCSE,

did you perform the needed steps for OAuth2.0 like it is described here: 

https://support.polycom.com/content/dam/polycom-support/products/voice/polycom-uc/other-documents/en...

If not, I would do it. I had similar issue after an update, OAuth solved it.