You can follow instructions I gave to James to provide me with enough details. You can also try to send a different valud for ConnectTimeout parameter in the gk config Let's say: [RoutedMode] # 60 seconds ConnectTimeout=60000 and see if the calls are still disconnected after 3 minutes. The problem is probably that your gateway is registered with the first gk. Try to register it as a permanent endpoint for both gatekeepers. I think your call routing path is incorrect - if the 1st gk is set up in signalling routed mode, it expects all signalling passes through it. But if you make a call from the 2nd gk, signalling flow is directly from ATA to GK2 and GW. So the GK1 disconnects call because even the signalling is not opened, but the call has been admitted. ----- Original Message ----- From: "Sebastian Nocetti" <snocetti@fibertel.com.ar> Sent: Wednesday, November 26, 2003 4:09 PM I have a GK and 3 GW registered against it and some ATA's Registered. Too I have another GK with same GW as permanent EndPoint and other ATA's registered. When a place a call from ATA on 1st GK, all is OK. But, when I place a call from ATA on 2nd GK, it obviusly send call to GW, and EVER call is unconnected after 160-170 secs. Too, I don't know why, I can see trhough status port on 1st GK calls made from 2nd GK, but without CALLER-IP. Somebody can help me?.. I don't know why call is unconnected on 2nd GK after 160-170 secs. ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ List: Openh323gk-users@lists.sourceforge.net Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
