debug CME question

goranpilat · ‎09-04-2009

Hi all,

When I do the debugging on CME (debug voice ccapi inout, debug h225 Q931), I see the debugging , but don't know how to easily see who sends which message (for example is the disconnect initiated by the CME or by the TSP)

in particular :

Data 0528501900060008914A000400022E7F815D60361326095634343434EF10A00100140140B50000120D80A2000943004C050000333839

Q931 Message IE Decodes

Protocol Discriminator : 0x08

CRV Length : 2

CRV Value : 0x751F

Message Type : 0x5A: RELEASE_COMP

Cause: Length Of IE=2

Data 8083

User-User: Length Of IE=29

Data 050580060008914A0004011100022E7F815B98281725505634343434EF

Q931 Message IE Decodes

Protocol Discriminator : 0x08

CRV Length : 2

CRV Value : 0xF51F

Message Type : 0x5A: RELEASE_COMP

Cause: Length Of IE=2

Data 8083

User-User: Length Of IE=34

Data 052580060008914A000411001100022E7F815B98281725505634343434EF10800100

Q931 Message IE Decodes

Protocol Discriminator : 0x08

CRV Length : 2

CRV Value : 0x7EDB

Message Type : 0x5A: RELEASE_COMP

Cause: Length Of IE=2

Data 8083

User-User: Length Of IE=29

Data 050580060008914A0004011100022E7F815D60361326095634343434EF

Q931 Message IE Decodes

Protocol Discriminator : 0x08

CRV Length : 2

CRV Value : 0xFEDB

Message Type : 0x5A: RELEASE_COMP

Cause: Length Of IE=2

Data 8083

User-User: Length Of IE=34

Data 052580060008914A000411001100022E7F815D60361326095634343434EF10800100

or

*Sep 4 10:56:34.392: vsacount in free is 2

*Sep 4 10:56:38.256: //13692/4EE0E727B56A/CCAPI/cc_api_call_disconnected:

Cause Value=3, Interface=0x46DCEED0, Call Id=13692

*Sep 4 10:56:38.260: //13692/4EE0E727B56A/CCAPI/cc_api_call_disconnected:

Call Entry(Responsed=TRUE, Cause Value=3, Retry Count=0)

*Sep 4 10:56:38.260: //13692/4EE0E727B56A/CCAPI/ccConferenceDestroy:

Conference Id=0x111B, Tag=0x0

*Sep 4 10:56:38.260: //13692/xxxxxxxxxxxx/CCAPI/cc_api_bridge_drop_done:

Conference Id=0x111B, Source Interface=0x46DCEED0, Source Call Id=13692,

Destination Call Id=13693, Disposition=0x0, Tag=0x0

*Sep 4 10:56:38.260: //13693/xxxxxxxxxxxx/CCAPI/cc_api_bridge_drop_done:

Conference Id=0x111B, Source Interface=0x477FCEB4, Source Call Id=13693,

Destination Call Id=13692, Disposition=0x0, Tag=0x0

*Sep 4 10:56:38.260: //13692/4EE0E727B56A/CCAPI/cc_generic_bridge_done:

Conference Id=0x111B, Source Interface=0x477FCEB4, Source Call Id=13693,

Any suggestions are most welcomed

Best regards

Goran Pilat

Nicholas Matthews · ‎09-08-2009

Hi Goran,

These debugs do not tell you the direction.

What will is: debug h225 asn1

I think it's fairly likely that it is your CME disconnecting because cause value 3 is 'No Route to Destination'. Basically the number you're receiving doesn't match an ephone or dial peer.

I would check 'debug voip ccapi inout' again the dest= in the debugs. Then use a 'show dial-peer voice summary' to see what your system is showing the dial peers as. Check for any translation problems on the incoming and outgoing dial peer.

-nick

goranpilat · ‎09-08-2009

Hello Nick,

Thanx for the reply. However, the problem is solved and the TSP took responsibility. The above traces happened sporadically, in the middle of conversation, sometimes didn't happen and so on... ghostbusters stuff...

The problem was in their core and now everything seems to be ok.

Thanks for the "debug h225 asn1", anyway.

Best regards

Goran Pilat