Forum Discussion
Teams Phone Numbers Mysteriously Unassigned
I am not an expert however we have the below under "Voice Routes"
Priority: 1
Voice Route: XXXXXX (provided by vendor)
PSTN usage XXXXXX (same as voice route, provided by vendor)
SBc Enrolled xxxx.xxxxx.com (provided by vendor)
No errors anywhere we can see as the SBC is hosted by our vendor. We logged a ticket with said vendor and no other customers are having this issue and our environment is online and no error reporting from their end.
The vendor also has our numbers (100 number ranges) and they have confirmed the numbers are all still active.
This is happening to Windows 10 and 11 laptops as well as Audio Codes 430HD phones. (Issue is Teams number not being assigned to the employee so end user devices are not the cause)
This has all been working fine since our migration from Skype for Business in October until this week. No changes were made over the last week from the vendors side or our side. Looks like a Teams issue as this is affecting multiple users (now 100 +) within our Teams environment and have confirmed no changes or errors. Some users are still working fine with their numbers assigned, very random issue. Is there a Teams log file we can export?
Hello againHaydenSlee,
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:
- Error messages indicating problems with the Teams service or related components, such as connectivity issues or issues with specific features.
- Warning messages indicating potential issues that may require attention, such as low disk space or network connectivity problems.
- Information messages that may provide context or additional details about the issue you are experiencing, such as details about the configuration or settings of the Teams service or related components.
A good reference: Search the audit log for events in Microsoft Teams - Microsoft Teams | Microsoft LearnAhme:D