CUCM 9.x with Gateway - Troubleshoot call leg

[philippe.cousineau]

Guys,

We have a CUCM 9.x at a main site (Site-A),  with a h.323 Gateway.

The h.323 Gateway have a Sip Dial-peer with another cisco pbx in another Country (Site-B).

In the past, people at Site-B used to called 816XXX to reach Site-B devices, and People in site-A can dial 83XXXX to reach people at site-B.

I know that some change occured in the last two weeks, since that it longer work for inter-site call.

I know that the IOS of Site-A has been updated to a 15.1   ( BUT we did add the IP address truested command to trust all PBX )

But still it's not working..

I did a debug voip dialpeer,  and I would like to have your opinion

When user from Site B dial : 816999

It’s going well to our router at Bellevue, as expected

040331: 5d10h: //-1/856FEA4E80C4/DPM/dpAssociateIncomingPeerCore:

   Calling Number=83644, Called Number=6999, Voice-Interface=0x0,

I see there is a successful match with dial-peer 6999

040341: 5d10h: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:

   Result=SUCCESS(0)

   List of Matched Outgoing Dial-peer(s):

     1: Dial-peer Tag=6999

This dial-peer 6999 point to Call Manager

dial-peer voice 6999 voip

description Outgoing to CUCM

destination-pattern 6...

session target ipv4:10.AA.XZ.ZZ

dtmf-relay h245-alphanumeric

And one have a recommendation ?

[Jaime Valencia]

Debug the calls and check the whole config, I've seen many cases in which more than one person had access to CUCM/GW, and changed something without telling anyone else.

[philippe.cousineau]

For that specific scenario, Do you recommend any other command to debug than

debug voip dial-peer

ps : The Inbound CSS of the Gateway On Call Manager side reach the Partition extension in the actual scenario

[Jaime Valencia]

Yes, debug DP doesn't give anything beyond the fact you're matching a DP or not.

debug voip ccapi inout

[Ayodeji Okanlawon]

You will need to see in depth into the h225 and h245 signalling as well ass the CCAPI process..

You should do this

debug voip ccapi inout

debug h225 asn1

debug h245 asn1

To capture all of these logs..you need to properly setup your gateway as follows

service sequence-numbers
service timestamps debug datetime localtime msec
logging buffered 10000000 debug
no logging console
no logging monitor
default logging rate-limit
default logging queue-limit

Then..

<Enable debugs, then test again.>

<Enable session capture to txt file in terminal program.> (such as Putty)

then do the ff:

terminal length 0
show logging

You can attach the logs here in a text file