The keep-alive time is not a function of the service provider, it's a function of the NAT firewall. The latest update to ICE includes adding keep-alives to the protocol. However ICE is still very far away from being an IETF standard and is very much evolving.
You can test keep alives with an external party through an extensive tunneling test (a proposal exists to add this function as one of the tests in STUN). To be conservative I would start with a keep-alive time less than the default* Connection Establishment Time* for a TCP packet. A time less than 60 seconds will work in most implementations however times as little as 5 seconds may be needed for some NAT routers. On 12/08/05, Nataraju A B <[EMAIL PROTECTED]> wrote: > > > > Regards, > Nataraju A.B. > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Rakesh > Dhandhukiya > Sent: Tuesday, August 09, 2005 1:03 PM > To: [email protected] > Subject: [Sip-implementors] keep alive with NAT in SIP > > Hi ! > > I want to keep alive with NAT. First of how to know the keep alive > timeout of NAT for UDP. Is there any file like tcp timeout ? > Is ICE used for NAT keep alive? > > [ABN] service provider may not disclose these timer values... only way > to find out these timer values would be to use trail and error > method.... > I don't think ICE been used to NAT keep alive... > > Thanks. > > Rakesh Dhandhukiya > _______________________________________________ > Sip-implementors mailing list > [email protected] > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > > _______________________________________________ > Sip-implementors mailing list > [email protected] > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > -- Michael Slavitch Ottawa, Ontario Canada _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
