Source note · CUBE troubleshooting commands

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.

Checked 2026-09-25

It is not possible to trace calls with a single SIP leg using the trace command.

Vendor: Cisco
Product: CUBE
Subsystem: VoIP Trace
Deployment: on-premises
Region: not restricted
Release range: IOS XE 17.3.2 and later
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 · Restrictions for VoIP Trace

Cite this note

APA

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

BibTeX

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

Read in context