Out Going Call H323 Fast Busy Call Manager 8.6(2)SU3

[Helmi Muzammil]

Hi All,

I have some problem with my two H323 Gateways ( 146.44.254.68 and 146.44.254.69) in Call Manager 8.6(2)SU3. My H323 Gateways is Hung.

when I outgoing call to H323 Gateway, the call being Fast busy. the digit not yet send to router. when i gather the SDI trace log, I see the Call Manager send Error 27 ( Destination Out of Order ) and send the dialed digit to 0.0.0.0 ( should be 146.44.254.68 and 146.44.254.69 ).

Then I reset both of h323 gateways in Call Manager, the 146.44.254.68 solved, The Call Manager can route the call to 146.44.254.68.

but my 146.44.254.69 gateway still problem, the call manager can't route the call to 146.44.254.69 with same error 27 (destination out of order). i have deleted and the add the gateway again, but the problem still persist.

what should i do? i need your advice.

Thanks,

[PCHoldmann]

Were these previously working?

If so, what changed, including things like power or network outages.

What are the gateways connecting to? PRI, analog, etc.

If it's PRI, does show ISDN summary show Multi-frame established?

Is h.323 bound to the correct interface on the router? Can you ping between the router to UCM from that interface?

[Helmi Muzammil]

Hi PCHoldmann,

Thanks for reply

the problem come after i added many new route pattern, and did BAT 2000 device phone.

my gateways connect to PSTN PRI, show isdn status in my gateways show multiple frame established.

and no connection problem with Call Manager and H323 gateway, both of them can reach each other.

I trya to add the 146.44.254.69 gateway to other call manager 6.1.4 for testing. and when i call to that gateway, call manager 6.1.4 can route the call to 146.44.254.69. so i think the problem is in my call manager.

Thanks,

Helmi

[Suresh Subramanian]

Hello Helmi,

Is the GW added to Route List and associated with Route pattern? or you have associated the GW directly to Route Pattern?

Please rate all the useful posts

[Helmi Muzammil]

Hi Suresh,

Thanks for reply.

First, the gateway added to route list and associated with route pattern. but the i try to associate the gateway directly to route pattern, but the problem still persist.

Thanks and Regards,

Helmi

[Manish Gogna]

If there is no firewall between this gateway and cucm and gateway has already been reset i would suggest a restart of ccm service on callmanager ( this is service impacting so should be done during off hours ).

HTH

Manish

[Helmi Muzammil]

Hi Manish Gogna,

Thanks for your reply.

I have tried restart the CCM service on Call Manager yesterday, but the problem still persist right now. what should i do then?

Thanks

Helmi

[Manish Gogna]

Can you share the following debugs from the gateway

debug ip tcp transaction and debug ip tcp packet

Please share the ip address of the callmanager as well.

Manish

[Helmi Muzammil]

Hi Manish,

Please find the debug ip tcp transcation and debug ip tcp packet attached.

I have 6 servers act as Call Manager Service.

146.44.254.167

146.44.254.168

146.44.253.167

146.44.253.168

146.44.4.167

146.44.3.167

Thanks

Helmi

[Ayodeji Okanlawon]

Helmi,

From the logs, we can see that your h323 gateway is configured to talk to two of your cucm..

146.44.254.167

146.44.4.167

The TCP connection for each of them is shown below..They look okay... We can see TCP ESTAB for both gateways..That suggest that the TCP connection is fine. Can you please do a test call and send the CUCM SDI traces..Include time of call, calling and called number

+++CUCM 254.167+++++

Jan 30 16:03:24.736 WIB: TCP0: state was CLOSED -> SYNSENT [23456 -> 146.44.254.167(1720)]

Jan 30 16:03:24.740 WIB: tcp0: I SYNSENT 146.44.254.167:1720 146.44.254.69:23456 seq 2588934838

        OPTS 4 ACK 3822062790 SYN  WIN 5840

Jan 30 16:03:24.740 WIB: TCP0: state was SYNSENT -> ESTAB [23456 -> 146.44.254.167(1720)]

Jan 30 16:03:24.740 WIB: TCP: tcb 71A8CB88 connection to 146.44.254.167:1720, peer MSS 1460, MSS is 1460

Jan 30 16:03:24.740 WIB: tcp0: O ESTAB 146.44.254.167:1720 146.44.254.69:23456 seq 3822062790

        ACK 2588934839  WIN 4128

Jan 30 16:03:24.740 WIB: tcp0: O ESTAB 146.44.254.167:1720 146.44.254.69:23456 seq 3822062790

        DATA 694 ACK 2588934839 PSH  WIN 4128

+++CUCM 4.167++++

Jan 30 16:02:08.947 WIB: tcp0: I LISTEN 146.44.4.167:51052 146.44.254.69:1720 seq 2541206725

        OPTS 20 SYN  WIN 5840

Jan 30 16:02:08.947 WIB: TCB6B3E98E0 created

Jan 30 16:02:08.947 WIB: TCP0: state was LISTEN -> SYNRCVD [1720 -> 146.44.4.167(51052)]

Jan 30 16:02:08.947 WIB: TCP: tcb 6B3E98E0 connection to 146.44.4.167:51052, peer MSS 1360, MSS is 516

Jan 30 16:02:08.947 WIB: TCP: Selective ack is disabled from the CLI

Jan 30 16:02:08.947 WIB: TCP: pmtu enabled,mss is now set to 1460

Jan 30 16:02:08.947 WIB: TCP: sending SYN, seq 4195712084, ack 2541206726

Jan 30 16:02:08.947 WIB: TCP0: Connection to 146.44.4.167:51052, advertising MSS 1360

Jan 30 16:02:08.947 WIB: tcp0: O SYNRCVD 146.44.4.167:51052 146.44.254.69:1720 seq 4195712084

        OPTS 4 ACK 2541206726 SYN  WIN 4128

Jan 30 16:02:08.975 WIB: tcp0: I SYNRCVD 146.44.4.167:51052 146.44.254.69:1720 seq 2541206726

        ACK 4195712085  WIN 5840

Jan 30 16:02:08.975 WIB: TCP0: state was SYNRCVD -> ESTAB [1720 -> 146.44.4.167(51052)]

Jan 30 16:02:08.975 WIB: TCB717C4F50 accepting 6B3E98E0 from 146.44.4.167.51052

Jan 30 16:02:08.975 WIB: TCB6B3E98E0 setting property TCP_NO_DELAY (0) 7117BC4C

Jan 30 16:02:08.975 WIB: TCB6B3E98E0 setting property TCP keepalive timeout (17) 7117BCCC

Jan 30 16:02:08.975 WIB: TCB6B3E98E0 setting property TCP_NO_DELAY (0) 7117BCA4

Jan 30 16:02:08.975 WIB: TCB6B3E98E0 setting property TCP_ALWAYSPUSH (15) 7117BCA4

Jan 30 16:02:08.975 WIB: tcp0: I ESTAB 146.44.4.167:51052 146.44.254.69:1720 seq 2541206726

        DATA 264 ACK 4195712085 PSH  WIN 5840

Please rate all useful posts

"The essence of christianity is not the enthronement but the obliteration of self --William Barclay"