On Jan 4, 2023, at 12:17 PM, Henning Westerholt hw@gilawa.com wrote:
so far, we did not have any customer that need this functionality.
I've had numerous customers who have needed the functionality, and ended up having to use something like the "imaginative" Contact workaround instead.
I suppose it's hard to say whether the functionality was strictly necessary or born of a more puristic sensibility about how to make the proxy trapezoid work. :-)
However, a very common scenario for us is a customer from chan_sip to chan_pjsip, and having previously relied on Path support because it existed in chan_sip for approximately a decade. This means we had to totally rearchitect their systems, some of which have been very stable for about that long.
No, it's not that I'm entitled and think open-source projects owe us something for free, of course. But from a product management point of view, I think this is quite embarrassing. It's better to never have offered Path at all than to implement it (with considerable fanfare at the time!), then break it via a mandatory and quite controversial upgrade path (chan_sip -> chan_pjsip), then obstinately refuse to fix it.
-- Alex