Hi Srini, It is also present in the Contact, Via and Request-Line and as I understand it, these are necessary requirements (well, if future communication is to be over TCP) but that's not the question.
The question is, is it valid to have transport=tcp as a URI parameter in the To and From headers? Calls are being rejected on this basis. I can't find anything forbidding it although I will concede that it is rather unnecessary. Cheers Steve -----Original Message----- From: Krishnamoorthy Srini-A19809 [mailto:[EMAIL PROTECTED] Sent: 16 January 2008 16:03 To: Stephen Paterson; [email protected] Subject: RE: [Sip-implementors] Transport=tcp interop problem Isn't the "Contact" header more appropriate for Uas to indicate the transport preference? Contact headers turn into request-URIs on the way back and the proxies and UAs route on request-URIs/Route headers, right?. We would obviously use the Via headers to indicate TCP properly (SIP/2.0/TCP) in the forward direction - guess there is no question there. -- Srini -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stephen Paterson Sent: Wednesday, January 16, 2008 10:51 AM To: [email protected] Subject: [Sip-implementors] Transport=tcp interop problem Hi all, When using TCP, we place 'transport=tcp' in both the To and From headers and it is claimed that the presence of this in the From header is invalid (interestingly the To header is not causing any grief). It seems to me that the From and To headers contain URIs and transport=tcp is a valid URI parameter so there should be no problem. Can anyone clear this up as I can't find anything definitive in 3261? Reference to the RFCs would be most appreciated. Cheers Steve Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales) P Please consider the environment and don't print this e-mail unless you really need to _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
