My fix does not break anything, as the re-hashing can be disabled by config. Backward compatibility is a must, always, in my opinion. I did a mistake though. Default value, if variable is not set, should be 0 ("disabled"). That would be something to modify.

Maybe in August 2004 servers and resources where much cheaper. Nowadays most telco companies can't afford to have double amount of resources, in case kamailio decides to duplicate the load over one of the destinations. I can be sarcastic too, and I don't see how that helps debating over this issue.

Regarding relying on Record-Route to secure delivery to same destinations : Maybe you are not aware of all SIP scenarios. For instance, SIP CANCEL, which must follow same path as original INVITE, and Record-Route has no use then. Same applies for ACK for non 2xx replies.

Maybe documentation should indicate that, if the optional priority field is not present, entries on file dispatcher.list are considered in reverse order. Hard to know that in advance.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.