Source note · CUBE troubleshooting commands

On IOS XE 17.3.2 or later with VoIP Trace left on, a failed SIP-trunk-to-SIP-trunk call can often be reviewed after the fact with 'show voip trace' without enabling debugs, provided the trace has not been overwritten. Out-of-scope calls, single-leg calls and any SIP methods VoIP Trace does not capture still need the buffered-debug procedure.

inferred · Checked 2026-09-25

Vendor: Cisco
Product: CUBE
Subsystem: call-flow trace collection
Deployment: on-premises
Region: not restricted
Release range: IOS XE 17.3.2 and later
Status: inferred
Checked: 2026-09-25

Sources

Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: VoIP Trace — Cisco Systems · tier 2 current vendor documentation · Overview, Restrictions, and memory behaviour sections

Cite this note

APA

WarmTransfer. (2026, September 25). CUBE troubleshooting commands: source note cube-troubleshooting-toolkit-trace-vs-debug-order. WarmTransfer. https://warmtransfer.net/knowledge/claims/cube-troubleshooting-toolkit-trace-vs-debug-order

BibTeX

@misc{warmtransfer-claim-cube-troubleshooting-toolkit-trace-vs-debug-order,
  title  = {CUBE troubleshooting commands: source note cube-troubleshooting-toolkit-trace-vs-debug-order},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/claims/cube-troubleshooting-toolkit-trace-vs-debug-order},
  note   = {Source note cube-troubleshooting-toolkit-trace-vs-debug-order, checked 2026-09-25}
}

Read in context