I agree, although when porting from SER to OpenSER it broke some of my logic
Which led me to discover the wonders of branch routing, which was a much better solution to my problem
Juha Heinanen wrote:
Tavis P writes:
With OpenSER, using the same config, in the same situation it would send the CANCEL first to itself and then to the endpoint.
this is the correct behavior and avoiding it would be difficult, for example, when the request is forked by the second ser instance.
-- juha