CUBE showing SIP messages on SSH line even though all debugs are off

[JamesHawkins]

Hi,

I have a CUBE running IOS-XE 17.6.3a on an ISR4331.

When I SSH to the router and enter term mon I see debug information about SIP calls transiting the router even though all debugging is off.

Has anyone else seen this and, if so, do you know how to turn it off?

I need to run other debugs without this cluttering them up.

Thanks!

[Jens Albrecht · Accepted solution]

Hello @JamesHawkins,

starting with IOS XE 17.4.1, 17.3.2, VOIP Trace logging is enabled by default for SIP activity on CUBE routers to facilitate troubleshooting and compliance with Cisco Webex and other cloud-connected solutions.

This feature outputs SIP message and call-processing information directly to the terminal session or syslog, regardless of whether debug commands are enabled or disabled.

This VOIP Trace feature can be turned off with the following commands:

conf t
voice service voip
 no trace
exit

This setting does not affect normal debug commands like 'debug ccsip messages' which will continue to work as before.

If you want to re-enable the VOIP Trace feature later for troubleshooting, simply use 'trace' command under 'voice service voip'.

For more details refer to the 'Introducing Always on debugging with VOIP Trace' section on page 47 of the CiscoLive presentation:
https://www.ciscolive.com/c/dam/r/ciscolive/global-event/docs/2022/pdf/BRKCOL-2169.pdf

HTH!

[Jonathan Schulenberg · Accepted solution]

VoIP Trace only outputs to the logging buffer if there is a problem, i.e. something you should troubleshoot:

VoIP Trace monitors and logs SIP signalling and call events in memory as they occur. In the event that a call error is detected, or calls fail with 3xx, 4xx or 5xx cause codes, these event details are written to the logging buffer after the call clears.

The correct syntax to disable the feature is voice service voip > trace > shutdown. Try it to confirm that's the origin of the output but don't leave it disabled; it's an incredibly useful feature.

[JamesHawkins]

Thanks both. When I looked at the messages I could see the CUBE receiving an Invite and then responding with a 422 Session Timer too small response.

The Min-SE on the CUBE was set to 1800 and in the Invite it was set to 450.
I have changed the Min-SE under voice service voip > sip to 450 and the messages have disappeared.
I was not aware that error messages were handled like that and can see the reason why that is so.
Thanks again for your responses

[Alexis Amaro]

Disable trace in voice service voip:

conf t

voice service voip

no trace

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