Which command verifies SIP trunk status on a CUBE device?

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 command verifies SIP trunk status on a CUBE device?

Explanation:
The key idea is that the health of a SIP trunk on a CUBE is reflected in the status of the SIP User Agent (SIP-UA) that the CUBE uses to handle SIP signaling. The command show sip-ua status provides a snapshot of this signaling layer: it shows whether the SIP UA is up, which transport methods (UDP/TCP/TLS) are being used, listening ports, and the peer relationships the CUBE has established for SIP signaling. This directly indicates whether the trunk’s signaling path is operational and reachable to the service provider. If the SIP-UA interface or its transports aren’t up, you’ll see indications in that output that the trunk isn’t healthy or reachable, which is exactly what you want to verify when checking a SIP trunk. The other options don’t serve the same purpose. show sip-ua statistics offers signaling counters and error counts, which are useful for troubleshooting throughput or error patterns but don’t immediately confirm the live trunk status. The option about verifying SIP trunk status via RTMT is something you’d use with Cisco Unified Communications Manager (CUCM), not on the CUBE device itself. And show sip-trunk status isn’t the correct command for CUBE to view trunk health.

The key idea is that the health of a SIP trunk on a CUBE is reflected in the status of the SIP User Agent (SIP-UA) that the CUBE uses to handle SIP signaling. The command show sip-ua status provides a snapshot of this signaling layer: it shows whether the SIP UA is up, which transport methods (UDP/TCP/TLS) are being used, listening ports, and the peer relationships the CUBE has established for SIP signaling. This directly indicates whether the trunk’s signaling path is operational and reachable to the service provider.

If the SIP-UA interface or its transports aren’t up, you’ll see indications in that output that the trunk isn’t healthy or reachable, which is exactly what you want to verify when checking a SIP trunk.

The other options don’t serve the same purpose. show sip-ua statistics offers signaling counters and error counts, which are useful for troubleshooting throughput or error patterns but don’t immediately confirm the live trunk status. The option about verifying SIP trunk status via RTMT is something you’d use with Cisco Unified Communications Manager (CUCM), not on the CUBE device itself. And show sip-trunk status isn’t the correct command for CUBE to view trunk health.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy