> I have read rfc 3261, which according to 17.2.3 the > branch parameter in the topmost Via header field of > the request should be examined to match requests to > transactions. Cseq should only be checked if the > branch parameter in the top Via header s not present.
Yes; the magic cookie matching rule applies when Via branch present and starts with magic cookie. However if server completely relies upon the magic cookie rule, you hit the garbage-in garbage-out situation that you are experiencing. <snip> > Is our SIP stack correctly handles the transaction? Yes; however if memory constraints allow better validation, you might want to do the extra validation (as though magic cookie not present) to accommodate better interoperability with non compliant devices (even if the extra validation is considered to be non compliant). > Do you think it seems like a race condition where > further considerations should take place? It sounds like the notifier device needs to fix their Via branch generation algorithm. -- This email is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient and have received this email in error, please notify BroadSoft, Inc. immediately by replying to this message, and destroy all copies of this message, along with any attachment, prior to reading, distributing or copying it. _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
