Forum Discussion
Voicemail - "This feature is not currently available"
Getting reports from users, and I have confirmed the same in my own tenant (all Teams-Only). PSTN calls are not going to voicemail when unanswered, as they are setup to do, but instead they're getting the message,
"This feature is not currently available".
I see in the Office health center that there is a service degradation incident LY204372 but it doesn't specifically mention this behavior. Is anyone else experiencing this?
I am also at this time unable to pull session diagnostics via the admin center Users-->Call History-->Session interface. The browser just spins...without returning results.
31 Replies
MTSBob I wanted to give you and everyone else on here an update. After a couple of weeks of back and forth with MS I have gone ahead and closed our ticket. Voicemail is working for us from all call paths we can think of testing, except calling from the number listed in Office 365 as the mobile number of the account being dialed.
MS wanted me to remove the mobile numbers to test, but since our company policy requires us to list our mobile number in our contact this isn't a real option.
As this is the only issue that is persisting for us, I have opted to close the ticket and move on. It is an annoyance but not a critical bug for us.
I tried now in a EU tenant it voicemail worked.
Can you call your voicemail settings from the settings menu in Teams?
I would suggest that you report this to Microsoft Support.
LinusCansby Yes, voicemail settings are all accessible both from Teams and from our 3PIP phones. PowerShell for the users who are affected report that they are all properly provisioned with Voicemail, etc. Oddly, however, we today started receiving a new message in our tenant telling us that "Microsoft Teams is ready for your organization - you can begin your upgrade today" - that's a new one, since we've been a Teams-only org now for over a year.
Looks like I'll be jumping into the tech support rabbit hole again. Thanks for checking on your end!Bob
MTSBob This is effecting us as well. Has been an issue for at least a week. I have a support case open with Microsoft and so far just normal tier 1 log collection, validation that users are set correctly. For us this seems to be primarily effecting users in the US West Coast. Our South East US and our UK users are not effected, though Microsoft swears that this cannot be a geographic issue.
Sorry to hear you are having trouble but I'm glad I am not alone on this one. I'm hoping maybe we can get some more attention on it.
