Hi Manpreet, Yes, I agree with you that this is inefficient. However, the behaviour you describe is allowed in SIP. Unfortunately in SIP, the usage of TCP sockets is very "promiscuous".
I believe the following draft tries to address the connection inefficiency of SIP over TCP (and SIP over TLS): http://www.ietf.org/internet-drafts/draft-ietf-sip-connect-reuse-07.txt However, it is not standard and you would still need to be able to handle multiple SIP sockets per call if you want to be able to interop with current SIP over TCP implementations. Regards, Attila Attila Sipos http://www.vegastream.com >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] Behalf >> Of Manpreet >> Singh >> Sent: 30 October 2006 04:05 >> To: [email protected] >> Subject: [Sip-implementors] SIP over tcp >> Importance: High >> >> >> Hi >> >> For a UA to do SIP over TCP, wont it be sufficient to open one TCP >> connection and exchange all messages related to the INVITE >> transaction and >> for future mid dialog/other transactions ( BYE, Re-invite >> etc ) over the >> same connection? I have seen implementations where for every >> new request in >> the dialog, a new tcp connection is made and the previous >> one is torn down. >> Is that necessary? Does any draft tell what should be the right >> implementation? >> >> thanks >> >> M. >> _______________________________________________ >> Sip-implementors mailing list >> [email protected] >> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors >> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
