Hi Expert, Now I got the full picture for the problem.
SIP Registrar behavior for the URI contact matching 1) REGISTER request with belwo contact send to Registrar Contact: ""<sip:+168999@178.21.49.29:3694 ;transport=udp;Hpt=8ea2_16;ssn;srti=s1_2>;expires=7200 2) Registrar sent 200OK with below contact Contact: ""<sip:+168999@178.21.49.29:3694 ;transport=udp;Hpt=8ea2_16;ssn;srti=s1_2>;expires=7200 3) Now there is another REGISTER request send to the Registrar in contact with additional parameter mentioned below Contact: ""<sip:+1689998@178.21.49.29:3694 ;transport=udp;Hpt=8ea2_16;ssn;TRC=ffffffff-ffffffff;srti=s1_2>;expires=7200 4) Then Registrar sent 200OK response with below contact headers. Where the Initial contact has value expires= 0 Contact: ""<sip:+168999@178.21.49.29:3694 ;transport=udp;Hpt=8ea2_16;ssn;srti=s1_2>;expires=0 Contact: ""<sip:+1689998@178.21.49.29:3694 ;transport=udp;Hpt=8ea2_16;ssn;TRC=ffffffff-ffffffff;srti=s1_2>;expires=7200 So is it a valid behavior from Registrar server? Which leads the earlier post asked for contact matching. BR/// Rakesh Kumar Mohanty On Fri, Jul 14, 2017 at 8:17 PM, Paul Kyzivat <pkyzi...@alum.mit.edu> wrote: > 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
