Which tool would you use to verify SIP trunk status on CUCM?

Prepare for the Cisco CLCOR 350-801 exam with detailed flashcards and multiple choice questions. Understand core technologies, and explore hints and explanations for a comprehensive learning experience. Equip yourself for success!

Multiple Choice

Which tool would you use to verify SIP trunk status on CUCM?

Explanation:
Verifying SIP trunk status hinges on inspecting the actual signaling between CUCM and the other endpoint. The Real-Time Monitoring Tool (RTMT) is the built-in diagnostic utility that lets you monitor CUCM services and view SIP signaling traces in real time. By connecting to CUCM with RTMT and capturing SIP traces for the trunk, you can examine the INVITE flow, responses (like 200 OK), and any error messages. This makes it possible to confirm that the trunk is registered, that signaling is being exchanged correctly, and that calls can be set up and torn down as expected. If traces show abnormal SIP messages or no signaling at all, you have a concrete basis for troubleshooting the trunk. Other options don’t give the same end-to-end visibility. Ping checks basic network reachability but does not verify SIP signaling or trunk health. Telnet can test port reachability but is insecure and doesn’t verify call signaling or registration. SNMP monitors device metrics, not the status of SIP trunk signaling or call flows.

Verifying SIP trunk status hinges on inspecting the actual signaling between CUCM and the other endpoint. The Real-Time Monitoring Tool (RTMT) is the built-in diagnostic utility that lets you monitor CUCM services and view SIP signaling traces in real time. By connecting to CUCM with RTMT and capturing SIP traces for the trunk, you can examine the INVITE flow, responses (like 200 OK), and any error messages. This makes it possible to confirm that the trunk is registered, that signaling is being exchanged correctly, and that calls can be set up and torn down as expected. If traces show abnormal SIP messages or no signaling at all, you have a concrete basis for troubleshooting the trunk.

Other options don’t give the same end-to-end visibility. Ping checks basic network reachability but does not verify SIP signaling or trunk health. Telnet can test port reachability but is insecure and doesn’t verify call signaling or registration. SNMP monitors device metrics, not the status of SIP trunk signaling or call flows.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy