The table within rfc3261 section 19.1.2 reflects the sip-uri parameters allowed when used within To and From. Note that transport has explicitly been made not optional. If I recall correctly, transport and other routing related parameters were excluded because the working group did not want them to potentially be used as part of an identity.
> -----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 _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
