This may signal that either the gatekeeper failed to log accounting records or some internal call timer (for a particular call state) expired. There are various timeouts, the latest cvs introduces additional timeout for Setup->Alerting and Alerting->Connect max timeouts.
----- Original Message ----- From: "Costin Manda" <siderite@xxxxxxxxx>
Sent: Thursday, March 31, 2005 12:42 PM
I used to have this setup: CiscoGW -> CiscoGK -> third party | --> Gnugk (for certain destintations)
I changed the setup by switching Gnugk and CiscoGK.
The problem is that I get a fair share of Interworking errors (127decimal) on the Cisco GW and gnugk logs the calls as 41 decimal.
any suggestions?
Details. I am looking at the gnugk detailed log and I see everything as it should be: RRQ, RCF ARQ, LRQ, RIP, LCF, ACF Setup fastStart[0] fastStart[1] SetupCF CallProceeding IRR (from my Cisco GW) (IRR received, then next line Job IRR deleted) then out of a sudden gnugk sends to Cisco GW a disengageRequest with disengagedReason=forcedDrop
------------------------------------------------------- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/Info/Sentarus/hamr30
_______________________________________________________
List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
