Gatekeeper sending DRQs

Unanswered Question
Jul 9th, 2008
User Badges:

Hi!

Can anyone tell me under which conditions a Cisco gatekeeper might be forcing a call down between two endpoints (Disengage Reason = forcedDrop?

The call is running fine for 15 minutes, and then BAM! It gets disconnected.

Sniffer traces show that the disconnect is sent by the gatekeeper without a previous event from any endpoint.

Can anybody help?


Best Regards,


Ariel

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
gogasca Wed, 07/09/2008 - 20:18
User Badges:
  • Green, 3000 points or more

Can we get debug h225 asn1, debug ras debug gatekeeper main 10

to find out

Also more details of the topology?

Any FW?

IOS versions

Exactly at 15:00 ? this may be a time rissue

Try

(config-gk)#timer irr period (increase it)

or

(config-gk)# no irq global-request



Thanks


arielroza Thu, 07/10/2008 - 07:22
User Badges:

Hi, Gonzalo.


The gatekeeper sits in the middle of a network with many PBXs, but is showing this behaviour only when handling a call between a Nortel BCM400 and another PBX (a second Nortel BCM400 or an Avaya). The PBXs are attached directly to the nework, with an IP Network Adapter.


IOS version is 12.4.(3a)

arielroza Tue, 08/11/2009 - 05:57
User Badges:

If anyone stumbles upon this thread. I found the reason. It turned out to be that the Nortel BCM400 did not support the IRQ (Information Requests) that the Gatekeeper sends to try to get information on an active call (when the participating gateway does not update the call info itself.)


As the PBX does not support this message, the gatekeeper sent a DRQ to Nortel after 3 unsuccesful IRQ attemps (12 minutes), that then complied and dropped the calls.

Actions

This Discussion