New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft MS-721 Exam - Topic 2 Question 47 Discussion

Actual exam question for Microsoft's MS-721 exam
Question #: 47
Topic #: 2
[All MS-721 Questions]

You have a Microsoft Teams Phone deployment.

You are deploying Direct Routing.

All users have a SIP URI in the format of user@contoso.com. The Session Border Controller (SBC) is named sbc.voice.contoso.com.

When troubleshooting errors on the SBC, you receive the warning shown in the following exhibit.

What is a possible cause of the issue?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

0/2000 characters
Celestine
2 months ago
I agree, licenses should be assigned first before troubleshooting.
upvoted 0 times
...
Katy
3 months ago
Wait, are licenses really that crucial for this to work?
upvoted 0 times
...
Carmela
3 months ago
Sounds like a certificate issue to me.
upvoted 0 times
...
Leonard
3 months ago
Definitely check the TLS settings, could be outdated.
upvoted 0 times
...
Flo
3 months ago
I think it might be the firewall blocking traffic.
upvoted 0 times
...
Tasia
3 months ago
I feel like licensing could be a factor, but I thought that was more about user access than SBC errors. Option D might not be the right choice.
upvoted 0 times
...
Dahlia
4 months ago
I’m a bit confused about TLS versions; I know TLS 1.0 is outdated, but I’m not sure if that’s the main issue here.
upvoted 0 times
...
Werner
4 months ago
I think I saw a similar question where firewall settings were the issue, so option B could be a possibility too.
upvoted 0 times
...
Talia
4 months ago
I remember something about certificates needing to match the FQDN, so option A seems likely, but I'm not completely sure.
upvoted 0 times
...
Janine
4 months ago
Ah, I see. If the users don't have the right licenses, that could definitely cause issues with the Direct Routing setup. I'll make sure to verify that.
upvoted 0 times
...
Virgina
4 months ago
I think the key here is to methodically go through each option and eliminate the ones that don't seem to fit the problem description. That should help me narrow it down.
upvoted 0 times
...
Alecia
5 months ago
Wait, I'm a bit confused. Could it also be an issue with the firewall or TLS settings on the SBC? I'll need to double-check those as well.
upvoted 0 times
...
Milly
5 months ago
Okay, let's see here. The warning is about the certificate not matching the FQDN, so that's the first thing I'd check.
upvoted 0 times
...
Wai
5 months ago
Hmm, this looks like a tricky one. I'll need to carefully review the details and think through the possible causes.
upvoted 0 times
...
Raylene
5 months ago
I agree with Ashton, that seems like a likely reason for the issue.
upvoted 0 times
...
Ashton
5 months ago
I think the possible cause could be the firewall blocking outbound traffic on port 443 to Microsoft Teams.
upvoted 0 times
...
Harley
6 months ago
TLS 1.2 being enabled on the SBC? That's a wild guess, but hey, maybe the IT team is really into cyber security.
upvoted 0 times
...
Maurine
6 months ago
The firewall blocking traffic to the signaling port on the SBC seems like the most likely culprit here. I bet the network admin forgot to open that port.
upvoted 0 times
Julian
2 months ago
Sounds like a classic network issue!
upvoted 0 times
...
Rochell
2 months ago
Have you checked the firewall rules?
upvoted 0 times
...
Maybelle
2 months ago
Yeah, that’s a common oversight.
upvoted 0 times
...
Ben
2 months ago
I agree, the signaling port could definitely be blocked.
upvoted 0 times
...
...

Save Cancel