cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
715
Views
0
Helpful
1
Replies

H323 via Gatekeeper fails with Temporary Network Failure

b.t
Level 1
Level 1

Hi All - The dreaded Temporary Network Failure error

I am trying to troubleshoot a fairly complex call routing issue, and am struggling to find the right debug to use.......

Call routing is:

PBXa --> E1 --> MGCPRtrA --> Gatekeeper --> H323RtrB --> E1 --> PBXb

If I can believe the users, they are saying that the problem is intermittent (although I have never managed to get a call through).

If have used debug ISDN Q831 and debug voice CCAPI inout.  A ping from router A, shows 16 hops to the destination, and I am told that there is also a firewall between, so there are multiple points that this could be failling.

What I am trying to find, is a way to debug that will point me in the direction of the root cause - whether it be CODEC, or network, bandwidth or gatekeeper.

Any ideas?

Thanks in advance

Brian

Debug attached from Router B:

Calling number=8753

Called number=8600456921, then translated to 6921

(I have also been down the debug ras and debug h225 asn1 route)

1 Reply 1

Aashish Jolly
Cisco Employee
Cisco Employee

Hi,

   The debugs you've provided do not have h225 asn1 or h225 ras messages. However it does look like an issue with the codec. Some things that I noticed

1. You do not have a dial-peer on RtrB for inbound calls, it is matching dial-peer 0. I would not prefer that, create a separate dial-peer for matching voip calls, something similar to this

dial-peer voice 100 voip

  description ++ Inbound VoIP Calls ++

  incoming called-number .

  voice-class codec 1

  dtmf-relay rtp-nte h245-signal h245-alphanumeric

2. Check the dial-peer on RtrA and find out the codec being used, it should be g729r8. I do see g729br8 in the debugs and since we have dial-peer 0 matching, it may fail. So make sure on the codec on RtrA

Let us know if this helps.

Regards,

Aashish