Forum Discussion

Copper Contributor

Mar 25, 2020

Solved

Unable to create a Call Queue

Hi, I am trying to create a Call Queue in Teams using Powershell, but for some reason I can neither create a new call queue nor add the Teams-generated phone number to the resource account. T...

ChrisHoardMVP
Mar 25, 2020
Hi

See this thread here

https://techcommunity.microsoft.com/t5/microsoft-teams/call-queue-won-t-ring-agents/m-p/1242639#M48251

Try these

https://social.technet.microsoft.com/Forums/office/en-US/ab101ab9-5903-4b99-9943-8428bf517bb7/add-resource-account-to-call-queue-in-teams-using-powershell

Hope it helps and answers your question!

Best, Chris

ChrisHoardMVP

MVP

Mar 25, 2020

Hi

See this thread here

https://techcommunity.microsoft.com/t5/microsoft-teams/call-queue-won-t-ring-agents/m-p/1242639#M48251

Try these

https://social.technet.microsoft.com/Forums/office/en-US/ab101ab9-5903-4b99-9943-8428bf517bb7/add-resource-account-to-call-queue-in-teams-using-powershell

Hope it helps and answers your question!

Best, Chris

krzkal

Copper Contributor

Mar 26, 2020

ChrisHoardMVP That was indeed very helpful. Thank you very much.

I think I will be able to crack it further, there is just one more thing that seems kind of strange to me:

Both Telephone Number and Resource Account are in the same UsageLocation PL

Yet, when I try to map the tel to res.acc. I get a UsageLocation mismatch error:

CsOnlineVoiceApplicationInstance -Identity "mailto:VySdRouting@vy.no" -TelephoneNumber +485887845654

The Telephone Number assignment failed. The country of the user’s Usage Location NO and the country of the Telephone Number PL do not match.

+ CategoryInfo : NotSpecified: (:) [Set-CsOnlineVoiceApplicationInstance], BvdCmdletException

+ FullyQualifiedErrorId : UserNumberCountryMismatch,Microsoft.Rtc.Management.Hosted.Bvd.SetVoiceAppEndpointCmdlet

+ PSComputerName : http://admin1e.online.lync.com/

I have no clue, I have checked it several times - they are marked as UsageLocation PL, both.

Could it be because of domain/upn that is NO?

krzkal
Copper Contributor
Mar 30, 2020
I have solved the issue

The problem was mostly timing - it takes time for everything to sync these days. Maybe not simple configuration tasks but certainly accounts creation, license assignment did take very long time.

Those error msgs I got were slightly misleading, but I finally got it...

If you face similar issue, please follow the link shared by Christopher and give it some time... everything works much faster and more intuitive through Powershell... yet, you will be forced to wait.