Inbound and Outbound calls not working in H323 Gateway

Inbound and Outbound calls not working in H323 Gateway

I have come across a situation where am unable to make inbound/outbound calls.

Here is the call flow
PSTN—VG-H323—MPLS—CUCM

This is debug of the actual failed incoming call

*Aug 9 06:10:03.923: //357/CCB999A780A0/CCAPI/ccSetMediaclassIp2ipTags:
media class tags set: NR 0, ASP 0
*Aug 9 06:10:03.923: //356/CCB999A780A0/CCAPI/ccSetMediaclassIp2ipTags:
media class tags set: NR 0, ASP 0
*Aug 9 06:10:03.923: //357/CCB999A780A0/CCAPI/ccGet_xc_nr_asp_info:
media class tags: NR 0, ASP 0
*Aug 9 06:10:03.923: //356/CCB999A780A0/CCAPI/ccGet_xc_nr_asp_info:
media class tags: NR 0, ASP 0
*Aug 9 06:10:03.923: //357/CCB999A780A0/H323/cch323_call_setup_normal: SETUP_NTF_TIMER is not running. Continue processing.
*Aug 9 06:10:03.923: //357/CCB999A780A0/H323/cch323_h225_set_new_state: Changing from H225_IDLE state to H225_IDLE state
*Aug 9 06:10:03.924: ISDN BR0/1/1:0 Q931: TX -> CALL_PROC pd = 8 callref = 0x81
Channel ID i = 0x89
Exclusive, B1
*Aug 9 06:10:03.950: //357/CCB999A780A0/H323/run_h225_sm: Received event H225_EV_SETUP while at state H225_IDLE
*Aug 9 06:10:03.950: //357/CCB999A780A0/H323/check_qos_and_send_setup: Setup ccb 0x7F04521FE1B8
*Aug 9 06:10:03.950: //357/CCB999A780A0/H323/run_h225_sm: Received event H225_EV_FS_SETUP while at state H225_IDLE
*Aug 9 06:10:03.950: //357/CCB999A780A0/H323/idle_fsSetup_hdlr: Setup ccb 0x7F04521FE1B8
*Aug 9 06:10:03.950: //357/CCB999A780A0/H323/generic_send_setup:
generic_send_setup: is_overlap = 0, info_complete = 0
*Aug 9 06:10:03.950: //357/CCB999A780A0/H323/generic_send_setup: ====== PI = 3
*Aug 9 06:10:03.950: //357/CCB999A780A0/H323/generic_send_setup: Send infoXCap=144, infoXRate=16, rateMult=0, xMode=128, info_layer1_prot=163
*Aug 9 06:10:03.950: //357/CCB999A780A0/H323/generic_send_setup: src address = 10.24.180.2; dest address = 10.24.203.205
Q931 Message IE Decodes
Protocol Discriminator : 0x08
CRV Length : 2
CRV Value : 0x0091
Message Type : 0x05: SETUP
Bearer Capability: Length Of IE=3
Data 9090A3
Called Party Number: Length Of IE=8
Data 8134343133353230
User-User: Length Of IE=566
Data 052080060008914A00042800B500001240013C05010000CCB999A7D93D11EA80A0A03D6FBCAB5000CD1D828007000A18B40287781100CCB9E7BBD93D11EA8351E2E218F9366D6704130000000C6013800B050001000A18B402205D001E400000060401004C60138012150001000A18B402205C000A18B402205D00130000010D4001800B050001000A18B402205D001E400001060401004D40018012150001000A18B402205C000A18B402205D000100010001800180010005420242524911A810010E6000011000930001550443000000018080CA0140B500001280C2E001010001A180B0A104039090A31801891E0284837007813438333532301C989E8100036774640000008D49414D2C0D0A50524E2C6973646E2A2C2C2C0D0A5553492C726174652C632C332C632C310D0A5553492C6C6179312C616C61770D0A544D522C30320D0A43504E2C30302C2C312C3438333532300D0A4350432C30390D0A4643492C2C2C2C2C2C2C792C0D0A4743492C63636239393961376439336431316561383061306130336436666263616235300D0A0D0A188000060004000000038095420467746401808D49414D2C0D0A50524E2C6973646E2A2C2C2C0D0A5553492C726174652C632C332C632C310D0A5553492C6C6179312C616C61770D0A544D522C30320D0A43504E2C30302C2C312C3438333532300D0A4350432C30390D0A4643492C2C2C2C2C2C2C792C0D0A4743492C63636239393961376439336431316561383061306130336436666263616235300D0A0D0A
*Aug 9 06:10:03.951: //357/CCB999A780A0/H323/cch323_h225_set_new_state: Changing from H225_IDLE state to H225_REQ_FS_SETUP state
*Aug 9 06:10:03.951: //357/CCB999A780A0/H323/run_h245_iwf_sm: received IWF_EV_FASTSTART while at state IWF_IDLE
*Aug 9 06:10:18.951: //357/CCB999A780A0/H323/cch323_h225_send_release: Cause = 102; Location = 0
*Aug 9 06:10:18.951: //357/CCB999A780A0/H323/cch323_h225_send_release: h225TerminateRequest: src address = 169391106; dest address = 10.24.203.205
Q931 Message IE Decodes


Q931 Message IE Decodes
Protocol Discriminator : 0x08
CRV Length : 2
CRV Value : 0x0091
Message Type : 0x5A: RELEASE_COMP
Cause: Length Of IE=2
Data 80E6
User-User: Length Of IE=34
Data 052580060008914A000411001100CCB9E7BBD93D11EA8351E2E218F9366D10800180
*Aug 9 06:10:18.951: //357/CCB999A780A0/CCAPI/cc_api_call_disconnected:
Cause Value=18, Interface=0x7F0440A44BF8, Call Id=357


Debugging Enabled for H323 Call:

· debug cch323 h225 and debug cch323 h245 –>call setup and tear down checking.
· debug voip dialpeer —>to check dial peer matching
· debug ip tcp transaction —-> to make sure that the TCP session for H.225 and H.245 is being established
debug isdn q931 –> to check idsn logs


Few things need to take a note :

H323 and SIP gateway never registers with the Call Manager.
· Call Manager shows the status of the H323/SIP Gateway as Unknown.

Make sure these configurations are in place in H323 Gateway

1. Step 1

conf t
voice service voip
allow-connections h323 to h323

allow-connections h323 to sip
allow-connections sip to h323

2. Step 2

GW1(config)#voice service voip
GW1(conf-voi-serv)#h323

3. Step 3 – Try resetting H323 by issuing

no h323
h323


4. Make sure your call manager IP is added in the trusted list
you can verify using the below command

show ip address trusted list

5. Make sure you bind the source interface

interface GigabitEthernet0/0/0
description **** LAN
ip address 10.X.X.X 255.255.255.0 >> Gateway ip address
ip nbar protocol-discovery
delay 10000
negotiation auto
h323-gateway voip interface
h323-gateway voip bind srcaddr 10.X.X.X >> gateway ip address

Else you can give the loop back IP as well but make sure you configure the same IP in the H323 Gateway else the call will be rejected
Router(config-fa)h323-gateway voip interface //
This command will bind interface IP Address with H323 for signaling. It used because H323 signaling contains different source address so to make it a single ip address need to bind with interface

6. Fail over configuration

dial-peer voice 2020
destination-pattern 44….
session target ipv4:10.X.X.X
preference 0 —->Preference 0 (This is the primary route for connecting with CUCM)
voice class h323 1

dial-peer voice 2021 voip
destination-pattern 44….
session target ipv4:10.1.1.102
preference 1 —->(Backup route to cucm)
voice class h323 1

7. And finally reset the H323 gateway in CUCM

Please see if this help , else leave your comments to assist you

Happy Learning! Happy Sharing!

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *