we just noticed an issue using this function

when we call it with 2 params (display and uri) and the SIP INVITE comes with a From uri like

sip:anonymous@anonymous.invalid; tag=13133439191609, without <> delimiters, then doing the uac replace in the ACK we have

 2(14923) DEBUG: uac [replace.c:922]: replace_callback(): DOWNSTREAM direction detected - replacing uri with the new uri
 2(14923) DEBUG: uac [replace.c:943]: replace_callback(): Replace [ sip:anonymous@anonymous.invalid] with ["14254350027" sip:14254350027@1.1.18.171]
 2(14923) DEBUG: uac [replace.c:980]: replace_callback(): inserting display ["14254350027"]

And this is the From header replaced

From: sip:14254350027@1.1.18.171"14254350027" <>;tag=13133439191609

But if the call comes with a From header like
<sip:anonymous@anonymous.invalid>; tag=13133439191609

Then this is the From header replaced
 2(19741) DEBUG: uac [replace.c:922]: replace_callback(): DOWNSTREAM direction detected - replacing uri with the new uri
 2(19741) DEBUG: uac [replace.c:943]: replace_callback(): Replace [ sip:1241342@1.1.18.171:5074] with ["14254350027" sip:14254350027@1.1.18.171]
 2(19741) DEBUG: uac [replace.c:980]: replace_callback(): inserting display ["14254350027"]


From: "14254350027" <sip:14254350027@1.1.18.171>;tag=13133439191609

Were you aware of this kind of behaviour? If possible we will look for a patch for this.

thanks a lot and regards

david