CUBE - debug for SIP Registration Traffic

[TONY SMITH]

Hi,

I've found that some CUBE instances don't show SIP registration messages and replies when you enable the normal "debug ccsip mess".   It doesn't seem to be platform specific, for example I have seen 29xx routers where it appears and other where it doesn't.  Is there some other specific debug that would show this, or some setting that controls whether or not these messages are included in the normal debugs?

Thanks, Tony S

[TONY SMITH · Accepted solution]

OK might have found this.   "debug ccsip non-call",  it seems this debug is available on some platforms/versions but not others, hopefully that corresponds to the platforms/versions that don't show these messages in the normal debugs.

[David Chachanidze]

Hello, Tony

Does your CUBE have any VoIP Dial-peers configured?
As I remember, CUBE MUST have at least one VoIP dial-peer (with session protocol SIP configured), so that "Debug ccsip messages" will start to output SIP Register messages. 

[TONY SMITH]

Thanks David.  Yes the CUBE configuration is more or less complete, complete subject to snagging.   In its initial state "debug ccsip messages" showed messages between CUCM and CUBE, and attempted messages between CUBE and ITSP, but not the registration attempts or replies.

The additional "debug ccsip non-call" is the solution (in this case at least).

From what I recall if there's not at least one dial peer with sipv2 protocol there are some lower level error messages for example "Process CCSIP_SPI_CONTROL not UP yet" but I can't remember exactly what debug is needed to display those.  However if you have a gateway that's so goosed it's not sending any SIP messages you could probably use "debug ccsip all" in the first instance.