Have you taken a look how this options works? It does not solve
NAT mapping keep alive problem.
----- Original Message -----
From: "Daniel Liu" <daniel.liu@...>
Sent: Saturday, March 27, 2004 7:52 AM
> Dear Julian,
> There is already a option to set the NATKeepaliveInterval for incoming call.
> I think this is for you.
> Default: 86400
> Keepalive interval in second for NAT socket. Leave it out if you don't understand it
> Julian write:
> > To solve this problem, we can let the subgk transmit a Information IE with call state:Q931::CallState_IncomingCallProceeding on
reception of RCF from the parent gk, this can make the TCP link not to be removed by the NAT router, usually NAT router with remove
TCP links which stay at idle state for one hour!
> > The attachment is the modified GKClient.cxx of gnugk v2.07 windows version.
> > ----- Original Message -----
> > From: Julian
> > To: openh323gk-developer@...
> > Sent: Tuesday, March 23, 2004 11:25 AM
> > Subject: Urgent BUG under proxy mode
> > Dear all,
> > As NAT routers don't keep dynamic links perminantly, and gnugks don't send packets on call signaling channels when it is at idle
state. This can cause a serious problem, the call signaling link items will be deleted on the routers after usually one hour, then
any incoming calls for the NATed gateway would fail.
> > I think to solve this problem, we can send information IEs on such TCP links when we get keep alive RRQs from the gateways or
subgks, do you agree with it?
> > I will provide the patch ASAP.
> > Regards,
> > Julian