What log level is required to troubleshoot call setup issues?

• A. Info
• B. Warning
• C. Error
• D. Debug

Answer: (D)

When diagnosing call setup problems, you need the most detailed trace of what the system is doing step by step. That level of detail comes from enabling debug logs. Debug logs capture every signaling event, timer transitions, and internal decision points during call setup, including the exact messages exchanged (such as SIP INVITE, 100/Trying, 180 Ringing, 200 OK, ACK) and the associated media negotiation details. This granular view lets you see exactly where the flow breaks or deviates from the expected path, whether a call stalls during routing, authentication, or SDP negotiation, or a message never leaves the device.

Other log levels provide less detail. Info gives a high-level view of events, which can miss the precise sequence leading to the problem. Warning highlights potential issues but not the full cause, and Error shows only failures after they occur, which often isn’t enough to pinpoint where the setup started to fail. For effective troubleshooting, the verbose, step-by-step insight from debug logs is essential. Remember to collect only what you need and disable after you’ve captured the necessary data due to the heavy volume generated.