Hi Ray, If you look at the code where the change is made, it is only changed when there is no route to destination. Is not for every call the completes with a normal event release code. 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. Freddy -----Original Message----- From: openh323gk-users-admin@xxxxxxxxxxxxxxxxxxxxx on behalf of Ray Jackman Sent: Mon 2/28/2005 6:58 PM To: openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Subject: Re: Configuring Reject / Disconnect Cause On Monday 28 February 2005 17:06, Teodor Georgiev wrote: > indeed, GnuGK can not only rewrite the disconnect cause, but also use it to > make the alternate routing decision. > > //FP REMOVED BY ME-authData.m_rejectReason = request.GetRejectReason(); > authData.m_rejectCause = Q931::NoRouteToDestination; > wont this make you re-route on "user-busy" ? not all disconnect codes should end up as no route to destination. just my thoughts. 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/
<<winmail.dat>>
