Unable to make outbound calls via h323 gateway using SCCP phone but works using SIP phone

[Deepak Mehta]

Hi All,

I am using a remote LAB set up from one of  cisco training providers.

I have two phones at HQ site one is 9971 and other is 7962 phone.

I have R1 router on Hq site which i am using to make outbound calls to PSTN phone .I have set up this as h323 gateway .All inbound calls are working fine. I can also successfully make outbound calls using SIP phone to the PSTN phone and it is negoiating g729 codec.( Region is same for both gateway and Hq-phone which set to negotiate  g7111 codec ).My first question is why is it negotiating g729?

When i use SCCP 7962 phone outbound call doesn't even work and there is nothing in the q931 debug .

What could be the reason for this.

I would appreciate any guidance on this.

Thank you

Deepak Mehta

[Jaime Valencia]

Did you configure a codec in H323?? If not, g729 is the default

if you don't see the calls hit the GW, it's not making it out of CUCM, check all the basics.

[Deepak Mehta]

Thank you Jaime.

i didn't configure the codec on the h323 ,so I believe you answered the first one.

For second one both Sccp and sip phone is using exact same pattern and also same css.only difference is the protocol and model of phones.

one is 7962 and other is 9971.cucm does show call routing when I do a DNA test for both.

i will try again.

[Vivek Batra]

You should see h.323/voice ccapi logs in gateway and verify whether call is hitting gateway or not, so that you can conclude to start troubleshooting in CUCM or gateway.

- Vivek

[Deepak Mehta]

First thing , i can see the call is routing for both SCCP and SIP phones from CUCM .( As per DNA same pattern is being matched )..

Both phones are matching the dial-peer 100 and 200 .SIP phone is still working fine .

For SCCP 7962 i still unable to establish a call and below debug cch323 h225.

I do not get anything for q931 debug for sccp phone.

callingNumber[2001] calledNumber[95032000]

Apr  9 07:52:06.787: //4/800ECEA10400/H323/setup_ind: ---- calling IE present

Apr  9 07:52:06.787: //4/800ECEA10400/H323/setup_ind: ====== PI = 0

Apr  9 07:52:06.787: //4/800ECEA10400/H323/setup_ind: Receive: infoXCap 0

Apr  9 07:52:06.787: //4/800ECEA10400/H323/setup_ind: Receive: infoXCap ccb 0

Apr  9 07:52:06.787: //4/800ECEA10400/H323/setup_ind: 

setup_ind: is_overlap = 0, info_complete = 0

Apr  9 07:52:06.787: //4/800ECEA10400/H323/setup_ind: Call Manager detected

Apr  9 07:52:06.787: //4/800ECEA10400/H323/cch323_h225_receiver: SETUPIND_CHOSEN: src address = 11.11.11.1; dest address = 11.100.64.11

Apr  9 07:52:06.787: //4/800ECEA10400/H323/run_h225_sm: Received event H225_EV_SETUP_IND while at state H225_IDLE

Apr  9 07:52:06.787: //-1/800ECEA10400/DPM/dpAssociateIncomingPeerCore:

   Calling Number=2001, Called Number=95032000, Voice-Interface=0x0,

   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,

   Peer Info Type=DIALPEER_INFO_SPEECH

Apr  9 07:52:06.787: //-1/800ECEA10400/DPM/dpAssociateIncomingPeerCore:

   Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=100

Apr  9 07:52:06.787: //-1/800ECEA10400/DPM/dpMatchSafModulePlugin:

   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0

Apr  9 07:52:06.787: //4/800ECEA10400/H323/common_idle_setupInd_hdlr: full match is found

Apr  9 07:52:06.787: //4/800ECEA10400/H323/cch323_h225_set_new_state: Changing from H225_IDLE state to H225_SETUP state

Apr  9 07:52:06.787: //-1/800ECEA10400/DPM/dpAssociateIncomingPeerCore:

   Calling Number=2001, Called Number=95032000, Voice-Interface=0x0,

   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,

   Peer Info Type=DIALPEER_INFO_SPEECH

Apr  9 07:52:06.787: //-1/800ECEA10400/DPM/dpAssociateIncomingPeerCore:

   Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=100

Apr  9 07:52:06.787: //-1/800ECEA10400/DPM/dpMatchSafModulePlugin:

   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0

Apr  9 07:52:06.787: //4/800ECEA10400/H323/cch323_create_incoming_callinfo_block: peer 3AB9F754, voice_peer_tag 100, ccb: 39F8BD90

Apr  9 07:52:06.787: //4/800ECEA10400/H323/cch323_create_incoming_callinfo_block: Calling Party is CCM

Apr  9 07:52:06.787: //4/800ECEA10400/H323/cch323_h225_handle_deferred_ind: UnBuffering deferred indications

Apr  9 07:52:06.791: //4/800ECEA10400/H323/run_h225_sm: Received event H225_EV_RELEASE while at state H225_SETUP>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

R1#

Apr  9 07:52:06.791: //4/800ECEA10400/H323/cch323_h225_send_release: Cause = 21; Location = 0>>>>>>>>>>>>>>>>>>>>>>>>>>>

Apr  9 07:52:06.791: //4/800ECEA10400/H323/cch323_h225_send_release: h225TerminateRequest: src address = 185273089; dest address = 11.100.64.11

Apr  9 07:52:06.791: //4/800ECEA10400/H323/cch323_h225_set_new_state: Changing from H225_SETUP state to H225_IDLE state

===================

R1#sh run | s dial-peer voice

dial-peer voice 100 voip >>>>>>>>>

 incoming called-number .

 voice-class codec 1  

 voice-class h323 1

 dtmf-relay h245-alphanumeric

 no vad

dial-peer voice 200 pots >>>>>>>>>>>>>>

 destination-pattern 9T

 direct-inward-dial

 port 0/1/0:23

 forward-digits 7

dial-peer voice 101 voip

 destination-pattern 2...

 session target ipv4:11.100.64.12

dial-peer voice 202 pots

 translation-profile incoming hq

 incoming called-number .

[Jaime Valencia]

Then, as previously explained, you need to move over to CUCM to troubleshoot this.

[Deepak Mehta]

OK , i will look through the CCM traces but what do you think could be the possible reasons of this.

Can you give me few scenrerios which can lead to this .Thank you

[Ayodeji Okanlawon · Accepted solution]

Looking at the logs, the call is originating from a CUCM that is not the in the gateways trust list hence why you are getting cause code 21.

Please add a second dial-peer pointing to 11.100.64.11 or add this dial-peer to your trust  list

Apr  9 07:52:06.791: //4/800ECEA10400/H323/cch323_h225_send_release: Cause = 21; Location = 0>>>>>>>>>>>>>>>>>>>>>>>>>>>

Apr  9 07:52:06.791: //4/800ECEA10400/H323/cch323_h225_send_release: h225TerminateRequest: src address = 185273089; dest address = 11.100.64.11

Apr  9 07:52:06.791: //4/800ECEA10400/H323/cch323_h225_set_new_state: Changing from H225_SETUP state to H225_IDLE state

example below:

dial-peer voice 102 voip

pref 1

 destination-pattern 2...

 session target ipv4:11.100.64.11

dtmf-relay h245-alpha

no vad

[Deepak Mehta]

Thank you Ayodeji....let me try this.

[Deepak Mehta]

Deji-You have hit the bullseye with your expert analysis!!!!!The issue is fixed after adding CUCM to trust list.

I really thank you for guiding me here.

If you can look at below and let me know what do i need to fix this.

Can't make inbound call from SC PSTN-SB phone .Below output is taken from

SB MGCP gateway where call is coming in.

I have tried various options on MGCP gateway config in CUCM eg Display IE or redirecting IE support etc .Also on voice interface supplementary services command (isdn supp-service name calling ) is configured.

-------------------------------------------------------------------------------

pr 13 17:58:06.555: ISDN Se0/1/0:15 Q931: RX <- SETUP pd = 8  callref = 0x0080 

        Bearer Capability i = 0x8090A2 

                Standard = CCITT 

                Transfer Capability = Speech  

                Transfer Mode = Circuit 

                Transfer Rate = 64 kbit/s 

        Channel ID i = 0xA98381 

                Exclusive, Channel 1 

        Facility i = 0x9F8B0100A11802010302010080105369746543204C6F63616C205053544E 

                Protocol Profile =  Networking Extensions 

                0xA11802010302010080105369746543204C6F63616C205053544E 

                Component = Invoke component 

                        Invoke Id = 3 

                        Operation = CallingName 

                                Name Presentation Allowed Extended

                                Name = SiteC Local PSTN 

        Display i = 'SiteC Local PSTN' 

        Calling Party Number

R3# i = 0x4181, '70054000' 

                Plan:ISDN, Type:Subscriber(local) 

        Called Party Number i = 0xA1, '70044001' 

                Plan:ISDN, Type:National

Apr 13 17:58:06.559: ISDN Se0/1/0:15 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x8080 

        Cause i = 0x80E4 - Invalid information element contents>>>>>>>>>>>