Hello, have you tried with the latest 5.8.7? Or just with 5.8.5?
Cheers, Daniel On 03.02.26 16:26, Andreas Heil via sr-users wrote: > Hi all, > > I’m currently testing a migration from version 5.6.x to 5.8.x. > > The problem: > 1. INVITE comes in with a To-header like this: > > To: sip:[email protected]:5060 > > 2. uac_replace_to in a branch_route: > > uac_replace_to("", > "sip:+$(avp(newDAD){s.replace,CC,})@$var(carrierDomain);user=phone“); > > Note: It does not matter if we try to change the To in different ways like: > uac_replace_to("", "sip:[email protected];user=phone“); Or: $td > = > „some.carrier.net"; > > 3. What gets on the line is: > > To: > <sip:[email protected]:5060>sip:[email protected];user=phone > > Or in case of ($td): > > To: <sip:[email protected]:5060>some.carrier.net > > Note: the INVITE received has 1 space between „To:" and Content, The INVITE > send has 2 spaces. > > The bug only appears if the initial to-header is NOT enclosed in < >. > > I could track it down to version 5.8.5 in which it appeared first. > Everything before (including 5.8.4) behaves normally. > > I think it’s introduced by commit 6367a41f64ed165792ffe71ea310fd917947ccba > There is a comment beneath it, that reports something similar with the From > header, too. > > How can I fix that in the config, or is it a bug? > > Greetings, > Andreas > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions -- > [email protected] > To unsubscribe send an email to [email protected] > Important: keep the mailing list in the recipients, do not reply only to the > sender! -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio World Conference, May 7-8, 2026 - Berlin, Germany -- kamailioworld.com
__________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions -- [email protected] To unsubscribe send an email to [email protected] Important: keep the mailing list in the recipients, do not reply only to the sender!
