You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Refer-To URI headers copied to target URI of outgoing INVITE (since fix for #962) #970
The fix for #962 removed the toAor() call from session.connect(request.refer_to.uri, options, initCallback);.
As intended, the URI parameters of the refer_to URI are now included in the outgoing INVITE,
but now the refer_to URI headers are copied, too.
In my understanding, this is wrong.
The URI headers in the refer_to URI shall be used to construct the INVITE (as it is done for the Replaces header
a few lines above), but they shall not be forwarded to the target in the request-URI or To header.
We don't want the target to include those headers into the messages originating from the target.
Activity
removing refer_to uri headers when creating target uri for INVITE - v…
jmillan commentedon Apr 24, 2026
Thanks for reporting. Can you please provide with a PR?
remove refer_to uri headers when creating target uri for INVITE - #970 (