For example, I have providers that return back > LRJ messages when they are at full capacity or not able to complete the > call for which ever reason. Most of these LRJ messages come back with > release code undefine. Which hit the part of the code where no route to > destination is set to the release code of authData.m_rejectReason = > request.GetRejectReason();. This returns a different type of release code > that we cannot re-route on. I'm not saying this is the case for everyone, > but its a specific case for us. very cleaver. good job. i dont use LRQ's to process routes that way so i have not directly seen this problem yet. i just thought that gnugk would send LRQ and if destination was found then call would go thru and if no destination was found as in LRJ then gnugk would respond with "no route to host" which my customers are able to re-route on. thanks for pointing out this situation. regards ray ------------------------------------------------------- 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_id=6595&alloc_id=14396&op=click _______________________________________________________ List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
