MICROSOFT SKYPE FOR BUSINESS TEAMS UPGRADE

A support person called me 2 days later, connected to me remotely, went through all of the Powershell commands to setup Cloud Voicemail (that I had already done a million times), made several calls, pulled up CLS logging,Ĭaptured traces of the voicemail sip sessions to my edge and off to the cloud, which showed the calls failing at an MS server with the following error: Us and people in our organization alike are coming unglued. We literally have had no voicemail since. Me they have shut off EXUM, have transparently migrated my tenant to Cloud Voicemail, had tested the migration, and that my voicemail traffic appeared to be normal.

MICROSOFT SKYPE FOR BUSINESS TEAMS UPGRADE

Had been getting emails from MS, but all of them said they would upgrade me to Cloud Voicemail transparently. Problem is, Microsoft shut off Exchange Unified Messaging on. So, we were using Exchange Unified Messaging for our voicemail. EXCEPT-our mail is handled by Office 365. We had no Skype for Business Online Tenant-in fact it was explicitly disabled many years ago because we were having all sorts of federation woes (I think this disabling is the source Our setup: We had an on-premise Skype for Business 2015 installation.

I am not a novice-I've been working with Skype for Business for many years, am proficient in powershell, the various admin consoles, I will try to explain my issues as concisely as I can as well as what I have tried.

Microsoft skype for business teams