CUCM 9.1.1 call failes over H.323

[Amit23]

hello,

i have cucm and h.323 gateway.

when calling from extension 423 it failed and play : call can not be completed.\

see the below H.323 gateway logs:

May 27 15:38:37: ISDN Se0/0/1:15 Q931: TX -> SETUP pd = 8  callref = 0x08D5

        Sending Complete

        Bearer Capability i = 0x8090A3

                Standard = CCITT

                Transfer Capability = Speech

                Transfer Mode = Circuit

                Transfer Rate = 64 kbit/s

        Channel ID i = 0xA9839F

                Exclusive, Channel 31

        Display i = 'Nesrine Harb Ext:426'

        Calling Party Number i = 0x0081, '426'

                Plan:Unknown, Type:Unknown

        Called Party Number i = 0x80, '66774169'

                Plan:Unknown, Type:Unknown

May 27 15:38:37: ISDN Se0/0/1:15 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x88D5

        Cause i = 0x829C00000000 - Invalid number format (incomplete number)

May 27 15:38:39: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x0, Calling num 607

May 27 15:38:39: ISDN Se0/0/0:15

!

one successful call logs also:

May 27 15:38:39: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8  callref = 0xC7AE

May 27 15:38:39: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x47AE

May 27 15:38:44: ISDN Se0/0/1:15 Q931: RX <- SETUP pd = 8  callref = 0x2D6D

        Sending Complete

        Bearer Capability i = 0x8090A3

                Standard = CCITT

                Transfer Capability = Speech

                Transfer Mode = Circuit

                Transfer Rate = 64 kbit/s

        Channel ID i = 0xA18394

                Preferred, Channel 20

        Calling Party Number i = 0x2181, '44940839'

                Plan:ISDN, Type:National

        Called Party Number i = 0xC1, '0000'

                Plan:ISDN, Type:Subscriber(local)

May 27 15:38:44: ISDN Se0/0/1:15 Q931: TX -> CALL_PROC pd = 8  callref = 0xAD6D

        Channel ID i = 0xA98394

                Exclusive, Channel 20

May 27 15:38:44: ISDN Se0/0/1:15 Q931: TX -> ALERTING pd = 8  callref = 0xAD6D

        Progress Ind i = 0x8088 - In-band info or appropriate now available

May 27 15:38:44: ISDN Se0/0/1:15 Q931: TX -> CONNECT pd = 8  callref = 0xAD6D

May 27 15:38:44: ISDN Se0/0/1:15 Q931: RX <- CONNECT_ACK pd = 8  callref = 0x2D6D

!

please help me how can fix it?

[Jaime Valencia]

Call your telco, find out what they expect for calling party, configure accordingly. I doubt they will accept any calls with just a 3 digit calling party.

[Amit23]

many thanks for reply Jaime!

but see in second call, it is showing full caller number:

Calling Party Number i = 0x2181, '44940839'

!

why showing different as we have same external mask for both phones?

[Jaime Valencia]

That's something you need to sort out by looking at your configuration, obviously something is not configured as required.

[Jitender Bhandari]

Hi,

Make a test call and collect CCM traces and below debugs from GW

Debug isdn q931

debug voip ccapi inout
debug h225 q931
debug h225 asn1
debug h245 asn1

provide calling and called party number.

HTH

Jitender Bhandari

[Brandon Pierce]

        Cause i = 0x829C00000000 - Invalid number format (incomplete number)

Is the dial plan any different for that extension?  The above error in the Q.931 output seems to think you should be sending differently.  Your telco is basically expecting you to send something you currently are not.

[Amit23]

Bze it is showing calling party 3 digit and it should be 8 digit like in below working call..

but as i have same mask on both phones, why one showing three digit and other is ok?

[Brandon Pierce]

Are both phones in the same device pool and/or CSS?  Your dialplan between both phones could be different and you might be transforming elsewhere.  Take a look at the phone, is it in a different  device pool than the working one?  Are the calling privileges the same between both, meaning the Calling Search Space is the same?  Are you dialing the exact same way for both phones?  Could you be matching to a route pattern that has the same digit match but in a different partition and thus accessed from the three digit extension? These are some of the things you will need to look into.

[Amit23]

no,

both phones are in different device pool.

phone A in pool a and it has second line of different pool and different css

phone b have pool b and it has second line that has pool a css and partition.

it is just like opposite of phone a configuration.

[Brandon Pierce]

You need to work out the configuration differences and trace how the call is completed.  Use the Dialed Number Analyzer (DNA) to help you with this and see where things are going wrong.

[Nadeem Ahmed]

Rightly Said by Java (+5).

First of all your Telco is not expecting that number format that why calls is getting failed. having Said second calls works . that you need to couple of sanity checks.

1) what is the number is being from CUCM to GW?

2) Is there any Translation rule configured and getting invoked?

3) If yes you need toggle that which dial-peer is it being applied to ?

4) Debug voice ccapi inout and isdn q931 and translation.

5) prior to that you need to be sure there is no issue with CUCM and CUCM is sending correct digit to GW and GW is the culprit who is modifying the digit while sending out the call to PSTN(Telco)

Please post your GW config and along with debug voice ccapi inout and isdn and translation after verifying the CUCM is in correct place. if CUCM is something modifying or incorrect TP,RP is getting hit then you need to correct the config on CUCM.

Br,

Nadeem Ahmed