How does the SIP handler work in R80 and above?

[Hugo_vd_Kooij]

Hi,

I was used to the concept that if you have service with SIP hander op UDP/5060 (the default) and a UDP/5060 object without the SIP handler that the order of the rules was important.

In R7x the issue is that if you have SIP handler attached to a service in rule N then this handler is attached to the port on all following rules. In that repect the exact order of rules was vital as using a rule too late would still put a SP handler on UDP port 5060 because that was done on a higher rule.

With R80 and bove rule ordering is more complex. And I now see logs that seem to indicate the old rule order thing is less relevant: as you can see in the attache image.

So how does that work these days in R80 and above?

[PhoneBoy]

I think it matters less due to Column-based matching, which evaluates destination first, then source, then service.
However, I could still see the order being relevant if a particular connection matched multiple rules and the more complex service handler was listed in the rule that matched first.
Don’t know that for sure but makes sense logically.