Hi Matthew, In RFC 3665 Section 3.1, transport=tcp is included in the Contact to intimate to other party that in case of any new requests within that dialog, the other party MUST use the Contact address provided and transport as TCP.
I think the transport in top-most Via decides which transport to use while sending the messages. Regards, Somesh S. Shanbhag --- Matthew Gardiner <[EMAIL PROTECTED]> wrote: > Thanks Somesh, > > Yes my stack will stamp TCP or UDP into the Via > prior to transmitting the > message. I was really querying which fields in the > message inform the stack > as to which socket type (i.e. stream, datagram) to > send the message out on. > > I wonder, does your answer imply that examples such > as message F1, in > section 3.1 of RFC3665 are syntactically incorrect > as here we have an INVITE > with "transport=tcp" in the Contact: but no such > parameter in the > Request-URI? > > thanks, > Matt > > > -----Original Message----- > From: Somesh S Shanbhag [mailto:[EMAIL PROTECTED] > Sent: 07 November 2005 13:10 > To: Matthew Gardiner; > sip-implementors@cs.columbia.edu > Subject: Re: [Sip-implementors] SIP over TCP > > > Hi Matthew, > > You have to change the Via also. Something like this > .. > > Via:SIP/2.0/TCP > 172.16.25.17:5060;branch=z9hG4bK-c7542 > > Regards, > Somesh S. Shanbhag > > --- Matthew Gardiner <[EMAIL PROTECTED]> > wrote: > > > Hi all, > > > > Could somebody please list the part(s) of a SIP > > message which must be > > changed in order to indicate to a SIP stack that > the > > message should be sent > > using TCP? > > > > I imagine these to be the Contact: header, in > order > > that the UAS knows > > whether or not to formulate a TCP or UDP packet > for > > a future request and the > > Request-URI to indicate to the transmission logic > in > > the stack that the > > destination is listening on a TCP port. If someone > > could confirm/deny my > > assumptions that would be greatly appreciated. > > > > thanks for your time, > > > > Matthew Gardiner > > Software Engineer > > Aculab > > > > > > _______________________________________________ > > Sip-implementors mailing list > > Sip-implementors@cs.columbia.edu > > > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > > > > > ----------------------------------------- > SIMPLICITY IS THE BEAUTY. > BE NATURAL LIVE NATURAL. > ----------------------------------------- > Somesh S. Shanbhag > Focus Area - VoIP Team (FA-VoIP) > Mascon Global Communication Technologies > Enterprise of Mascon Global Limited > #59/2, 100Ft Ring Road > Banashankari II stage > Bangalore-560070 > Karnataka > INDIA > Website: http://www.masconit.com > ----------------------------------------- > > > > > __________________________________ > Yahoo! Mail - PC Magazine Editors' Choice 2005 > http://mail.yahoo.com > ----------------------------------------- SIMPLICITY IS THE BEAUTY. BE NATURAL LIVE NATURAL. ----------------------------------------- Somesh S. Shanbhag Focus Area - VoIP Team (FA-VoIP) Mascon Global Communication Technologies Enterprise of Mascon Global Limited #59/2, 100Ft Ring Road Banashankari II stage Bangalore-560070 Karnataka INDIA Website: http://www.masconit.com ----------------------------------------- __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com _______________________________________________ Sip-implementors mailing list Sip-implementors@cs.columbia.edu http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
