Forum Discussion

Iron Contributor

Jul 03, 2020

Solved

Dynamic Emergency Calling

Some assistance please in those who have configured Dynamic Emergency Call Routing When it comes to Set-CsOnlineLisSubnet for the subnets. For example, the persons IP address is 10.10.10.100 ...

emergency calling

HenryPhillipsNimbitech
Jul 03, 2020
Hi fowler_23 ,

Have you tried defining the Network via New-CsTenantNetworkSubnet, an example of which is shown here: New-CsTenantNetworkSubnet -Identity 192.168.1.0 -Description "Home Subnet" -MaskBits 24 -NetworkSiteID "Home Office"

The above should let you at least define the Subnet Mask, so not sure if you did this and then your set command it would help?

You might want to even do the New-CsTenantNetwork site. A sequence of which is shown below:

#Specify New Network Location
New-CsTenantNetworkSite -EmergencyCallingPolicy "Home Office" -Description "Home" -Identity "Home Office"

#Add Subnet to Network Location
New-CsTenantNetworkSubnet -Identity 192.168.1.0 -Description "Home Subnet" -MaskBits 24 -NetworkSiteID "Home Office"

#Associate Subnet with LIS Location
Set-CsOnlineLisSubnet -Subnet 192.168.1.0 -LocationId c0139040-8a99-4288-b09b-639b34efb999
Get-CsOnlineLisSubnet

Thanks

Henry

fowler_23

Iron Contributor

Jul 09, 2020

HenryPhillipsNimbitech Thanks for the message.

Yes - I started with defining the Site and Subnet.

However, no emergency policy was assigned to me. Looking at the Teams logs (.....calling.txt). This log shows info about the emergency policy. It shows I matched the Site Match Info but NetworkLocationMatchInfo shows NotMatched

"debugInfo": {
"ncsDebugInfo": {
"trustedIpMatchInfo": {
"publicIp": "xx.xxx.xxx.xxx",
"trustedIpAddress": "xx.xxx.xxx.xxx",
"maskBits": 32,
"reason": "Matched"
},
"siteMatchInfo": {
"ipv4": "xx.xxx.xxx.xxx",
"subnetLengthIPv4": "32",
"subnetId": "xx.xxx.xxx.0",
"maskBits": 24,
"teamsEmergencyCallRoutingPolicyTag": "TeamsEmergencyCallRoutingPolicy=Tenant: Office",
"teamsEmergencyCallingPolicyTag": "TeamsEmergencyCallingPolicy=Tenant:Emergency Call Notification",
"networkSiteId": " Office Site ID",
"enableLocationBasedRouting": false,
"reason": "Matched"
},
"networkLocationMatchInfo": {
"reason": "NotMatched"

It seems I have to add the Set-CsOnlineLisSubnet to match the NetworkLocation but as I say entering the format of 10.10.10.0 doesn't work. I have to add the actual IP I'm using. When I do that, networklocation shows Matched and Emergency Address shows.

HenryPhillipsNimbitech

Bronze Contributor

Jul 09, 2020

Hi fowler_23 ,

So I have had a good play with this as I find Emergency Calling really interesting and it is of course vital to help out the emergency services and those that need there services.

So not knowing if you are based in the US or not but are you using Dynamic Emergency Calling and if so have you specified anything in terms of Trusted IPs. Trusted IPs are what define your corporate network essentially and are vital in terms of the Dynamic Configuration as without this nothing else follows really.

Also when you mention you are unable to specify the subnet, do you mean it actually prevents you PowerShell wise or just that when you do it makes no difference?

I managed to reproduce your issue and for me it was because I seemed to have a conflicting other subnet defined here:

Once removed I could see the Emergency location reflected in the client by going to settings > calls and it was reflected in the log area you sent too.

But ultimately it is possible to define by way of Subnet and not an explicit IP, so don't give up.

Although this is centred around the Dynamic capabilities you may want to take a look at the following as it has some really good content and might spark some ideas: https://youtu.be/LSz8Klbx27M

Thanks

Henry

fowler_23
Iron Contributor
Jul 10, 2020
HenryPhillipsNimbitech

Thanks for your assistance. I have it working now using the subnet defined in networks & locations rather than having to use the exact IP address in there.

I think it could have been the duplication of that subnet in network topology so thanks for pointing that out

I was also defining it when on my company VPN which could have caused issues. By removing any duplicates and testing it on my home network or office network, it's working.

Thanks for the advice.
- Rmac__
  Copper Contributor
  Sep 03, 2020
  fowler_23 Can you provide some details on how you fixed this?
  
  I'm in the same boat, the system requires that you define the network sites and mask bits for the dynamic emergency policies to work, but also define that same network (minus the mask bits some how) for the LIS. Policies are working, it's matching the sites enough to give me the proper policy but the LIS is not matching even though it's in there. Can you provide some direction on how you defined these to setup network sites and LIS database?
  
  "endpointNetwork": "Trusted",
  siteMatchInfo
  "reason": "Matched"
  "networkLocationMatchInfo":
  "reason": "NotMatched"
- HenryPhillipsNimbitech
  Bronze Contributor
  Jul 10, 2020
  fowler_23
  
  Perfect 🙂