Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft Exam MS-721 Topic 3 Question 40 Discussion

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

You have a Microsoft Teams Phone deployment.

You are deploying Direct Routing by using a certified Session Border Controller (SBC). The FQDN of the S6C is sbcVcontoso.com. You use signaling port 5067.

You cannot place calls and receive an error message m the Microsoft Teams admin center as shown in the following exhibit.

What is a possible cause of the issue?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Yoko
1 months ago
Haha, I bet the IT admin who set this up forgot to renew the SBC certificate. Classic mistake, right?
upvoted 0 times
Laurena
1 days ago
C) The Forward P-Asserted Identify (PA!) header is disabled.
upvoted 0 times
...
Tran
7 days ago
B) The Baltimore root certificate is missing on the SBC.
upvoted 0 times
...
Altha
15 days ago
A) Location-Based Routing is enabled for the SBC
upvoted 0 times
...
...
Kristofer
1 months ago
Hmm, I'm not sure about this one. Maybe it's Option D and the failover timer is set too low, causing the calls to drop before they can connect properly.
upvoted 0 times
Krystal
9 days ago
D) The failover timer is set to 0 seconds
upvoted 0 times
...
Dylan
18 days ago
C) The Forward P-Asserted Identify (PA!) header is disabled.
upvoted 0 times
...
Frederic
19 days ago
B) The Baltimore root certificate is missing on the SBC.
upvoted 0 times
...
Elina
22 days ago
A) Location-Based Routing is enabled for the SBC
upvoted 0 times
...
...
Tamera
2 months ago
I'm going with Option C. The Forward P-Asserted Identity (PAI) header is crucial for Direct Routing, so if it's disabled, that could definitely cause call failures.
upvoted 0 times
Freida
13 days ago
I think we should check if the Forward P-Asserted Identity (PAI) header is disabled on the SBC. That could be causing the issue.
upvoted 0 times
...
Lajuana
21 days ago
I agree, Option C seems like the most likely cause. Without the Forward P-Asserted Identity (PAI) header, calls won't work properly.
upvoted 0 times
...
...
Jerry
2 months ago
But could it also be because the Baltimore root certificate is missing on the SBC?
upvoted 0 times
...
Jeniffer
2 months ago
Option B seems the most likely culprit. If the Baltimore root certificate is missing, the SBC won't be able to establish a secure connection with Teams, leading to this issue.
upvoted 0 times
...
Lavera
2 months ago
I agree with Tandra, the error message seems to indicate a problem with the PAI header.
upvoted 0 times
...
Tandra
2 months ago
I think the issue might be with the Forward P-Asserted Identity header.
upvoted 0 times
...

Save Cancel