Configure Debug Collection for CUBE and TDM Gateways

Publisher

Cisco Systems

URL

https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-border-element/215208-configure-debug-collection-for-unified-b.html

Published

2026-08-17

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

• Cisco's CUBE debug baseline uses a 10 MB logging buffer and disables console and monitor logging, which it warns can harm router performance and debug accuracy. in context
• For SIP calls through CUBE, Cisco recommends debug ccsip messages and debug ccsip error together with debug voip ccapi inout, which usually has minimal CPU impact and adds call state information. in context
• Cisco's baseline for CUBE debug collection sets debug and log timestamps to datetime with msec, localtime, show-timezone and year, and enables service sequence-numbers. in context
• Cisco's basic debug set for SIP calls on CUBE is debug ccsip messages and debug ccsip error, with debug ccsip non-call optional, and debug voip ccapi inout recommended alongside because it usually has minimal CPU impact. in context
• Before debugging, Cisco recommends logging to a 10 MB buffer (logging buffered 10000000), disabling console and monitor logging, and millisecond timestamps; debugs should be stopped (undebug all) if CPU exceeds 80%. in context
• Cisco lists 'debug ccsip all' and 'debug ccsip verbose' as advanced SIP debugs and says to watch the CPU closely while advanced debugs are running. in context
• Cisco's basic SIP debug set for CUBE is 'debug ccsip messages', 'debug ccsip error', 'debug ccsip non-call' and 'debug voip ccapi inout'. in context
• Cisco says most CUBE debug scenarios need a log buffer of at least 10 MB so that enough output is collected before it is overwritten. in context
• Cisco says 'debug voip ccapi inout' usually has minimal CPU impact and recommends enabling it alongside any signaling debugs. in context
• Cisco puts no number on the CPU cost of 'debug ccsip messages'. Its guidance is qualitative and scaled by current CPU: it treats ccsip messages as a basic debug, allowed at about 50% CPU, while all debugs must stop above about 80%. The practical cost therefore depends on call rate and has to be judged from 'show process cpu' on the box. inferred in context
• Cisco's collection procedure runs 'clear log' to empty the buffer before the issue is reproduced. in context
• To collect output, Cisco uses 'terminal length 0' followed by 'show log', or sends the output off the box with 'show log | redirect' to an FTP URL. in context
• Before enabling debugs, Cisco says to run 'show process cpu sorted | exclude 0.00' to check the 5-second, 1-minute and 5-minute CPU values and the top processes. in context
• Cisco's CPU guidance for CUBE debugs: at about 30% CPU or less, basic through advanced debugs can be enabled; at about 50%, use basic debugs only and keep monitoring; above 80%, stop debugs immediately and engage support. in context
• Cisco's CUBE debug-collection baseline sets 'logging buffered 10000000', a 10 MB local log buffer, and notes that the size can be adjusted. in context
• The CUBE debug baseline turns off console and monitor logging ('no logging console', 'no logging monitor') so that debug output does not degrade router performance. in context
• The CUBE debug baseline includes 'logging queue-limit 10000' and 'logging rate-limit 10000'. in context
• Cisco warns that syslog servers tend to skip or drop lines of debug output when the server is congested, even though the tech note gives a 'logging host' configuration. in context
• For digital PRI and BRI call flows on the same gateways, the tech note lists 'debug isdn q931' and 'debug isdn q921'. in context
• The CUBE debug baseline sets 'service timestamps debug' and 'service timestamps log' to 'datetime msec localtime show-timezone year' and turns on 'service sequence-numbers'. in context
• Cisco turns debugs off with 'undebug all' once output has been collected. in context
• The 'voice iec syslog' command turns on Voice Internal Error Code (IEC) messages, which help identify why a call disconnected. in context
• The two Cisco documents do not contradict each other on VoIP Trace's first release. The configuration guide lists only the 17.3.2 train, while the tech note also names 17.4.1. The safest reading is that 17.3.2 or later on the 17.3 train, and 17.4.1 or later, include the feature. inferred in context
• Tech note 215208 says VoIP Trace arrived with Cisco IOS XE 17.4.1 and 17.3.2. in context
• Cisco lists debug ccsip messages, debug ccsip error and debug ccsip non-call as the basic SIP debugs to collect on CUBE, with debug ccsip all, debug ccsip verbose and debug voip ccapi inout as advanced debugs. in context
• Cisco advises stopping debugs immediately and engaging TAC if router CPU goes above 80 percent during CUBE debug collection. in context
• Cisco's baseline for CUBE debug collection sets millisecond debug timestamps, service sequence-numbers, a 10 MB logging buffer (logging buffered 10000000) and disables console and monitor logging. in context

Cite this source record

APA

WarmTransfer. (2026, August 17). Configure Debug Collection for CUBE and TDM Gateways. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-technote-215208-cube-debug-collection

BibTeX

@misc{warmtransfer-cisco-technote-215208-cube-debug-collection,
  title  = {Configure Debug Collection for CUBE and TDM Gateways},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-technote-215208-cube-debug-collection},
  note   = {Cisco Systems, accessed 2026-09-23}
}