MENU
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?
Suggested Answer: B
Get Premium MS-721 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
34 comments · newest first
SU
Sue
10 months ago
Nah, I’m leaning towards A. Location-Based Routing can mess things up.
LI
Lizette
10 months ago
Wait, could it really be that simple? What about option C?
CH
Chana
10 months ago
Definitely agree with B. That’s a common problem!
SA
Santos
11 months ago
I think option B is the issue. Missing certificates can cause call failures.
FR
France
11 months ago
D seems unlikely, who sets a failover timer to 0 seconds?
DE
Delsie
11 months ago
Setting the failover timer to 0 seconds seems odd, but I don't remember if that would prevent calls from going through. It could be a possibility.
JE
Jess
11 months ago
The P-Asserted Identity header sounds familiar, but I can't recall if it directly affects call placement. I might need to double-check that.
CH
Cherry
12 months ago
I think the Baltimore root certificate is crucial for the SBC to function properly. I recall a practice question that mentioned certificates causing issues.
VE
Velda
12 months ago
I remember something about Location-Based Routing, but I'm not entirely sure if it applies here. It seems like it could be a factor.
AU
Augustine
12 months ago
Hmm, my first instinct is that the issue could be related to the Forward P-Asserted Identity (PAI) header. I'll review the SBC settings and make sure that's configured correctly. Might also check the failover timer just to be thorough.
RA
Rasheeda
1 year ago
I'm a bit confused by all the technical details here. I'll need to take some time to really understand the setup and the error message before I can make a confident guess about the cause. Gotta be careful with these tricky networking questions.
CR
Cristal
1 year ago
Alright, this seems straightforward. The error message is pretty clear - it's probably an issue with the certificate on the SBC. I'll focus on checking the Baltimore root certificate and making sure it's installed properly.
RO
Rolande
1 year ago
Okay, let's see here. The error message mentions something about the SBC, so I'm guessing the issue is related to the SBC setup. I'll need to double-check the FQDN, port, and any other SBC settings to see if they're configured correctly.
JO
Joni
1 year ago
Hmm, this looks like a tricky one. I'll need to carefully review the details about the SBC configuration and the error message to figure out the most likely cause.
YO
Yoko
1 year ago
Haha, I bet the IT admin who set this up forgot to renew the SBC certificate. Classic mistake, right?
LA
Laurena
1 year ago
C) The Forward P-Asserted Identify (PA!) header is disabled.
TR
Tran
1 year ago
B) The Baltimore root certificate is missing on the SBC.
AL
Altha
1 year ago
A) Location-Based Routing is enabled for the SBC
KR
Kristofer
2 years 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.
TA
Tayna
1 year ago
Agreed, let's look into that and see if adjusting the failover timer resolves the issue.
YV
Yvonne
1 year ago
We should check the settings and make sure the failover timer is properly configured.
VI
Viola
1 year ago
Yeah, I think so too. The failover timer being set to 0 seconds could definitely cause problems with call connections.
OZ
Ozell
1 year ago
Maybe you're right, Option D does seem like a possible cause for the issue.
KR
Krystal
1 year ago
D) The failover timer is set to 0 seconds
DY
Dylan
1 year ago
C) The Forward P-Asserted Identify (PA!) header is disabled.
FR
Frederic
1 year ago
B) The Baltimore root certificate is missing on the SBC.
EL
Elina
1 year ago
A) Location-Based Routing is enabled for the SBC
TA
Tamera
2 years 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.
FR
Freida
1 year 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.
LA
Lajuana
1 year ago
I agree, Option C seems like the most likely cause. Without the Forward P-Asserted Identity (PAI) header, calls won't work properly.
JE
Jerry
2 years ago
But could it also be because the Baltimore root certificate is missing on the SBC?
JE
Jeniffer
2 years 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.
LA
Lavera
2 years ago
I agree with Tandra, the error message seems to indicate a problem with the PAI header.
TA
Tandra
2 years ago
I think the issue might be with the Forward P-Asserted Identity header.