Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: VoIP Trace

Publisher

Cisco Systems

URL

https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube/ios-xe/config/ios-xe-book/m_voip-trace-for-cube.html

Published

2026-04-25

Updated

unknown

Accessed

2026-09-23

HTTP status

200

License

Cisco documentation terms; no-redistribution; short excerpts and locators only

Source notes citing this source

• Starting with Cisco IOS XE Dublin 17.12.1a, VoIP Trace cover buffers show the call's cause code (Cover Buffer Enhancements for VoIP Trace). in context
• 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 in context
• VoIP Trace records SIP messages for SIP-trunk-to-SIP-trunk calls, CCSIP messages, events and APIs, SIP errors, call-control flows processed by CUBE, and FSM states and events. in context
• VoIP Trace on CUBE is enabled by default. It logs SIP signaling and call events without any debug being turned on. in context
• VoIP Trace logs traces for error calls at up to five traces per second. in context
• VoIP Trace keeps all call trace data in system memory. For calls with IEC errors, the data is also written to the logging buffer. in context
• Lowering the VoIP Trace memory-limit resets the existing VoIP Trace data. in context
• By default VoIP Trace uses up to 10% of available platform memory. The 'memory-limit' command under 'voice service voip' > 'trace' can set a custom value from 10 to 1000 MB instead. in context
• When VoIP Trace reaches its memory limit, older traces are overwritten. in context
• The CUBE configuration guide's feature table lists VoIP Trace as introduced in Cisco IOS XE Amsterdam 17.3.2. in context
• VoIP Trace cannot trace incoming calls once active calls have used up the memory limit, and it cannot trace calls that have only a single SIP leg. in context
• The 'show voip trace' command accepts call-id, session-id, sip-call-id, correlator, all, cover-buffers, statistics and detail. in context
• Running 'shutdown' in VoIP Trace configuration stops tracing for active calls and deletes all existing traces, so disabling VoIP Trace discards whatever it has captured. in context
• The 'show voip trace' output covers only the SIP leg of a call. For media forking, it also shows the forked legs. in context
• The VoIP Trace feature table lists Tenant-based Filtering for VoIP Trace at Cisco IOS XE Cupertino 17.8.1a. in context
• VoIP Trace on Cisco CUBE, introduced in IOS XE Amsterdam 17.3.2, logs SIP signalling and events without enabling debugs, and is on by default (it can be turned off with shutdown). in context
• CUBE VoIP Trace uses by default 10 percent of platform memory (configurable from 10 MB to 1000 MB) and overwrites older traces when the limit is reached. in context
• CUBE VoIP Trace captures SIP messages for SIP trunk-to-SIP trunk calls. in context
• CUBE VoIP Trace data is viewed with show voip trace, keyed by call-id, session-id, sip-call-id or correlator, among other options. in context

Cite this source record

APA

WarmTransfer. (2026, April 25). Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: VoIP Trace. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-cube-voip-trace-iosxe

BibTeX

@misc{warmtransfer-cisco-cube-voip-trace-iosxe,
  title  = {Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: VoIP Trace},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-cube-voip-trace-iosxe},
  note   = {Cisco Systems, accessed 2026-09-23}
}