Location Services in Teams Understanding and Troubleshooting

Teams Nation & Metaverse One
16 Apr 202245:11

Summary

TLDRThe speaker, an expert in unified communications with a focus on Microsoft since 2005, discusses the intricacies of Location Information Services (LIS) in Microsoft Teams. He explains the importance of location services, particularly for emergency services compliance, referencing theRAY BAUMS Act in the U.S. The presentation delves into the technical aspects of location, including physical and logical locations, managed networks, and the impact of VPNs on location accuracy. It outlines the components of LIS, such as emergency policies, network topology, and trusted IPs. The speaker also addresses the challenges of determining user location, especially with the rise of remote work, and the solutions Microsoft Teams offers, like dynamic location updates and work-from-home mode. The session includes troubleshooting tips for LIS issues and the importance of enabling location services on devices for Teams to function correctly. The Q&A session touches on the use of Teams on mobile phones for E911 services and the limitations of the Teams web client for emergency services.

Takeaways

  • 📍 The concept of location in Microsoft Teams includes both physical and logical locations, which are crucial for emergency services and network management.
  • 🏢 A managed network is one that an organization controls, including its physical infrastructure and public IP addresses, whereas an unmanaged network like a hotspot has a dynamic public IP address.
  • 🔄 The use of a VPN can change a device's logical location, affecting how network traffic flows and potentially altering the perceived location of a user.
  • 🚨 TheRAY BAUMS Act in the United States mandates that devices capable of making emergency calls must be able to route calls appropriately and provide a dispatchable location.
  • 📞 Microsoft Teams can technically determine a user's location for enterprise voice services if the backend is configured correctly, aligning with the legal requirements for emergency services.
  • 🏠 Home networks, especially for senior executives, can sometimes be managed by an organization's IT department, which can complicate location determination when combined with VPNs.
  • 🤔 The accuracy of location information is essential for emergency services to respond effectively; hence, understanding how networks work is critical for location services.
  • 📱 Mobile phones using Microsoft Teams can leverage geocodes to determine location when connected to a corporate-controlled Wi-Fi network, aiding in emergency call routing.
  • 🖥 Desktop applications and IP phones can obtain a Location Information Services (LIS) address, but the latter cannot confirm or edit location details, which are automatically provided.
  • 🛠️ Troubleshooting location services in Microsoft Teams involves checking diagnostic logs for information on location determination, ensuring that network and application settings align with the expected configuration.
  • ⏱️ Location updates should occur automatically when switching networks, such as moving from a cellular network to Wi-Fi, and if not, re-logging into Teams can force a location refresh.

Q & A

  • What are the two main types of locations discussed in the script?

    -The two main types of locations discussed are physical locations, such as homes, offices, and parks, and logical locations, which refer to the networking perspective of where a user is in terms of their network and IP addresses.

  • Why is it important to understand both physical and logical locations in the context of Microsoft Teams?

    -Understanding both physical and logical locations is crucial for accurate location services, which are essential for emergency services routing, ensuring user safety, and complying with legal requirements such as the Ray Baum's Act in the United States.

  • What is a managed network and how does it relate to location services?

    -A managed network is a network that is controlled and maintained by an organization's IT team, including the management of physical infrastructure and public IP addresses. It is important for location services because it allows for the accurate determination of a user's logical location.

  • How does a VPN influence a user's logical location in Microsoft Teams?

    -A VPN can change a user's logical location because it alters the path of network traffic, potentially leading to a different public IP address and thus a different logical location being identified for the user.

  • What is the Ray Baum's Act and how does it impact Microsoft Teams users in the United States?

    -The Ray Baum's Act is a law that went into effect in the United States, which mandates that devices capable of making emergency service calls must route those calls appropriately and provide information consistent with the user's physical location. This impacts Microsoft Teams users by requiring that the technology be able to determine their location for emergency services.

  • What is a dispatchable location and why is it important?

    -A dispatchable location is a specific address that can be used by emergency services to locate and respond to a caller in need. It is important because it ensures that emergency responders can quickly and accurately find the caller, which is a requirement under laws like the Ray Baum's Act.

  • How does Microsoft Teams handle location services for users working from home?

    -Microsoft Teams uses a combination of network configuration, geocoding, and user-entered data to determine the location of users working from home. It allows for the setting of a work-from-home address, uses geocodes to suggest a location, and enables users to manually enter their address for location services.

  • What are the five main components of location services in Microsoft Teams?

    -The five main components of location services in Microsoft Teams are emergency policies, dynamic routing, emergency addresses, network topology, and trusted IPs.

  • How can a user manually enter their location information in Microsoft Teams?

    -A user can manually enter their location information in Microsoft Teams by accessing the location settings within the application, adding their physical address, and saving it for future sessions.

  • What is the purpose of the 'work from home mode' in Microsoft Teams location services?

    -The 'work from home mode' is designed to accommodate users who are working remotely. It allows Microsoft Teams to dynamically determine the user's location based on their current network and IP settings, ensuring that emergency services can be accurately dispatched even when users are not in a traditional office setting.

  • How can an organization ensure that their users' locations are accurately determined by Microsoft Teams?

    -An organization can ensure accurate location determination by configuring their network topology in Microsoft Teams, defining trusted IPs, setting up emergency policies, and verifying physical addresses. They should also train users on how to manually enter or confirm their locations when working remotely.

Outlines

00:00

🗣️ Introduction to Location Services in Microsoft Teams

The speaker introduces the topic of location services within Microsoft Teams, providing personal background information as a long-time expert in unified communications with a focus on Microsoft since 2005. The overview emphasizes the evolution of technology and the importance of understanding the concepts and inner workings of location information services. The discussion differentiates between physical and logical locations, managed and unmanaged networks, and the impact of VPNs on determining one's location. The speaker also touches on the complexity of identifying a user's precise location due to the potential mismatch of physical and logical locations.

05:01

📍 Importance of Location Services for Emergency Services

The paragraph highlights the legal and safety implications of location services, particularly in the context of emergency services in the United States. It references the RAY BAUM's Act, which mandates that devices capable of making emergency calls must route the call appropriately and provide a dispatchable location that matches the user's physical location. The speaker discusses the technical feasibility of determining a user's location when using Microsoft Teams for enterprise voice and the requirement for a verified address to dispatch emergency services. The importance of dynamic and accurate location information for routing emergency calls is also emphasized.

10:03

🤔 Understanding Location Services Components and Pitfalls

This section delves into the components of location services, including emergency policies, dynamic routing, emergency addresses, network topology, and trusted IPs. The speaker explains how physical addresses are tied to users and the routing logic that determines the user's location. The concept of network sites, trusted IPs, and the correlation between a user's public IP and the managed network is explored. The paragraph also discusses the challenges of managing dynamic IPs, especially in home networks, and the role of direct routing and service providers in automating location information services.

15:05

🏠 Working from Home and Location Services Dynamics

The speaker addresses the challenges of implementing location services for remote work, where traditional office-based network configurations are less applicable. The paragraph discusses the need for Microsoft Teams to adapt to a more dynamic workspace, especially since the onset of the COVID-19 pandemic. It outlines the methods by which location can be determined, including static assignment, computer-suggested data based on geo-codes, and manual user input. The importance of accurate location information for emergency services when working from home is reiterated, along with the various policies that can control location settings.

20:06

📱 Client Perspective on Location Services

The paragraph provides an in-depth look at how location services function from the perspective of different clients, including PCs, Macs, mobile phones, and IP phones. It explains the process of location determination based on known networks, geo-codes, and manual user input. The speaker discusses the limitations of the web client for emergency services and the importance of allowing location services for accurate location detection. The paragraph also touches on the troubleshooting process for location services, emphasizing the need for permissions and the use of diagnostic logs to identify issues.

25:08

🛠️ Troubleshooting Location Services

The final paragraph focuses on troubleshooting location services, particularly on Windows PCs. The speaker demonstrates how to access diagnostic logs to identify issues with location services. It outlines the process of searching for specific information within the logs to determine what data is being collected and processed. The paragraph also discusses the importance of location permissions in Windows settings and how they affect the functionality of location services. The speaker provides guidance on what to do if location information is not being captured correctly and offers a quick overview of third-party tools that can assist in validating network information.

Mindmap

Keywords

💡Location Services

Location Services refers to the technology that determines the geographical location of a user or a device and is a core theme in the video. It is crucial for various functionalities in Microsoft Teams, especially for emergency services where accurate location information can be a matter of life and death. The script discusses both physical locations, such as homes and offices, and logical locations from a networking perspective.

💡Unified Communications

Unified Communications is the integration of various forms of communication technologies into a single system. It is mentioned in the context of the speaker's expertise and experience with Microsoft's suite of communication tools. Unified Communications is the broader field within which Location Services operates, aiming to enhance the overall communication experience.

💡Microsoft Teams

Microsoft Teams is a platform that combines chat, meetings, notes, and attachments. It is the central application discussed in the video where Location Services are being explored. The speaker talks about how Location Services in Microsoft Teams can enhance the functionality, particularly for emergency calling features, which is a significant aspect of the platform's capabilities.

💡Logical Location

Logical Location is a term used to describe the network-related positioning of a device, as opposed to its physical location. It is an important concept in the video because it affects how Microsoft Teams determines a user's location, especially in scenarios where the public IP address might change, such as when using a VPN or a hotspot.

💡Emergency Services

Emergency Services are a critical application of Location Services within Microsoft Teams. The video emphasizes the importance of being able to accurately identify a user's location when an emergency call is made. This is particularly important in the United States, where laws like the Ray Baum's Act mandate that devices capable of making emergency calls must be able to route the call appropriately and provide a consistent location.

💡Dispatchable Location

A Dispatchable Location is a specific address that can be used by emergency services to locate the caller. It is a regulatory requirement in certain regions, like the United States, for services to provide this information when a call is made to emergency numbers. The video discusses how Microsoft Teams can provide this information when configured correctly.

💡VPN (Virtual Private Network)

A VPN is a service that allows users to create a secure and encrypted connection over a less secure network. The script mentions VPNs in the context of how they can affect a device's logical location. When a VPN is used, the network traffic flows differently, which can impact the determination of a user's location for Location Services within Microsoft Teams.

💡Home Network

Home Network refers to the network setup in a user's residence. The video discusses how a home network can be managed by an individual or a company, especially for senior executives, and how it ties into the Location Services by potentially being on a managed network with a VPN or a direct connection that affects the logical location of the user.

💡Location Information Services (LIS)

Location Information Services (LIS) is a component within Microsoft Teams that deals with the configuration and management of location data. The video delves into the various components of LIS, such as emergency policies, dynamic routing, and the physical addresses that are used to determine a user's location for emergency services.

💡Work from Home Mode

Work from Home Mode is a setting in Microsoft Teams that accommodates users working remotely. The video discusses how LIS can adapt to dynamic work environments, such as employees working from home, by allowing users to manually set their location or using geocodes to determine their location when they are not on a managed network.

💡Geocodes

Geocodes are the geographical coordinates, typically latitude and longitude, that represent the location of a user or a device. In the context of the video, geocodes are used by Microsoft Teams to determine a user's location, especially when working from home or in other unmanaged network environments. They are a key part of the Location Services functionality for emergency calling.

Highlights

The speaker has extensive experience in unified communications, particularly with Microsoft technologies since 2005.

Location services in Microsoft Teams are crucial for emergency services, with legal implications under the RAY BAUM's Act in the United States.

Location is not just a physical place but also includes logical aspects from a networking perspective.

Different environments like offices, homes, hotspots, and VPNs can influence the logical location and impact network traffic flow.

Microsoft Teams can technically determine a user's location if the backend is configured correctly.

A dispatchable location is required for emergency services, which involves the physical address and its compilation.

Location Information Services (LIS) in Teams involves five main components that interact with each other.

Policies within Teams can notify users or conference them in during an emergency call, depending on the configuration.

Working from home has introduced challenges in determining user locations due to the dynamic nature of home networks.

Microsoft Teams uses various methods to determine a user's location, including known networks, user configuration, and geo-codes.

Client logic in Teams can cache location information for known networks to reduce the burden on the user.

Troubleshooting location services involves checking diagnostic logs for information on location data collection and processing.

Mobile devices using Teams have the ability to pull geo-codes for emergency services, assuming the device's location services are enabled.

The web client for Microsoft Teams does not support emergency services due to browser limitations.

Enabling location services on both the device and within the Teams application is essential for location information to be utilized.

Troubleshooting can also involve using third-party LLDP tools to validate network information for location services.

The speaker provided a comprehensive overview of how location services function within Microsoft Teams, emphasizing their importance for emergency services and legal compliance.

Transcripts

play00:00

today we are going to discuss the

play00:02

exciting parts of location services in

play00:04

microsoft teams

play00:07

i'm me

play00:08

that's who i am

play00:09

some know some do not i live in arizona

play00:13

where it is a

play00:15

a nice 80 degrees

play00:17

today which is clear skies beautiful

play00:19

sunny day

play00:20

um

play00:22

married with a couple boys and have been

play00:23

doing

play00:25

unified communications and specifically

play00:27

focused on microsoft unified

play00:29

communications since 2005 since the lcs

play00:32

day so it's been a long journey with

play00:34

microsoft as an mvp and

play00:37

um

play00:38

and in the field itself so i i'm excited

play00:41

that a lot of the technology that has

play00:43

been worked on in the past is moving

play00:44

forward specifically today that is

play00:47

location information services so enough

play00:49

about me

play00:50

i wanted to start off with the concepts

play00:53

and and

play00:54

and it's typically

play00:56

anyone that's presented or seen my

play00:57

presentations it's typically where i

play00:59

start

play01:00

trying to understand what it is we're

play01:02

doing why we're doing it and the kind of

play01:04

the inner workings of what that is so

play01:06

starting with that whole basis and

play01:08

concept we're going to start with what

play01:10

is a location all right so

play01:12

some of this will be very obvious to

play01:14

some people and to others it will not

play01:16

but a location is more than just

play01:19

a physical place that we're in right so

play01:21

there are offices there are homes there

play01:25

are bars there are parks your home

play01:28

there's your your parents house they're

play01:30

your children's i mean there's right

play01:32

locations can be anywhere that's

play01:33

physical physically where we are at with

play01:36

our computer i'm speaking on our

play01:38

location however there's also the

play01:41

logical location and the logical

play01:43

location is from a networking

play01:44

perspective where are we

play01:46

so

play01:47

when we're talking about an office while

play01:50

that office may be an office we own

play01:53

right it's somewhere that we go it's

play01:54

it's a shared workspace it's not

play01:57

something that we actually manage and so

play01:59

it's not a managed network and

play02:00

controlling

play02:02

what

play02:03

that network is ip wise from a layer two

play02:08

and technically layer three but a layer

play02:09

two perspective of what i p addresses we

play02:12

are we don't always maintain that so a

play02:15

managed office is something that is

play02:17

completely managed it's a network our

play02:20

network team manages the physical

play02:22

infrastructure as well as the public ip

play02:24

addresses how we get to the internet all

play02:26

of that all right then we move off of

play02:29

that concept to a hotspot a hotspot

play02:31

could be a hotspot that you own whether

play02:33

it's your phone whether it is

play02:37

somewhere that is at a coffee house or

play02:40

it is it's whatever it happens to be

play02:42

right it's a hot spot that turns on and

play02:44

turns off dynamically

play02:46

what public ip address you receive when

play02:49

you do that is all is an unknown it's

play02:53

unmanaged you don't manage that

play02:56

and so while you may own the hotspot

play02:59

that you're connecting to and from

play03:00

depending on where that hotspot connects

play03:02

within geographically it can it can get

play03:05

a different public ip address so it's a

play03:07

hotspot that's owned or again in a

play03:09

coffee house where you're just

play03:11

connecting and you're utilizing someone

play03:12

else's network

play03:14

take that same network concept and then

play03:17

add in a vpn on your device and now we

play03:20

technically are in a different logical

play03:22

location because our network traffic

play03:24

potentially is flowing differently

play03:28

there is a lot to be said about split

play03:30

tunneling and breaking off your

play03:31

microsoft traffic

play03:33

in that split tunnel when you are on a

play03:35

vpn so that that's different however

play03:38

that's not always the case so it's

play03:40

understanding and knowing how your

play03:41

network works and does not work from a

play03:44

vpn perspective that rolls right into

play03:46

the same concept of the home network

play03:48

something that's more managed and

play03:49

sometimes even managed by a company

play03:52

especially when we're talking about

play03:53

senior level executives

play03:55

they may have a network that's at their

play03:57

house but i.t of the company manages it

play04:00

much more common in smaller businesses

play04:03

um and and mid-size less common in

play04:06

larger enterprises but it does still

play04:08

happen

play04:09

that home network could be on the

play04:11

physical mpls or sd-wan or

play04:15

a site-to-site vpn connection it could

play04:17

also just be a home network that's

play04:19

that's been configured and set up by

play04:21

somebody that is

play04:23

you know you've said this is the

play04:24

guidelines this is the hardware we want

play04:26

you to use that kind of thing

play04:27

and again is there a vpn is there not a

play04:29

vpn how is that location going to

play04:32

influence us and taking all of that

play04:34

information into account when we go and

play04:36

try to find out where you're at it can

play04:39

get very tricky because

play04:41

obviously

play04:42

you can be any mismatch of any of these

play04:44

physical or logical locations and when

play04:46

we do so uh knowing exactly where your

play04:49

physical

play04:51

physical person is is what we're trying

play04:53

to locate and and the whole point is why

play04:56

right why do we care whoa

play04:59

why do we care where your physical

play05:01

location at and the biggest reason is

play05:03

from an emergency services perspective

play05:05

now

play05:07

from emergency services there is the law

play05:10

of what you have to do which can be

play05:12

what's the driving force in location

play05:14

services there is the because it's the

play05:16

right thing to do

play05:18

and then there is because we're trying

play05:20

to do what what needs to be done to make

play05:22

our our users in a safer place so in the

play05:25

united states

play05:27

the ray bombs act

play05:29

has actually already gone to effect that

play05:31

was earlier this year and in that law it

play05:33

specifically states that if you are on a

play05:36

device that has the potential to call

play05:39

to an emergency services one that

play05:42

service must route you appropriately

play05:45

where technically feasible and two

play05:48

the information needs to be consistent

play05:50

with where you're physically at right

play05:51

needs to be the right location so

play05:55

microsoft technology good and bad here

play05:57

right so the first part being where it

play05:59

is technically feasible well

play06:02

it's technically feasible so if you're

play06:03

using microsoft teams for enterprise

play06:06

voice we can technically find out where

play06:08

you're at if you have configured the

play06:10

back end to do so

play06:12

so we've met that requirement now we

play06:14

have to provide a dispatchable location

play06:17

and a dispatchable location specific to

play06:19

the united states has to do with the

play06:22

address and how the address is

play06:25

physically

play06:26

compiled right so there is the emergency

play06:28

database and that emergency database

play06:31

should automatically be able to hit and

play06:34

look up your physical address to

play06:36

dispatch emergency services

play06:39

so taking all that into consideration

play06:42

i included a link for anyone that really

play06:43

wants to look at the fcc rules for 9-1-1

play06:46

and how this all works but that's there

play06:48

and also wanted to state that there was

play06:50

an earlier law from um before the

play06:53

carries law and this supersedes that and

play06:55

it is much more

play06:57

encompassing so it brings us to a point

play07:00

where every single person that is using

play07:03

microsoft teams with enterprise voice in

play07:05

the united states legally must be able

play07:07

to dial an emergency service and be able

play07:10

to be properly located

play07:13

now

play07:14

what all that means to you and your

play07:15

company how things work that's for your

play07:18

your um legal team

play07:20

for me that's just here's the

play07:21

information take that as you will

play07:23

um

play07:24

beyond that from an emergency service

play07:26

perspective the desire to re receive a

play07:29

dynamic and when i say 9-1-1 we're

play07:31

referring to just emergency services

play07:33

that could be a a 1-1-2 a 1-1-9 that can

play07:36

be whatever the local emergency services

play07:38

is

play07:39

and dynamic depends on

play07:43

what level of dynamic we're looking at

play07:44

right self-made emergency calling is

play07:46

possible and has been for a very long

play07:48

time where we can create a network

play07:50

mapping

play07:52

of our network get our location from

play07:54

that physical logical perspective and if

play07:57

we know what that is we can send and

play07:59

route calls appropriately so from a poor

play08:01

man's emergency services perspective i

play08:03

could have independent

play08:05

gateway set up at every physical office

play08:08

location i own

play08:09

where it's logical to do so and actually

play08:12

send out the call out that gateway and

play08:14

appear that i'm at that location so

play08:15

again i'm actually meeting the criteria

play08:18

of if i'm in this building then i am

play08:20

sending it out this particular network

play08:23

gateway and that particular gateway is

play08:25

tied to this physical address and so

play08:27

everything kind of is kosher but that

play08:29

only works when we're on known managed

play08:31

networks that doesn't work when we're

play08:32

dynamically roaming in a coffee shop on

play08:34

our own networks and so or working from

play08:37

home so getting all of that into play is

play08:40

what we're trying to do with location

play08:42

services

play08:43

okay

play08:45

so with com with location services or

play08:48

lis location information services there

play08:50

are multiple pieces that are configured

play08:53

and of course nothing is simple and they

play08:55

all interact with one another and kind

play08:57

of inner tie so there are five main

play09:00

components and a bunch of subs but five

play09:02

main components of what we're looking at

play09:04

when we're talking about location

play09:06

services right so we have the emergency

play09:09

policies themselves the policies are

play09:13

in the policies group of the voice

play09:15

section as well as well as dynamic

play09:17

routing but those two pieces of the

play09:19

voice are specific to

play09:22

who gets notified when an emergency is

play09:24

called

play09:24

uh

play09:25

when i when an emergency is called right

play09:29

what do i do with it do i allow people

play09:31

to enable the work from home mode or the

play09:34

external location lookup as well as

play09:37

do i need to have some sort of alert or

play09:39

banner inside my

play09:41

um

play09:42

team's um enterprise voice phone app so

play09:46

when i go to the phone's app do i get a

play09:47

banner that has to be cleared that says

play09:48

something whether it be a warning a

play09:50

reminder some information from that

play09:52

perspective

play09:54

the emergency addresses are obviously

play09:55

physical addresses and those addresses

play09:57

should be verified and and known

play09:59

addresses

play10:00

and get entered as they would as they

play10:03

would be passed in what's known as

play10:04

pitfall information

play10:07

um to over the physical network um

play10:11

they have physical addresses are also

play10:13

tied to users right so if we are

play10:15

when we are doing calling plans so when

play10:17

i'm setting up a user and i'm giving

play10:19

them a number from a callings plan

play10:20

perspective i have to set their location

play10:22

that's a static location that i'm

play10:24

setting there and that is at the bottom

play10:25

of the list of our routing logic which

play10:27

we'll get to

play10:28

the network topology itself is your

play10:31

network sites right so these are the

play10:33

offices the physical networks and

play10:35

locations are tied to it's kind of this

play10:36

background robbening and the trusted ips

play10:39

that are tied to that site and when we

play10:40

say trusted ip we're saying when i go to

play10:44

ipchicken or to what's my ip or to

play10:46

whatever on the internet from my pc that

play10:49

physical ip address that i'm presented

play10:51

to to the internet which will be the ip

play10:53

that i'm presented to

play10:54

i'm presented to with microsoft teams

play10:57

isn't an ip that i own if it is then i

play11:00

trust that ip and i can make this

play11:02

correlation right the whole correlation

play11:04

is i have

play11:05

the next section of networks and

play11:07

locations tied i am one of those i am on

play11:10

a subnet i i've defined i'm on a wi-fi

play11:13

access point that i've defined or i'm

play11:15

physically plugged into a switch and a

play11:17

report that i've defined and my public

play11:19

ip is one that's trusted those two

play11:21

things mesh together

play11:23

then i'm on a known network i'm

play11:24

somewhere that i control and i know what

play11:26

that expectation is

play11:29

and again that that known ip ideally are

play11:32

ips that you manage

play11:33

could you

play11:35

put in an ip that's dynamic at some

play11:37

point right so you're using a home based

play11:41

internet at a location and that

play11:43

home-based internet has ip 1.1.1.1 today

play11:48

is there any guarantee that that ip's

play11:50

going to remain because it's not a

play11:52

static ip that's assigned to me because

play11:53

i'm a home

play11:55

network user

play11:56

so do i own that network not really um

play11:59

could i put that in sure

play12:01

managing it may be cumbersome and

play12:03

there's the potential that if it does

play12:04

change and it just happens to have

play12:06

changed when the user dials an emergency

play12:08

call that it doesn't get caught as being

play12:10

a known location so

play12:11

there's that so from again from a

play12:13

network we have subnets very basic we

play12:15

have wi-fi which is our vss ids of

play12:18

whatever network we're connecting to

play12:20

that's not your ssid right that's the

play12:22

bss id

play12:23

switches if you have lldp

play12:26

enabled in your network or your switches

play12:28

are capable and even up to the port

play12:30

so we have the ability to get you down

play12:33

to a physical location from a port

play12:35

perspective if you're plugged in which

play12:37

means i can send and include information

play12:39

to look to information to emergency

play12:41

services

play12:42

that is down to the physical office on

play12:44

the plug that i'm plugged into very very

play12:46

minute or

play12:48

very broad from a specific of this

play12:50

subnet is in this entire wing or floor

play12:53

or building as the case may be

play12:56

to even a little bit more granular when

play12:58

i'm in it with a wi-fi access point and

play13:00

i've got 30 of them across my building

play13:02

if i'm on this one that means i'm on

play13:04

floor

play13:05

x with

play13:07

wing b or whatever the case may be right

play13:08

but we can get more granular so we go

play13:10

from less granular to more granular as

play13:12

we go down that road and then the final

play13:14

thing that i often forget that's part of

play13:16

the emergency services is if we're doing

play13:19

direct routing which

play13:21

a lot of

play13:22

this uh you know i would think people

play13:24

are using but maybe not but from a

play13:26

direct routing perspective

play13:28

if you are using a service provider that

play13:31

can understand this information to

play13:33

automate the location information

play13:34

services

play13:36

then ideally

play13:37

which is an ideal world then ideally

play13:40

you have configured your sbcs

play13:42

and the configuration within direct

play13:44

routing to say include this information

play13:46

if not if you don't click this on and

play13:47

say yes include the pitfall information

play13:50

then in fact it just doesn't get sent so

play13:52

you could configure everything the user

play13:54

could be configured to know their

play13:56

location but when they dial an emergency

play13:58

call that emergency location doesn't

play14:00

actually flow outbound all right it's

play14:02

tagged into the sip information so those

play14:04

are your various components and before

play14:06

we get to the work from home we're going

play14:08

to try

play14:10

to share

play14:13

an application to show you visually what

play14:16

i'm talking about because i think it

play14:18

would it helps me to kind of run through

play14:21

what it is we're referring to so if

play14:22

we're looking at in my tenant the

play14:25

various policies again here we have our

play14:27

calling policies and our call routing

play14:28

policies that are specific to emergency

play14:31

the value of the call routing policy is

play14:34

if i had multiple locations that had a

play14:38

direct route capable

play14:40

handoff then i could potentially have

play14:44

a call from a certain location route out

play14:48

a specific location and that gives me

play14:49

the ability to to present that call as

play14:52

that location because the calls egress

play14:54

is the actual location that that phone

play14:56

is routing too

play14:57

calling policies include all the

play14:59

information again specific generally in

play15:01

a large enterprise we will have many

play15:03

many emergency policies and those

play15:05

policies will be tied to

play15:09

the user's location typically and that

play15:11

comes down to this notification mode

play15:13

where we are notifying a user or users

play15:17

when somebody dials an emergency number

play15:20

that that person has in fact done so

play15:23

it sends a team's notification they

play15:25

realize hey sally down in office a in

play15:29

florida dialed 9-1-1 i'm in the florida

play15:31

office i'm security of florida i need to

play15:33

be aware that that's happening and to be

play15:35

on the lookout so that when emergency

play15:37

services do arrive i can correctly

play15:39

direct them to the correct location that

play15:41

kind of information depending on the

play15:43

provider if you're tied into one that

play15:46

has and uses the emergency location

play15:48

information we also have a notification

play15:51

mode and the notification modes allow us

play15:53

to actually conference someone in and

play15:55

that's typically again an

play15:56

emergency or a security desk or somebody

play15:59

that's handling emergency calls call

play16:01

comes in they all get conferenced in and

play16:03

it creates a nice scenario but that's

play16:05

what that is here's the external

play16:07

location lookup mode we talked about the

play16:09

the location mode is the work from home

play16:11

mode we're about to speak on so that is

play16:13

our emergency policies area so when

play16:15

we're talking there again direct routing

play16:18

and then our location so all of the

play16:19

locations that we were discussing are

play16:21

located here okay let's jump back to the

play16:24

deck

play16:27

and

play16:30

maybe

play16:34

maybe

play16:37

it doesn't want to play

play16:38

there it goes

play16:41

maybe

play16:43

or maybe not

play16:45

yeah

play16:46

sometimes maf is low you know yeah it is

play16:49

it's like load and go load and go and it

play16:52

doesn't want to

play16:53

okay

play16:57

it says it's loading

play16:59

and powerpoint lines coming back up

play17:01

there we go okay

play17:03

so working from home so working from

play17:05

home the whole concept of working from

play17:07

home is not new right i mean obviously

play17:09

there have been people working from home

play17:11

remotely for a very very long time

play17:13

however

play17:14

when the pandemic started way back when

play17:16

it seems like forever ago

play17:19

in 2020 that kind of accelerated the

play17:21

whole concept of now everybody's working

play17:23

from home and so because we're working

play17:25

from home how do we accommodate

play17:28

a more dynamic workspace so now while we

play17:31

can define and we've gone through we can

play17:33

set subnets we can set our our physical

play17:35

switches to gather information we know

play17:37

where you're at well now we don't know

play17:39

where anyone's at because everybody's

play17:40

working from home so you went from

play17:42

trying to get most people covered to now

play17:45

nobody's covered and so microsoft was

play17:47

looking at methodologies and changes to

play17:49

the application to say how do we make

play17:51

this an easier solution for users that

play17:53

don't burden the user that they're

play17:55

constantly changing things looking for

play17:57

updates so

play17:58

there are definitely a lot of parts of

play18:01

the whole lis world

play18:03

and there's policies that can control

play18:05

can you even set a work from home

play18:07

address because there may be reasons

play18:08

that you don't want to but assuming that

play18:10

that's that button is on

play18:12

and you have you configured your your

play18:15

physical internal network and your pc

play18:17

allows it to look up its own location

play18:19

then you have the options of a

play18:22

physically controlled location that

play18:23

you've managed a customer or client

play18:26

entered data and a computer suggested

play18:30

data be invited geo codes and that that

play18:32

precedence of how that's identified and

play18:35

how we decide what's important goes

play18:36

through the list of the company what

play18:38

they say is your location is primary

play18:41

past that

play18:42

if the computer can figure out where

play18:43

you're at from a geo codes perspective

play18:45

your latitude and your longitude we'll

play18:47

use that

play18:48

if that's not correct then we look to

play18:51

see can you um have you put in

play18:53

information that is statically assigned

play18:56

so this would be from your calling

play18:58

plan's perspective if that user's there

play19:00

if not okay so we don't know where

play19:02

you're at so that's where it follows

play19:03

through the

play19:04

the actual lookup client codes and we'll

play19:07

actually look at that logic a little

play19:08

deeper now so um client logic is and

play19:11

this is from microsoft's little blur i

play19:13

just copied and pasted so this is not

play19:14

something that um is created by me but

play19:18

from

play19:19

there's two various ways clients look at

play19:22

their location right have i been on this

play19:25

this physical logged into teams before

play19:27

and have i been able to identify myself

play19:30

do i know who i am

play19:32

do i know the network i'm on

play19:34

and have it

play19:36

is that known information so that would

play19:37

mean i've logged into this specific pc

play19:40

from this specific teams application and

play19:42

it has cached this information that that

play19:45

knows where i'm at or is it new which

play19:47

isn't the case i've never done any of

play19:48

those things one of those variables is

play19:50

off so i've logged into this location

play19:52

before but it's a new pc or it's a

play19:55

different pc or whatever the case may be

play19:57

i've cleared out my cache could be

play19:58

potentially another one but from a

play20:01

client perspective it looks like a brand

play20:03

new

play20:04

network right

play20:06

so from that if an admins define the

play20:08

network it's the li information the lis

play20:11

information is from your clients um

play20:13

collected my public ip as well as my

play20:15

private as potentially your bss id

play20:18

potentially your your

play20:20

ldap not

play20:22

lldp not all that lldp information

play20:25

potentially all of that's gathered it's

play20:26

pushed up to microsoft it kind of turns

play20:28

on and says oh i know where you are and

play20:30

it sends down your location and stamps

play20:31

it all good

play20:33

second option is

play20:35

the admins define your

play20:37

dynamic location but it's not one of

play20:38

them

play20:39

teams wasn't able to get geo codes so

play20:42

you're you maybe you don't allow it on

play20:44

from a pc perspective

play20:46

by policy or just because you guys

play20:48

haven't

play20:49

and so the end user is allowed to put in

play20:51

their information they type in their

play20:53

address they save it it's cached the

play20:55

next time

play20:56

we log in it may have that information

play20:58

that matches but that's the physical

play21:00

location you're at during that specific

play21:02

session and the third one is we don't

play21:04

get anything dynamically bad but the os

play21:07

does provide geo codes at that point we

play21:09

will get a screen pop that says hey it

play21:11

appears you're here and you either

play21:12

confirm or edit that is the place that

play21:14

you're actually at and depending on

play21:17

logic of which one of these were chosen

play21:19

depends on how

play21:21

confident microsoft is where you're at

play21:23

and how the routing and logic will

play21:25

happen so if it is a high probability

play21:29

or confidence a hundred percent are

play21:31

higher then guess what that call is

play21:33

going to route itself automatically to

play21:35

your service provider um or in the psap

play21:39

right where it's going driving directly

play21:41

to them there's no interaction it just

play21:42

works if we're not sure where you're at

play21:44

then different routes are going to be

play21:46

taken but the whole point is we're

play21:47

trying to be as specific as possible and

play21:50

as ideological as possible that we get

play21:52

to where you are so let's look at those

play21:54

different clients from a client

play21:56

perspective now these are screenshots

play21:57

because trying to switch off networks to

play21:58

make this happen won't work

play22:00

but

play22:02

option number one so the admin has

play22:03

configured your network they're your

play22:05

location they have gone through the

play22:07

process and set up your known ip

play22:09

addresses and either subnet or some

play22:12

information we're here we're not getting

play22:14

into that we're just getting that it's a

play22:15

configured location

play22:17

when that happens and the client logs in

play22:20

what we're looking at is down here in

play22:22

the bottom left hand corner

play22:24

so you'll notice one that in purple

play22:26

you have a physical address that's

play22:28

pushed back to you that should be the

play22:29

address you're at if you're not you need

play22:31

to reach out to your admin and say hey

play22:32

something's wrong here you're actually

play22:35

assigned an address that's not correct

play22:37

to my location

play22:38

two you will notice that it is showing

play22:40

you that the current location is a work

play22:43

provided location you and it grayed out

play22:44

there's nothing you can do about it

play22:46

the work is said this is where you're at

play22:48

so therefore that is where you're at it

play22:50

is a confident location based off

play22:52

configuration again assuming the

play22:54

configuration is correct but the key

play22:56

here is that it's not something that we

play22:57

can modify because it is a location that

play22:59

has been pushed down by the admin it's

play23:01

not something we need to even think

play23:02

about all right it's just done

play23:03

automatically on our behalf

play23:05

okay looking at option two where the

play23:07

user is configuring it so in this case

play23:09

no geo codes no known location by the

play23:12

admin what does the client look like

play23:14

here and if we look initially we have at

play23:18

the very bottom left where it says

play23:19

location not defined right we don't know

play23:21

who you are we don't know where you're

play23:22

at all we know is that teams is running

play23:26

that's it and you're on somewhere we

play23:28

don't we're not sure where that's at

play23:30

if i click on the button i get the

play23:32

current emergency location you'll notice

play23:34

i have a plus ad the whole ad concept is

play23:37

to add my physical address it's a whole

play23:38

manual process to do so and when i click

play23:41

it i get the whole new location box now

play23:43

the location box is broken up into what

play23:46

would be considered the format

play23:48

the location services are looking for

play23:51

so if this does get passed to an

play23:54

emergency help desk

play23:56

that goes outbound to the emergency

play23:57

services they will get your information

play24:00

if they support pitfall but it's not

play24:01

going to be a verified address but it

play24:03

will allow them to say hey this is what

play24:04

i see you entered

play24:06

um

play24:07

if you're assuming that we can talk

play24:09

while you're on this 911 call or

play24:10

emergency call i see that the

play24:12

information you entered is x is that

play24:14

accurate if it is great they punch it in

play24:17

their database it pulls up the actual

play24:19

location that they're looking for from a

play24:21

verified address perspective and they

play24:22

can dispatch so it helps speed up that

play24:24

process

play24:25

um it also helps um if it's right right

play24:28

so the more accurate and more precise

play24:30

you are in the information that you're

play24:32

putting here obviously the better

play24:35

number three is once i put in that

play24:36

information i can click add and once i

play24:39

click add you'll notice at the bottom it

play24:41

now looks similar to the very first

play24:43

slide right

play24:45

however if i click on the address i have

play24:47

an edit or a reset so

play24:49

if i've done something wrong

play24:51

the most common times this will look

play24:53

wrong in my experience has been when you

play24:55

are on a hotel network and that hotel

play24:58

network constantly uses the same ip

play25:00

addresses and it just gets confused um

play25:03

sometimes we just reset stuff and do

play25:05

edit or and and put a new one back in

play25:07

if in fact that's what we're trying to

play25:09

do so

play25:10

that is from a user configured

play25:11

perspective what that looks like or

play25:13

option two again we don't have geo codes

play25:15

we don't know anything about where

play25:16

you're at

play25:17

and off we're going now option three

play25:19

using geo codes is a uniquely new

play25:21

feature that in my experience works

play25:25

never but

play25:27

it's supposed to work so

play25:29

i actually don't have a working

play25:30

screenshot because i can never get it to

play25:31

work and there's an open bug that i have

play25:33

on this but

play25:35

when your box throws its geo codes to

play25:38

the service microsoft's back end takes

play25:41

those coordinates right latitude and

play25:42

longitude looks it up in their database

play25:44

and pushes back a physical address

play25:47

um and we'll see in logs where the

play25:49

client definitely knows its geo codes

play25:51

it's being able to pull that information

play25:53

it's definitely sending it off to

play25:54

microsoft and then it just gets a

play25:56

timeout and doesn't get a response so

play25:58

unfortunately that is what it is but if

play26:01

you notice here there's a couple things

play26:02

one the traditional location icon is

play26:04

shown i'm next to the address the

play26:06

physical address where they believes

play26:08

you're at shows up and assuming that's

play26:10

where you're at you can click confirm

play26:12

and you are on a

play26:14

physical location that's not always

play26:16

accurate keep in mind that your ip

play26:18

address and your locations and how this

play26:20

works and where this goes

play26:23

you know it's up to up to the device

play26:25

you're using from a precision

play26:27

perspective i think probably even more

play26:29

important is satellite information and

play26:32

and location information typically

play26:33

doesn't pinpoint down to the

play26:36

the one by one meter space that you're

play26:38

at but rather it is kind of a general

play26:41

circle or error so is it the right

play26:42

address is it not is it close is it not

play26:44

we can edit this address um

play26:46

instead of just leaving it as is

play26:49

but it's doing its best to know where

play26:50

you're at so those are the three client

play26:53

looking options when we're new but what

play26:54

if we're known so it simplifies things

play26:57

if the if it's a known network and then

play26:59

by a no network it means

play27:01

you're logging back into this pc again

play27:03

or this application and this has

play27:05

happened before we've seen you right the

play27:08

your physical public ip address and your

play27:10

physical ip that's your your personal

play27:12

life address they match hey and you have

play27:14

cached information that you said this is

play27:16

where you're at well it'll bring it all

play27:17

back and this is part of

play27:19

eliminating or limiting the burden onto

play27:21

the client where if i'm working from

play27:23

home and i've put this information in

play27:24

once well then every time i go home with

play27:26

my laptop it should just show that as my

play27:28

location and it should assuming nothing

play27:30

changes

play27:31

that constantly will be there so

play27:33

again i go somewhere with my pc

play27:36

it will still check to see is this a

play27:38

something that's on the um defined

play27:41

network and we do that because hey

play27:44

what if something's changed in the back

play27:46

end and your subnetting has changed

play27:48

where you used to be building x was uh a

play27:51

10.1.1 now you're 10.1.2 well hey then

play27:54

let's go ahead and

play27:56

take that information

play27:58

from the service and push it back down

play28:00

to overwrite your cache so it does

play28:02

verify that that's still statically the

play28:04

same if it is otherwise if it's not

play28:06

something that's set there we just pull

play28:08

your information and from your cache and

play28:10

bring up your location so it's a it's a

play28:12

much quicker process and less

play28:15

okay so that's all from the client

play28:17

perspective

play28:18

that's all great so

play28:20

um

play28:21

some additional thoughts and processes

play28:23

on this whole concept is working from

play28:25

home

play28:26

works from your pc and your mac so

play28:29

if you have a a macintosh or a

play28:33

microsoft based personal computer a pc

play28:35

you're using microsoft teams natively on

play28:37

that machine so it can pull your

play28:39

information and location and everything

play28:41

happy and go lucky well great then

play28:43

that's going to work

play28:44

mobile phones if you're running teams

play28:47

from a work from home from look from any

play28:49

location right a mobile phone if it can

play28:53

pull to your lis location which would be

play28:55

i'm on a physical

play28:57

network i have my physical phone my

play28:59

physical

play29:00

mobile device is connected to wi-fi that

play29:03

wi-fi is a network that is controlled by

play29:05

the company well guess what that address

play29:07

is pushing down to the to that device

play29:09

and you can actually see it in the

play29:10

calling

play29:12

if it gets it by geo codes which it can

play29:14

do as well

play29:15

it's supposed to show that address but

play29:18

it doesn't always so there's a little

play29:19

work being done there but it's same

play29:21

thing so the mobile phone can use geo

play29:22

codes and the mobile phone can use ls

play29:24

but you can't manually enter that

play29:25

information that's not an option for you

play29:28

last would be your ip phones right so

play29:30

your poly

play29:31

your audio

play29:33

codes

play29:34

your

play29:35

sennheiser yay link

play29:38

etc those physical phone devices your

play29:40

desktop phones they can get an lis

play29:42

address but they don't enter confirm or

play29:44

edit anything it's just what they get is

play29:46

what they get

play29:48

generally speaking

play29:50

they maintain that information

play29:52

all the way down to your uh lldp

play29:55

information that comes however we have

play29:57

seen where it reverts back to subnet

play29:59

every so often um

play30:01

and typically it has to do with

play30:04

the network itself or the device there's

play30:06

multiple ways but the phone should be

play30:08

able to pull your lis location

play30:11

and then finally again geocodes they do

play30:13

require that you allow your pc

play30:17

one to get its location and two to allow

play30:20

the application to pull the location

play30:21

whether it's on your phone or with

play30:23

mobile phone or whether it's on your pc

play30:24

so that's just one of those things that

play30:26

if you're not going to allow it to find

play30:28

your location because location services

play30:30

are either disabled or very limited then

play30:32

it's not going to be able to get geo

play30:33

codes

play30:35

lastly i'll say

play30:37

if i'm on a device and i jump from

play30:39

network to network so i like a mobile

play30:41

device i'm outside um my office building

play30:44

i am on cellular network i walk into my

play30:47

office building it jumps on the wi-fi if

play30:49

teams was open that physical address

play30:52

should be updated within two to five

play30:54

minutes

play30:55

and i say should because i typically see

play30:58

it updated within around 30 seconds it's

play31:00

actually very quick but i will also say

play31:03

when i don't see it update it doesn't

play31:04

have ever updated just it seems to be in

play31:06

a stuck state logging out of teams

play31:09

re-logging in will cause that location

play31:11

service to re-pull its location and use

play31:13

its logic and that'll fix it but

play31:16

it should be an automatic process but

play31:18

again keep that in mind so

play31:20

that happens obviously mobile phones

play31:22

desktop applications whatever it is that

play31:24

you're jumping between networks so

play31:26

okay so now off to the fun part

play31:28

troubleshooting so

play31:30

troubleshooting we're going to focus on

play31:33

the

play31:34

windows pc because that's what i'm on

play31:36

and that's easier to do

play31:38

since that's what i have to show um

play31:40

control alt shift one the old key

play31:42

sequence to pull down those diagnostic

play31:44

logs or on the mac option command shift

play31:46

one

play31:47

that is where we get the information

play31:49

right that things are coming up

play31:51

they dumps to on a windows machine to

play31:53

your user profile your downloads folder

play31:56

and then it's creating the logs and then

play31:58

in a couple seconds it moves all the

play31:59

logs to a subfolder called ms teams

play32:01

diagnostics logs and the date and time

play32:03

they were captured at so there will be a

play32:04

nice little folder for you to go look

play32:06

into and there'll be a bunch of sublogs

play32:07

within there the two that we care about

play32:10

are in a subfolder called web and then

play32:12

the main microsoft teams diagnostic log

play32:15

followed by date and time capture and

play32:17

the exact same log followed by

play32:19

underscore calling those two logs will

play32:21

show us what we're looking for from an

play32:22

information perspective so

play32:24

rather than just talk about it i want to

play32:26

show how that actually looks i do set

play32:28

that when you guys are opening up and

play32:30

looking at things search on set location

play32:32

info will get you into the information

play32:34

you're looking for so that's typically

play32:35

what i do when i'm looking for am i

play32:37

actually getting location right so i've

play32:39

configured everything i've set up my

play32:41

machine i plug it into the network i'm

play32:43

on a known network and nothing happens i

play32:45

don't get a location why well

play32:48

let's go ahead and try to switch sherry

play32:51

now to

play32:53

this tool

play32:54

now

play32:55

this happens to be um sccm's

play32:59

logging tool right parsing tool that's

play33:01

what i like to use there are all kinds

play33:03

of things you can open things on notepad

play33:04

you can open things and a visual be

play33:07

decoder there are

play33:09

there's all kinds of different ways to

play33:10

look at whatever you're like no plan

play33:12

notepad plus

play33:14

again i don't care do whatever it is

play33:16

that you like to do um this happens to

play33:18

be that the one that i'm looking at

play33:21

because i like it for all logs it works

play33:24

seems to work anyway that's what i'm

play33:25

using so that's what anyone's looking

play33:26

for today it's the sccm or the endpoint

play33:29

configuration manager that free tool

play33:31

that comes with sccm okay so i'm looking

play33:34

at my my various log and this particular

play33:36

one

play33:37

as i pulled it up is the main

play33:39

diagnostics log

play33:41

i i named it on-prem and subnet because

play33:43

i've got to keep these things separated

play33:45

but it's a fairly large log it's about

play33:47

three megs in size and there's a lot of

play33:49

information right this is where we're

play33:50

setting our policies and things are

play33:52

going so if i do a search

play33:54

for set location info i'm going to jump

play33:56

down to the towards the bottom of where

play33:58

i'm looking for

play34:00

when i get to this information

play34:02

i can see what data

play34:05

teams is figuring out and sending back

play34:07

up to the service the parsing of that

play34:09

data will be in the calling log but we

play34:10

if it doesn't always get that far right

play34:12

so starting here will tell us what data

play34:15

is actually being collected

play34:16

and if i look i can see that from this

play34:19

particular network this pulled my

play34:21

location

play34:22

of my physical ip address my physical

play34:24

mac address my subnet and you can see

play34:28

geo coordinates were pulled as well so

play34:29

that is configured and let to go and i'm

play34:31

not a calling plan user that's led it

play34:33

knows here right um 911 is different so

play34:36

it's trying to figure stuff out

play34:38

um my location was in cash

play34:40

and it comes back again with my

play34:43

my subs and this information gets pushed

play34:45

back up

play34:46

so

play34:48

basic information of what's being

play34:50

captured is gathered here

play34:52

and then we will quickly look at

play34:56

if we can get the calling log

play34:58

which is if there is one with data

play35:01

probably where i would start to see what

play35:03

information is being processed from the

play35:06

cloud right

play35:08

so i look at the calling log you'll

play35:10

notice that it's broken it down into

play35:12

okay so this is just specific to what

play35:14

has to do with my call i haven't made

play35:16

any calls all i've done is log in so i

play35:18

found out that i have an emergency

play35:20

numbers right so when i dial this

play35:21

particular pattern that's seen as an

play35:23

emergency number my policy that's been

play35:25

applied to me

play35:27

if there's a mass that's applied and

play35:28

where it routes out all of those

play35:30

informations that right while awesome

play35:32

don't really apply to us at this moment

play35:34

unless we're not getting the

play35:35

notifications and things that we're

play35:36

looking for

play35:38

our latitude and longitude is a trusted

play35:40

network right we know that we're on a

play35:42

trusted network and we know that because

play35:45

the public ip is matching

play35:47

but here's our latitude and longitude

play35:48

provided the address that pushes back

play35:51

from our information and you can see i

play35:53

have

play35:54

from an additional info this is our sub

play35:56

info it's just in this office 16

play35:58

somewhere within the suite of offices

play36:00

but i don't actually

play36:01

go beyond the sub offices within this

play36:04

location because it is being

play36:06

brought to us by again here's our

play36:08

matched public ip address

play36:11

and more importantly the sites being

play36:14

matched on subnet so we can find out

play36:17

that the subnet is what's matched we're

play36:19

on this particular one right we have a

play36:21

match there we have a match on the

play36:23

trusted information

play36:24

and i have a location id all right so

play36:26

that doesn't mean much to you but we'll

play36:28

show back quickly at the end if we have

play36:31

time that those ids are actually visible

play36:34

within teams admin center when you

play36:36

create a location that's the idea it's

play36:38

given so that's that's how we match that

play36:39

up and it actually brings back

play36:41

this physical address right okay so

play36:44

that's when we're on prem when i'm

play36:46

working from home

play36:48

i don't get a calling logs specific to

play36:52

this information because none of this

play36:53

calling information none of the lis has

play36:55

done well i find it interesting that it

play36:57

doesn't show you that it failed it just

play36:59

doesn't show you that anything happened

play37:00

because nothing happened um so we start

play37:04

with your location is unknown right we

play37:06

don't know who you are we don't know

play37:08

where you're at um everything is unknown

play37:10

it's no no no no out once we get that

play37:12

unknown information we then come down to

play37:15

what is the information that we have

play37:16

well we do know your mac address we know

play37:19

that you're on an ssid of this was my

play37:22

phone that i was coming through

play37:24

um your subnet your geo code so you have

play37:26

latitude and longitude still

play37:29

and

play37:29

what would be applied from an emergency

play37:31

calling perspective now i've set my

play37:33

stuff to global so the global policy is

play37:35

still going to apply

play37:36

but that information is coming down but

play37:38

more importantly i'm on a public network

play37:41

and there is no information here to tell

play37:43

me who or what i am and so there's no

play37:44

way for this to automatically pull

play37:46

anything out and so if i jump to my

play37:48

calling log and look at the log specific

play37:51

to this

play37:52

calling working from home

play37:54

there's nothing there it didn't process

play37:56

anything it didn't look at anything

play37:58

there was nothing to be found

play38:00

automatedly okay so those are the two

play38:02

kind of when we're looking at things a

play38:04

big gotcha if we have a calling log

play38:07

we've just logged in and pulled

play38:08

diagnostics right so we've logged in

play38:10

we've waited about a minute control

play38:12

shift one we go to our calling log

play38:14

nothing's there

play38:15

more than likely something's not getting

play38:17

caught and we'll need to back up to the

play38:19

other logs

play38:21

well that i did not mean to do

play38:24

so

play38:25

let's try that again

play38:28

all right

play38:30

and so

play38:31

the last three will just

play38:33

it's more interesting than anything else

play38:35

um to show that we actually have

play38:38

data that's being captured um

play38:42

and how it's being seen differently so

play38:44

if we look at

play38:46

the

play38:47

wi-fi and we'll just look at the calling

play38:49

side of things of where things are

play38:50

captured

play38:55

a lot of it looks the same and what

play38:56

we're looking for once we get down to

play38:58

this trusted information again

play39:00

interestingly this confidence is low on

play39:02

these these geocodes being actually in

play39:05

this site id however

play39:07

we do have as we move down the

play39:10

patch we match on subnet but we also

play39:13

match on the chassis id now this is the

play39:17

switch one yep so we match on chassis we

play39:20

also match on subnet well chassis is

play39:21

more specific or potentially more

play39:24

specific than our side id and so we

play39:26

actually pushed back our location id

play39:28

that matches that specific um chassis or

play39:31

switch right and that one happens to be

play39:34

the exact same thing it is no more

play39:35

granular that switch is just in this

play39:37

location but

play39:38

we do find both answers in that specific

play39:41

scenario

play39:43

also of interest here will be

play39:45

[Music]

play39:52

nothing

play39:53

that's all that i'm going to show of

play39:54

interest in this one however we will

play39:56

show

play39:58

the port that if we've defined the

play40:00

actual port and we support lldp that

play40:03

when we search on on it

play40:06

we get information back and this

play40:08

information is physically within the

play40:11

calling log 2 of the switch

play40:13

capture but because the port wasn't

play40:15

defined

play40:16

in

play40:18

the tenant right in admin center it

play40:20

doesn't even bother to try it just

play40:21

brings it back but you can see here that

play40:23

we bring back the chassis id and the

play40:25

port that we're physically on sunday and

play40:27

everything that else comes back and so

play40:29

we have the ability to do so and then

play40:30

finally as we're out of time let's go

play40:33

ahead and quickly look at our wi-fi and

play40:36

when we're looking at wi-fi the

play40:37

interesting part here is let me roll

play40:40

down to it

play40:41

again we find the bss id the bsi sid

play40:45

matches we have a location id so all of

play40:47

that follows down the same scenario

play40:50

we only see in the calling log what's

play40:51

been parsed so if you're missing

play40:53

information validate that you're getting

play40:55

it

play40:55

one way to do so and one of the things

play40:57

that we want to quickly touch on because

play41:00

we are out of time and i apologize but

play41:03

um we do have the ability to

play41:06

uh

play41:07

back to

play41:08

[Music]

play41:09

we will we won't be sharing the deck so

play41:11

there is that um and a lot of the

play41:14

information that's in here is

play41:15

specifically because of there's

play41:17

links and copies and information that

play41:19

hopefully are of value

play41:21

but

play41:22

when we're looking at

play41:24

the information here

play41:28

okay so we've done that troubleshooting

play41:30

there is a third party lldp tool

play41:33

hell

play41:34

is the one that

play41:36

sponsors this they have the ability to

play41:38

do a discovery you can install the

play41:40

module import the module and then you

play41:42

can evoke it it basically listens to the

play41:44

network traffic and then brings back

play41:46

what your actual lldp information you

play41:49

see because if you don't see the

play41:50

information well then we can kick it

play41:51

back to being the network team that's

play41:53

the problem we're not getting things

play41:54

back but we should get back your switch

play41:56

your port your chassis id all that

play41:58

information and it's a great way to

play42:00

validate that things are working on

play42:01

specific subnets or network chassis that

play42:03

you're

play42:04

working on

play42:06

the demo is just to run that so for

play42:07

other time we'll skip that and finally

play42:10

the windows location if you're not

play42:11

seeing your geo code this is windows 11

play42:13

same applies to windows 10

play42:15

ios and android have the same location

play42:18

restrictions as well

play42:19

if we don't have location services even

play42:21

enabled but then we don't allow it per

play42:23

application we're not going to allow it

play42:25

to actually do anything so if i click

play42:27

this on and i and i relaunch

play42:31

teams it will immediately try to pull

play42:32

location again and you'll notice teams

play42:34

will show up in the bottom when it lasts

play42:36

pulled and it'll start to gather

play42:37

information so if we don't allow that to

play42:39

happen you're not going to get geo codes

play42:41

and things aren't going to pull so with

play42:44

that

play42:44

we have the end of our session and we

play42:46

will open for some

play42:48

couple of minutes because we're out of

play42:50

time but a couple of minutes of q a if

play42:51

there are anything that's in the queue

play42:54

yes

play42:55

yes there are a couple of questions in

play42:57

the chat

play42:58

we'll try to hurry

play43:00

yeah so uh one second so the course the

play43:03

first question would be

play43:06

uh what happens when i use teams on a

play43:08

mobile phone with e911

play43:11

yep so

play43:12

same thing um mobile phones today have

play43:14

the ability to the mobile application to

play43:17

pool your geo codes and so it will pull

play43:20

just like on your your cellular phone

play43:22

would

play43:23

many will say why use teams to call

play43:25

9-1-1 if you're on a mobile phone just

play43:27

use the dialer that's built into your

play43:29

dialer but it does have the ability to

play43:31

pull geocodes and again if you're

play43:33

on-prem in a known location using wi-fi

play43:36

it'll pull that location too and send

play43:37

that information

play43:40

thank you and we have one more question

play43:43

how does team web climb determining

play43:45

locations end users set

play43:50

will it try

play43:52

um ls based on the hosts network

play43:54

information

play43:58

so if i understand the question

play44:00

how does the

play44:01

how does the client determine its

play44:03

location

play44:05

yeah the question is how does team's web

play44:08

client determining location oh the web

play44:11

client okay

play44:12

does not yeah web client is excluded web

play44:14

client does not work so the actual

play44:17

emergency services from a web client

play44:20

is not an option so unfortunately

play44:24

they don't have the ability to make the

play44:26

same calls to the

play44:28

network to find your information right

play44:30

the actual application

play44:32

being the browser isn't allowed and

play44:35

blocked and that doesn't work so the web

play44:36

client is excluded from

play44:38

applications at work

play44:41

thank you very much bran um thank you

play44:44

everyone for your attention and for

play44:46

being present at this session

play44:49

i have placed a link for rating this

play44:52

session and

play44:53

please if you would like to give us a

play44:55

feedback because it means a lot to the

play44:57

speakers and to us as well

play45:00

so yes thank you once again bran for the

play45:02

awesome session

play45:05

and

play45:06

i wish you a great rest of the day

play45:09

great thanks everyone

Rate This

5.0 / 5 (0 votes)