Forum Discussion
NumberAlreadyAssigned
I'm looking to allocate a number to a Resource in Teams. I'm picking this up after somebody else has been at it but it's still perplexing.
I have deleted all queues and auto attendants.
There are several numbers on the tenancy. One is a service number but I'm unable to allocate it to a resource account using either the Teams admin centre or PowerShell.
I get this error message.
The telephone number 4412345678 is already assigned to another user. Please assign another number that is available in the telephone number list.
+ CategoryInfo : NotSpecified: (:) [Set-CsOnlineVoiceApplicationInstance], BvdCmdletException
+ FullyQualifiedErrorId : NumberAlreadyAssigned,Microsoft.Rtc.Management.Hosted.Bvd.SetVoiceAppEndpointCmdlet
+ PSComputerName : admingb1.online.lync.com
Get-CsOnlineTelephoneNumber says :
RunspaceId : 7e302568-c2c7-455b-9459-8a4ae538bdd3
ActivationState : Activated
BridgeNumber :
CallingProfile : 962f77e8-046e-435c-ada8-31bc0396cda6
CityCode : EMEA-GB-ALL-ENG_ND
FriendlyName : NGC-Bot
Id : 4412345678
InventoryType : Service
Location :
O365Region : EMEA
SourceType : Tnm
TargetType : ucap
Tenant : Microsoft.Rtc.Management.Hosted.Bvd.Types.LacTenant
TenantId : 9fgg900d-9bed-5677-b3fc-9a6e40089c20
UserId :
IsManagedByServiceDesk : False
PortInOrderStatus :
It's baffling that it's not allocated to anything but insists it is.
Any pointers on advice would be appreciated. Publicity has been printed with the number so I really need to get it assigned to a resource account so I can use it on a queue or auto Attendent.
TIA
Andrew
- When did you delete the queues and such? I've noticed a sync issue today where settings have shown as being applied, but are still not working. For example I enabled enterprise voice for a user at 10:30am (US Central), and when I left at 4:45pm I was still getting an error back from Team's saying that Enterprise Voice wasn't enabled.
- I'm looking at it again today so there'll have been about 18 hours for things to propagate. Here's hoping!
- I'm not sure if you've seen, but Microsoft did just publish an incident in the O365 admin panel for a sync issue related to Teams Voice. They called out dial pad functionality, but also said voice services. TM205715.
