MS-700 Manage Meetings and Calling Practice Question
You are a Teams administrator for a multinational company. The company uses Direct Routing for PSTN connectivity. A user reports that when they receive an incoming PSTN call, the call rings on their Teams client but when they answer, the call drops immediately. You have verified that the user's voice configuration is correct and that the Session Border Controller (SBC) is reachable. You need to troubleshoot the issue. Which tool should you use to capture and analyze the SIP traffic for this call?
⚠ Common exam trap
The trap here is assuming that Call Analytics or client logs provide sufficient SIP detail, when in fact SBC-level tracing is required to see the full SIP dialog.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Session Border Controller (SBC) logs and SIP tracing
For Direct Routing call drops, SIP signaling issues are common. Capturing and analyzing SIP traffic on the SBC provides the detailed SIP messages exchanged with Teams, revealing errors like 488 Not Acceptable Here or 603 Decline. SBC logs and SIP tracing are essential for this level of troubleshooting, whereas other tools offer only high-level or client-side data.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Teams client debug logs
Why it's wrong here
Teams client debug logs capture client-side activity, including media and signaling, but they do not provide the full SIP trace from the SBC perspective. While they can be useful, they are less comprehensive for Direct Routing issues. The SBC logs are more authoritative for SIP-level troubleshooting.
- ✓
Session Border Controller (SBC) logs and SIP tracing
Why this is correct
SBC logs and SIP tracing capture the SIP signaling between the SBC and Teams. Since the call rings but drops upon answer, the issue likely lies in SIP signaling (e.g., media negotiation, codec mismatch, or SDP issues). Analyzing SBC logs and SIP traces will reveal the exact SIP messages and error codes causing the drop.
- ✗
Microsoft 365 network connectivity test tool
Why it's wrong here
The Microsoft 365 network connectivity test tool assesses network readiness and connectivity to Microsoft 365 services. It does not capture SIP traffic or provide call-specific signaling details. It is useful for general network diagnostics but not for troubleshooting individual call drops.
- ✗
Microsoft Teams admin center Call Analytics
Why it's wrong here
Call Analytics provides detailed information about calls, including quality and signaling, but it does not capture raw SIP traffic. It shows media and signaling metrics but is not a packet capture tool. For deep SIP troubleshooting, you need to capture the actual SIP messages exchanged between Teams and the SBC.
About these practice questions
One of 211 original MS-700 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
This MS-700 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the MS-700 exam.