Forum Discussion
Polycom VVX 411 Signing out Users at Random
Hi CosmoDenger
If you are using MFA, web sign-in is required.
Ref: https://documents.polycom.com/bundle/ucs-sfb-dg-5-9-0/page/c-ucs-sfb-web-sign-in-for-skype-for-business-online.html
Web Sign In supports Multi-Factor Authentication (MFA) on polycom phones. If you are using MFA, you must use Web Sign In as the user sign-in method with Polycom phones.
For more information on configuring Office 365, see Microsoft's Configure Azure Multi-Factor Authentication Settings.
- CosmoDengerNov 11, 2019Brass Contributor
DamianCastillo, absolutely. We have no problems signing in. The issue is that our users are signed out automatically every 7 days. I have two cases open with Microsoft and no one can figure out what to change to prevent the sign outs.
- DamianCastilloJan 21, 2020Copper Contributor
Hello CosmoDenger
Are you still having the same issue? usually, that kind of error can be found in the logs of the phones.
You can try checking this Poly community post:
https://community.polycom.com/t5/VoIP-SIP-Phones/FAQ-How-can-change-Logging-Levels-or-use-Syslog/td-p/4741
I would recommend you to enable these ones for exchange issues:
app1=2 , pps=2 , sip=debug, so=2 , auth=debug nisvc= debug pgui= debug curl=1
and for registration issues:
app1=2 , pps=1 , sip=debug, so=2 , auth=debug nisvc= debug tls= debug curl=1
Also, you may confirm that the consent its being applied by your O365 Admin:
That would give you an idea.
(Y) 😄
- AnonymousJan 21, 2020
CosmoDenger I am also facing the same problem with onprem skype/exchange2016.
Polycom phone can login successfully to EWS and then after few days getting error message "Warning Authentication failed re-enter password to access the Calendar"
Please let me know if you found any solution.
- CosmoDengerJan 22, 2020Brass Contributor
Unfortunately, we still don't have a solution. I have had a ticket open with Microsoft for approx. 3 months now and I think they have ghosted me. This sign out happens on Polycom and Audiocodes phones. We have done all the logging suggested by Microsoft and they confirmed the issue is on their end but cannot provide a resolution. We are a cloud only deployment.