> No, it does not. GKRouted is not the same as GkRouted. > I'd suggest checking the log to see if you receive any signaling > messages and make sure the signaling routed mode is enabled. It's a typo :"> but in the config file it's ok. And if it weren't in routed mode I wouldn't know when the calls are completed to the second. The LCFs contain the IP of the gnugk machine in the callSignalAddress and the rasAddress. Anyway, while looking at the logs I found out something interesting: succesful calls show after the LRQ job ends and it is deleted a "TCPServer 1 sockets selected from 4, total 4/0" from yasocket.cxx, then the proxychannel.cxx setup request. The 102 calls show Idle timeout for Worker 11111 / Worker 11111 closed. Could it be that the idle timeout is too short? I have in my config: SignalReadTimeout=10000 StatusReadTimeout=3000 StatusWriteTimeout=5000 SignalTimeout=60000 AlertingTimeout=60000 ------------------------- E-Mail powered by MadNet. http://www.madnet.ro/ ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&opÌk _______________________________________________________ List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id?49 Homepage: http://www.gnugk.org/
