I am registered with Office 365 and I'm currently using the BTOE feature on Skype for Business on my PC. It doesn't matter what credentials I use, I still cannot log into Skype for Business or even do a proper 'Time Synchronization' for the phone. I'm using the 'pool.ntp.org' for the time. I get the 'Auto Discovery has failed' followed by a message saying that logging into Skype has failed.
What do I need to and/or what should I be looking at to fix this?
Solved! Go to Solution.
I already solved this issue by realizing the ports on our switches were configured to work with our older VoiP phones. Clearing the configuration on the ports solved this problem
Hello @AdamJF,
welcome to the Polycom Community.
Both the community's Must Read First and the community's FAQ reference the basic minimum information a new or follow up post should contain.
This ensures the questions having to be asked are limited and any new or follow up post contains the right amount of details to ensure any voluntary participant within the community does not spend additional time chasing basic information.
As a reminder the basic information asked for:
UC Software 4.0.0 or later via the Web Interface Utilities > Phone Backup & Restore > Phone Backup > Phone Backup
Whilst providing the answers to some of the above may not directly impact any possible answer the community can provide, it does enable Polycom to have an overview of the current software used and other details and allows us to look up a potential support partners if an issue needs to come into support.
Please ensure you always check the FAQ's and/or utilize the community search before posting any new topics or follow up post’s.
Jan 17, 2017 Question:How can I troubleshoot simple Skype for Business, LYNC or Office365 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
Polycom Global Services
I already solved this issue by realizing the ports on our switches were configured to work with our older VoiP phones. Clearing the configuration on the ports solved this problem