On Tuesday 01 March 2005 01:58, Ray Jackman wrote: > 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 100% correct. As I mentioned, GnuGK should have defined a list of disconnect code values, which will trigger a rerouting. Obviously codes like 16,17,18,19 (not sure for 16), should not cause rerouting :) > > > ------------------------------------------------------- > 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/ ------------------------------------------------------- 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/
