Forum Discussion
Solved
Call queue won't ring agents
Hi, I've managed to set-up my call queue in teams, added a group (with myself in the group), all licenses are set-up appropriately and can call the number, but it doesn't ring in Teams. When I call ...
- Hi Luke_Pulis
Thanks! No problem: the supermassive growth of teams this last month (about 10 million daily active users) has meant that MS is working hard to scale up the platform to meet the sudden growth, and it has caused a bit of latency with the service. They are aware and it's in hand
Hmm, I see. This article may help
https://social.technet.microsoft.com/Forums/office/en-US/ab101ab9-5903-4b99-9943-8428bf517bb7/add-resource-account-to-call-queue-in-teams-using-powershell
Also, is your Teams instance set to Teams Only in the Teams Admin Centre?
https://docs.microsoft.com/en-us/microsoftteams/answer-auto-attendant-and-call-queue-calls
Let me know how you get on
Best, Chris
Hi Luke_Pulis
I would recreate the call queue.
I take it you followed the steps in this article here
https://docs.microsoft.com/en-us/microsoftteams/create-a-phone-system-call-queue
If you recreate and are still getting it let me know. Which type of routing did you set? Attendant?
Best, Chris
I would recreate the call queue.
I take it you followed the steps in this article here
https://docs.microsoft.com/en-us/microsoftteams/create-a-phone-system-call-queue
If you recreate and are still getting it let me know. Which type of routing did you set? Attendant?
Best, Chris
To be honest, the whole process has been a nightmare. Starting with the Teams Admin Panel, almost every step in the creation has returned some sort of error. I ended up restoring to using PowerShell to create the call queue but couldn't find any cmdlet documentation on how to add users/groups as agents. for some reason the Teams Admin Panel will let me add groups, but not individual users? So I decided to just create a group and add myself to it, no big deal. I have it set-up as attendant routing at the moment.
Thanks for you quick response, Chris.
- Hi Luke_Pulis
Thanks! No problem: the supermassive growth of teams this last month (about 10 million daily active users) has meant that MS is working hard to scale up the platform to meet the sudden growth, and it has caused a bit of latency with the service. They are aware and it's in hand
Hmm, I see. This article may help
https://social.technet.microsoft.com/Forums/office/en-US/ab101ab9-5903-4b99-9943-8428bf517bb7/add-resource-account-to-call-queue-in-teams-using-powershell
Also, is your Teams instance set to Teams Only in the Teams Admin Centre?
https://docs.microsoft.com/en-us/microsoftteams/answer-auto-attendant-and-call-queue-calls
Let me know how you get on
Best, ChrisChrisHoardMVP The technet link helped the situation. I deleted everything and restarted the whole process using only Powershell which cleared up the systems confusion. Thanks, Chris.
