The design of uac_replace_from() with record-route parameters is expecting that From/To headers are not changed. If that is done, then the endpoint is supporting the rfc3261 and restore should not be needed - e.g., change only for the initial invite and for the rest change the from/to to anonymous values.

If one of the devices is not rfc3261, the solution is to use the other mechanism from uac_replace_from(), that stores the initial values in dialog variables and don't rely on sip message at all.

For clarification: "brings the from URI Parser to crash" -- what do you mean by that? Like throwing errors or causing a crash? The first is ok, the second needs to be fixed. For first case, perhaps it's still some space for improvements, eg., check if the result has only allowed chars in order to do replacement, otherwise just write error logs and keep the old value.

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