Forum Discussion
gdackerm
Nov 05, 2021Brass Contributor
New error with Teams Call Queue Voicemail
Starting this week we have a Call Queue error. This was working previously and we had reports from users saying that callers just had music and never had the option to leave a voicemail. Opening th...
tpeyton
Nov 05, 2021Copper Contributor
I have the same issue, just started this morning. Callers are not getting forwarded to the voicemail anymore and the red message just appeared in the call queue settings.
gdackerm
Nov 05, 2021Brass Contributor
tpeyton, good to know others see this as well but I'm sorry you have the same issue. I followed the support articles that seemed related but no resolution. The first was to ensure that Office365 had the correct Country, which is done. And that the language was selected in the Call Queue, which it is. I think something is going on here. I'm wondering if Microsoft launched some new feature during/part of the Ignite conference that had the side-effect?
- gdackermNov 05, 2021Brass Contributor
AndresGorzelany here are the settings. Before this week, there was no issue.
Call Queue Language -
And we shortened the time and number of callers to get to voicemail. We are sure callers are exceeding those values and are not sent to voicemail
- Nov 08, 2021Hello Greg, thanks for the additional information,
I could confirm with someone from Microsoft that the "You must select a language..." is being displayed always regardless of the language selected or not and that is not intended, I also could reproduce that so I think you can ignore that for now...
Is this happening -every time- or just in some cases?
Can you call the billing call queue resource account voicemail manually to test if you get the vm?
is some issue reported at Service Health in the Admin portal for your tenant region?- gdackermNov 08, 2021Brass ContributorAndresGorzelany, it seems, and I must run some tests today to be sure, that the callers never go to voicemail due to this issue. There is no description of this problem in the Service Health area related to this. We are in the middle of changing vendors so the support path is unclear right now but I intend to ask a favor with a Microsoft friend to see if I can get to the bottom of this. Additionally, for the company that is having the same problem. I'm working with them to run some tests in a test call queue to see if the system works properly despite the warning message. I'll post an update here as soon as I have more detail.