Probably nothing wrong will happen:). You may land with 4 hour long calls in case, when ARQ/ACF sequence is completed, but no signalling channel has been opened (due to equipment failure or network failure). But this should be a very rare case. ----- Original Message ----- From: "Mike Ockenga" <Mike.Ockenga@xxxxxxxxx> To: "GNU Gatekeeper Users" <openh323gk-users@xxxxxxxxxxxxxxxxxxxxx> Sent: Monday, December 10, 2007 8:14 PM Subject: SignalTimeout value modification question > In RasTbl.h, the variable m_timeout is type "long", so I could > theoretically set SignalTimeout=14400000 (4 hours) in my *.ini to > support 4-hour calls where the gatekeeper (in routed mode) actually > doesn't see the Q.931/H.2X5 traffic for IP-dialed calls from "the > Internet" to registered systems. > > What havoc could that cause? > > -- > Mike Ockenga ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________________ Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_name=openh323gk-users Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users Homepage: http://www.gnugk.org/
