Hi Vikas: A few answers inline. Cheers, Dan
--- On Sat, 1/17/09, VG <vikasraigu...@gmail.com> wrote: > From: VG <vikasraigu...@gmail.com> > Subject: Re: [sipxtapi-dev] TCP Connection Break? > To: dpet...@sipez.com > Cc: sipxtapi-dev@list.sipfoundry.org > Date: Saturday, January 17, 2009, 12:24 AM > Hi Dan, > > As you mentioned > its too late to get this TCP error out to the SIP stack, > but thats ok > > What is the Normal Timeout time. The SIP resends are defined in RFC 3261 (30 sec, 60, sec. 120 sec.) I think we keep TCP sockets around for an hour of idle time by default (i.e. no incoming or outgoing messages). > Do you follow the TCP Stack default time out Mechanism. > It could be 1hr then you will come to know about the > breakage of connection > after 1hr. Yes, if there is no outgoing send attempts during that period. Otherwise we should know at the first SIP transaction. > > Correct me if i am wrong. > > Regards, > Vikas > > > On Fri, Jan 16, 2009 at 9:10 PM, Daniel Petrie > <dpet...@sipez.com> wrote: > > > Hi Vikas: > > TCP has a hand shake to acknowledge that data was > received by the other > > side. In the sipX SIP stack all we worry about is if > the socket is still > > known to be good before sending. SIP requires resends > if there is no > > respond from the other side, even over TCP. So if a > socket has gone bad, > > but we do not know it yet, its ok. > > > > Here is why: > > + let say the socket is bad, but we don't know yet > > + we attempt to send a SIP message > > + the TCP socket returns successfully saying it sent > the bytes > > + no TCP ACK comes back and TCP attempts resends, but > still fails > > + its too late to get this TCP error out to the SIP > stack, but thats ok > > + as there was no SIP response, we attempt a resend, > this time we > > get a socket write error. Then the SIP stack should > attempt to reconnect > > the socket and/or failover using DNS SRV and try the > next alternative > > address. > > > > I hope this helps. If you are looking to accomplish > something else by > > checking the socket status, please let me know. There > are more active > > alternatives to keeping the sockets connected > specified in the SIP outbound > > IETF draft. We have not yet come across the need for > these yet. It would > > be great to understand how you are using sipX. > > > > Cheers, > > Dan > > > > > > --- On Fri, 1/16/09, VG > <vikasraigu...@gmail.com> wrote: > > > > > From: VG <vikasraigu...@gmail.com> > > > Subject: [sipxtapi-dev] TCP Connection Break? > > > To: sipxtapi-dev@list.sipfoundry.org > > > Date: Friday, January 16, 2009, 5:04 AM > > > Hi, > > > > > > I like to know is there any mechanism is > supported in tapi > > > regarding tcp > > > connection breakdown. > > > > > > Let suppose : > > > User A sending Sip on TCP -> Server > > > Now if link gets down how could this Server comes > to know > > > that Link is down. > > > > > > Or server still wait for the response from > Client. > > > > > > Is there any way to find out Connection Break > Down in TCP.. > > > >From both end Sending and Receiving. > > > > > > Please update me regarding it. > > > > > > Thanks in advanced. > > > Regards, > > > Vikas Gupta > > > _______________________________________________ > > > sipxtapi-dev mailing list > > > sipxtapi-dev@list.sipfoundry.org > > > List Archive: > > > http://list.sipfoundry.org/archive/sipxtapi-dev/ > > _______________________________________________ sipxtapi-dev mailing list sipxtapi-dev@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
