Hi Chris, Many thanks for the reply.
This draft looks very useful. The original SIP RFC was somewhat vague when describing SIP over TCP. This has resulted in implementations with much variability in behaviour. As a result of this, interoperability problems seem to be relatively common. I'm glad this draft gives everyone some recommended (and sensible) behaviour!! Thanks again, Attila >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] Behalf Of Chris >> Boulton >> Sent: 17 June 2005 13:02 >> To: Attila Sipos; Ehsan Abouzeid; [email protected] >> Subject: RE: [Sip-implementors] SIP over TCP problem >> >> >> Most definitely not recommended. The re-use of existing TCP >> connections >> is encouraged for scalability. >> >> Take a look at:- >> http://www.ietf.org/internet-drafts/draft-gurbani-sipping-con >> nection-gui >> delines-01.txt >> >> >> Chris. >> >> >> -----Original Message----- >> From: Attila Sipos [mailto:[EMAIL PROTECTED] >> Sent: 17 June 2005 12:44 >> To: Ehsan Abouzeid; [email protected] >> Subject: [Sip-implementors] SIP over TCP problem >> >> >> Hi all, >> >> I have a user-agent which gets an INVITE (sent over TCP) >> from some kind of server. >> The user-agent keeps this TCP socket open for the >> duration of the call. At the end of the call, the >> user-agent user hangs up and so the user-agent sends >> a BYE using the same original TCP connection. >> >> This is OK isn't it? >> >> The server does see the BYE. >> The server makers complain that the user-agent >> should drop the original TCP and open up a new >> one to send the BYE. >> Is this really necessary? >> What's wrong with using the original TCP connection? >> >> Regards, >> >> Attila >> >> Attila Sipos >> http://www.vegastream.com >> >> >> >> >> >> _______________________________________________ >> Sip-implementors mailing list >> [email protected] >> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors >> >> >> Information contained in this e-mail and any attachments are >> intended for the use of the addressee only, and may contain >> confidential information of Ubiquity Software Corporation. >> All unauthorized use, disclosure or distribution is strictly >> prohibited. If you are not the addressee, please notify the >> sender immediately and destroy all copies of this email. >> Unless otherwise expressly agreed in writing signed by an >> officer of Ubiquity Software Corporation, nothing in this >> communication shall be deemed to be legally binding. Thank you. >> >> >> _______________________________________________ >> 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
