Hi Expert, I am facing an issue on which the contact URI comparison has happened and it fails due to the TRC parameter not in order which I guess so far.
Contact: "" <sip:[email protected]:36948 ;transport=udp;Hpt=8ea2_16;ssn;srti=s1_2> Contact: "" <sip:[email protected]:36948 ;transport=udp;Hpt=8ea2_16;ssn;TRC=ffffffff-ffffffff;srti=s1_2> I saw in RFC 3261 19.1.4 URI Comparison URI uri-parameter components are compared as follows: - Any uri-parameter appearing in both URIs must match. - A user, ttl, or method uri-parameter appearing in only one URI never matches, even if it contains the default value. - A URI that includes an maddr parameter will not match a URI that contains no maddr parameter. - All other uri-parameters appearing in only one URI are ignored when comparing the URIs. Rosenberg, et. al. Standards Track [Page 154] ________________________________________ RFC 3261 SIP: Session Initiation Protocol June 2002 URI header components are never ignored. Any present header component MUST be present in both URIs and match for the URIs to match. The matching rules are defined for each header field in Section 20. ================================================ And Note that equality is not transitive: sip:[email protected] and sip:[email protected];security=on are equivalent sip:[email protected] and sip:[email protected];security=off are equivalent Rosenberg, et. al. Standards Track [Page 155] ________________________________________ RFC 3261 SIP: Session Initiation Protocol June 2002 sip:[email protected];security=on and sip:[email protected];security=off are not equivalent So does it mean the correct order should be given below where the TRC parameter should be put at the last? Contact: "" <sip:[email protected]:36948 ;transport=udp;Hpt=8ea2_16;ssn;srti=s1_2> Contact: "" <sip:[email protected]:36948 ;transport=udp;Hpt=8ea2_16;ssn;srti=s1_2;TRC=ffffffff-ffffffff> BR/// Rakesh Kumar Mohanty _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
