Jun 15 2022 09:10 AM
Jun 15 2022 09:10 AM
Over the last 2 weeks or so, we've noticed a handful of our Teams phone numbers which were assigned to users, become Unassigned. We have no automation in place - everything move, add or change we perform with our phone numbers is manual. The numbers in question have been assigned for months now. It wasn't until my phone number was assigned to someone else that we realized the issue. In order to assign a phone number that is already assigned, you'd have to delete the current user - which we certainly have not done. Mysteriously, the phone number status changed from assigned to unassigned. Has anyone experienced this? We have Operator Connect through Pure-IP. Thye don't touch our numbers once they are given to us in the Admin portal (or do they?). My MS Premier ticket came up empty. Apparently there are no audit logs for phone numbers, just licenses. And we verified no change in license status at all.
Jun 18 2022 07:22 AM
Since the community has not yet responded to your post, you might want to seek assistance with other resources that are focused on tech support:
Jun 21 2022 06:57 AM
Jun 29 2022 08:41 PM
Jun 30 2022 08:32 AM
Jun 30 2022 10:06 PM
@dennyhanrahan I'm not familiar with Operator Connect, but a quick Google shows these providers offer Session Border Controllers as a Service (SBCaaS) so our setup is similar.
We are using Session Border Controllers and Direct Routing. Our carrier is Optus.
We have reserved number ranges for each of our offices, and these number ranges are hosted by Optus. We pay Optus for our call charges (not Microsoft).
Jul 12 2022 01:58 PM
We are facing the same issue. We do run Operator Connect but have been able to check and see there have been no changes through iPilot. It's very frustrating that there aren't activity logs to go back to on the MS side. We thought we've been going crazy since we asked MS and they said there is no way that should be happening.
Jul 13 2022 03:40 PM
Jul 13 2022 04:33 PM
Jan 03 2023 09:18 PM
We are only now experiencing the exact same random issue with our Teams Direct Routing.
Over the last couple of days our users have had their numbers unassigned. We can re-assign the number, however it disappears again after about 15 minutes.
We have over 360 users, all with Office E5 licenses and have been working using Teams for over 3 months.
Dialpads are now missing in Teams Applications
Audio Codes handsets have signed out
Internally Teams is working fine, however we cannot make/receive to/from external due to the numbers being unassigned
Does anyone know how to resolve the issue?
Jan 03 2023 09:45 PM
Jan 03 2023 09:59 PM
Jan 04 2023 12:05 AM - edited Jan 04 2023 12:06 AM
hmmm...No-One is expert; we are all still learning and supporting eachother if we can as much as we can:)
Yes you can Review the Teams event logs: You can check the Teams event logs to see if there are any errors or warning messages that may provide clues about the cause of the issue. To do this, you can use the Get-EventLog cmdlet in PowerShell to retrieve the event logs for Teams.
The Detailed steps for your reference:
To review the Teams event logs using PowerShell, you can follow these steps:
Open a PowerShell window as an administrator.
Connect to the Exchange Online PowerShell module by running the following cmdlet: Connect-ExchangeOnline
Enter your Office 365 global administrator credentials when prompted.
To retrieve the event logs for Teams, run the following cmdlet: Get-EventLog -LogName "Teams Event Log"
To filter the event logs by a specific date range, you can use the -After and -Before parameters, like this: Get-EventLog -LogName "Teams Event Log" -After (Get-Date).AddDays(-7) -Before (Get-Date)
To view a specific event log entry, you can use the Format-List cmdlet to display all the properties of the event log entry, like this: Get-EventLog -LogName "Teams Event Log" | Format-List *
To export the event logs to a CSV file, you can use the Export-Csv cmdlet, like this: Get-EventLog -LogName "Teams Event Log" | Export-Csv -Path "C:\Temp\TeamsEventLogs.csv"
You want to check for any errors or warning messages that may indicate a problem with the Teams service or any related components. Some specific things you may want to look for include:
Feb 01 2023 04:59 PM