On 7/14/17 3:53 AM, Rakesh wrote:
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:+12345@179.18.39.29:36948;transport=udp;Hpt=8ea2_16;ssn;srti=s1_2>
Contact: ""
<sip:+12345@179.18.39.29: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:
...
The following:
- All other uri-parameters appearing in only one URI are
ignored when comparing the URIs.
is the operative rule here.
So does it mean the correct order should be given below where the TRC
parameter should be put at the last?
Contact: ""
<sip:+12345@179.18.39.29:36948;transport=udp;Hpt=8ea2_16;ssn;srti=s1_2>
Contact: ""
<sip:+12345@179.18.39.29:36948;transport=udp;Hpt=8ea2_16;ssn;srti=s1_2;TRC=ffffffff-ffffffff>
What leads you to this conclusion? Parameter order is never relevant.
Thanks,
Paul
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
