Ah, the old emergency calling conundrum. I'm with you guys on option B. Can't go wrong with a custom emergency calling policy. Although, if I was the one configuring this, I'd probably also throw in a nice little Easter egg for the end-users, like a dancing emoji or something. Really spice things up, you know?
Hmm, I was thinking option C might be the answer. Dynamic emergency calling seems like it could be the right approach for external users. But you both make a good case for option B. I guess it really depends on the specific requirements of the deployment.
I agree, option B seems like the way to go. Enabling external location lookup mode is key here. Although, I'm a bit surprised they're not asking about Location-Based Routing, since that's a common requirement for emergency calling.
This question seems straightforward, but it's testing our understanding of emergency calling in Teams. I'm leaning towards option B - creating a new emergency calling policy with external location lookup mode enabled. That way, external users can manually configure their emergency address in the Teams client.
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Jamika
11 months agoJohnna
11 months agoCorazon
11 months agoArthur
11 months agoMertie
11 months agoEdda
11 months agoAlline
11 months agoClorinda
11 months agoJutta
11 months agoRicki
11 months ago