There is no real meaning to transport parameter in From or To header. So UAS should just ignore it. Rejecting request based on it, does not seem correct.
>-----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 > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
