> maybe depends on call destination > maybe the endpoint with 34 diconnect cause is dialing some weird > destination which is not available and the disconnect cause is received > from the terminating endpoint (gw); in this case gnugk is doing the right > thing...that is signalling the disconnect cause; > Are both gateways dialing the same numbers as destinations? Well, the two clients are dialing different prefixes, but gnugk rewrites them to the same prefix. They reach the gateway with the same numbers. What is weird is not really the disconnect code, but rather the fact that it comes after the call already starts. It is the first time I see calls with code 34 having positive duration. In the logs the terminating gateway sends the releasecomplete package to gnugk. So gnugk does its job of closing the connection. I am being told that direct connection to the terminating gateway does not produce these weird results. ------------------------- 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/
