cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
545
Views
7
Helpful
7
Replies

H.323 Gateway Inbound Calls Not Working

h.matsalia
Level 1
Level 1

Hi Guys,

I'm having an issue with my H.323 Gateway. It was working before, but the incoming calls were coming in with unkown identity. In the process of troubleshooting from the CUCM, we reached a point that we decided to delete the H.323 gateway, adding it back we lost the inbound calls. We can only call out but when someone calls the call appears to be going through then drops.
If someone will help resolve this I will really appreciate.

CUCM: vrs 11.0, 

Cisco Router: 2811

GSM Gateway: Huawei, B683

7 Replies 7

You need to provide more detail for anyone here to be able to help you. The router configuration and the relevant CUCM IP address(es) would be a good place to start.

Hi @Elliot Dierksen ,

Thank you for your reply, it was working with the same router configuration, the changes we did was only in the CUCM. Though I can provide them for escalation purposes. 

If the inbound calls are ringing, but then dropping when someone picks up (which is what I'm inferring from what you wrote), that would imply a codec issue. If that is the case, check the codec list that the gateway is using to communicate into CUCM and check that against the Region setting on the gateway config in CUCM. 

Another possibility, to the point @Elliot Dierksen made, is that there is an IP issue. Please provide the IPs of CUCM and the H323 gateway. Also provide the H323 binding address on the gateway and whether that matches the IP of the gateway as configured in CUCM.

Once we have that and take a look we may ask for some debugs. We will help get you sorted.

Maren

Hi @Maren Mahoney ,

Thanks for your reply, though the issue we are facing is inbound calls are not coming in at all, the phone is not even ringing, and the outbound are perfect.
We were troubleshooting the issue of unknown identity calls on the CUCM as result the issue affected our calls the inbound call.

I agree with @Nithin Eluvathingal that it is possible that when you re-added the gateway in CUCM that a setting such as the inbound calling search space was missed. Please double-check that, along with the IP set in CUCM (specifically that it matches the H323 bind address in the GW).

If you have tried all of the suggestions listed, you will need to provide more details for us to continue troubleshooting. Please provide screenshots of the GW config in CUCM, along with the router config. If possible, also attach the trace file containing an inbound call that fails so that we can see what CUCM is doing when it receives signaling from the gateway. When you include your config and your trace file, please upload them as attachments to a post (rather than pasting the text into the post itself). Doing so make them much easier for us to work with.

Maren

From your post, I assume you were troubleshooting only from the CUCM and you deleted the H323 gateway from the CUCM and then added it back, and now you’ve noticed that incoming calls are not working.

Can you check if the inbound significant digits and the calling search space are configured the same as before?



Response Signature


Vaijanath Sonvane
VIP Alumni
VIP Alumni

Hi @h.matsalia,

Just to add to what other members have pointed, please check below as well:

  • Ensure the H.323 protocol is correctly bound to the correct interface on the gateway. Maybe you can try removing the command from interface and add it back. 
  • Ensure the gateway is correctly added back to the CUCM with the correct IP address and relevant settings like number of digits, calling search space etc.
  • Ensure the dial-peers for inbound calls have the appropriate destination-patterns and session targets pointing to the CUCM.
  • Ensure the translation rules or called number modifications are correctly applied, if used.
  • Check if any voice class codecs or digit manipulation were configured and reapply them as needed.

 

 

Please rate helpful posts and if applicable mark "Accept as a Solution".
Thanks, Vaijanath S.