Hello All
Hope everyone is doing good
i have came across the below scenario,
ELIN numbers are not populated in SBC logs and MS Teams Client logs , eventhugh ELIN was properly configured using Set-CsOnlineLisLocation and working well for other cities in US . ELIN was not populated one of the US city.
As you all know, l Microsoft Teams clients are capable of using location information from the Network,OS, or User for emergency calls.
When the network is the desired source of the location, there are 3 key places that need to be configured.
First, the Trusted IP Address. This address is used by the Teams client to understand if it is on your organization’s network, or outside/remote. Trusted IP Address is not used beyond that, - Meaning This is kind of public IP of our orgainization network which connect through the Gateway to M365 Teams servers
Second, the client’s IP address is checked about the subnets configured in the Network Topology to establish if there’s a match for a network topology site
If there is a match, the policies from that site are applied.
For emergency calls, there is the Emergency Call Routing Policy, that establishes the route a call will take to reach emergency call takers if Direct Routing is being used, and there is the Emergency Calling Policy to configure notifications
Third, the client’s IP address and BSSID for wireless, and IP address, switch chassis, and switch port for wired, are compared against the LIS database
LIS stands for Location Information Services, and its job is to match your network information to the various places in our organization.
How to collect the support files for troubleshooting 933/911 calls
Right click on the Teams icon in the systray – you may need to click on the ^ icon beside the clock to see it.
Select “Collect Support Files”. You’ll see a of activity as the client writes files to the downloads folder, and then zips them automatically
Grab that zip file and open it.
Click on the folder called “web”, and then double click the file named “MSTeams Diagnostics Log 25_8_2023__9_31_02_PM_calling.txt”
First we will see the unsuccessful / NOT matched logs during the troubleshooting
Search for the phrase “trustedIpMatchInfo”. from MSTeams Diagnostics Log 25_8_2023__9_31_02_PM_calling.txt”
Section 1 : TrustedIP
Section 2 : SiteMatchInfo
The next section is used to apply policies if the Teams client is within a given site internal to the organization.
Section 3 : NetworkLocationMatchInfo
The next section is used to establish the Teams Client’s location within the organization for emergency calling purposes.
Comments
Post a Comment