Which of the following logs would you consult to troubleshoot SIP signaling and calls on gateways?

• A. SNMP traps
• B. SIP/call logs on gateways
• C. System health reports
• D. Network analytics

Answer: (B)

Logs that capture SIP signaling on gateways reveal the exact message flow, timing, and identifiers used during a call, which is essential for diagnosing where a problem occurs in setup, mid-call negotiation, or teardown. These gateway-level logs show the actual SIP messages exchanged—INVITE, TRYING, RINGING, 200 OK, ACK, CANCEL, BYE, and any reINVITEs or SDP negotiations—along with call-id, dialog state, and timestamps. By tracing this sequence, you can pinpoint where the flow breaks: a missed INVITE, a misrouted response, a SIP error response, or a media negotiation issue, and you can correlate events to a specific call using the call identifiers. In short, you get the most direct, actionable view of how SIP signaling and calls are processed by the gateway.

SNMP traps focus on device status (CPU, memory, interfaces), which helps with overall health but not the detailed signaling flow. System health reports provide general health metrics but lack the step-by-step SIP message details. Network analytics show traffic patterns and QoS trends but do not reveal the actual SIP signaling sequence.