Forum Discussion
New-CSTeamsUnassignedNumberTreatment Not Working - You are not setup to use this calling feature
Hi all, We are off-boarding users and when we remove their licences and their phone number associated with their account, I would like a way to forward that number back into a AA or CQ. When ...
Hi,
Yes I have run the correct commands as per message. The issue occurs when you phone the number that is unassigned it does not forward to the AA or CQ I specified and just plays
a message that 'I am not setup to use this calling feature' I have assigned the Virtual Licence to the AA and CQ's. Are there any other prereqs that could be missing ?
PS C:\WINDOWS\system32> $RAObjectId = (Get-CsOnlineApplicationInstance -Identity Email address removed).ObjectId
PS C:\WINDOWS\system32> New-CsTeamsUnassignedNumberTreatment -Identity MainAA -Pattern "^([\+]4410000000$)" -TargetType ResourceAccount -Target $RAObjectId -TreatmentPriority 2
Yes I have run the correct commands as per message. The issue occurs when you phone the number that is unassigned it does not forward to the AA or CQ I specified and just plays
a message that 'I am not setup to use this calling feature' I have assigned the Virtual Licence to the AA and CQ's. Are there any other prereqs that could be missing ?
PS C:\WINDOWS\system32> $RAObjectId = (Get-CsOnlineApplicationInstance -Identity Email address removed).ObjectId
PS C:\WINDOWS\system32> New-CsTeamsUnassignedNumberTreatment -Identity MainAA -Pattern "^([\+]4410000000$)" -TargetType ResourceAccount -Target $RAObjectId -TreatmentPriority 2
I have exactly the same issue, did you ever resolve this?
- Not yet
So I've got it working. I spoke with Microsoft and they said that there was a problem with the resource account.
I created a new resource account and still didn't work. Turns out the resource account needs a calling plan, tested it and confirmed.
A small price to pay to keep all unassigned numbers "working" if you ask me.Just fyi, went back to the old resource account added calling plan still didn't work, so I suspect there was actually a problem with the resource account as per Microsoft's initial diagnosis.
Good luck