Re: [EXT] Possible bug introduced in 5.8.5

Andreas Heil via sr-users <[email protected]>
Newsgroups gmane.comp.voip.ser
Message-ID <[email protected]>
Hi,

> Am 04.02.2026 um 12:20 schrieb Andreas Heil via sr-users <[email protected]>:
> 
>> 
>> But are you sure you're not calling uac_replace_... twice per packet processing? And for test - can you explicitly call msg_apply_changes() after uac_replace_...() and check?
> 
> I commented out every other use of uac_replace_to and even uac_replace_from.
> 
> 

I removed the uac_replace_…. from config completely.
And replaced the one in the branch_route with:

remove_hf("To“);
append_hf("To: <sip:[email protected];user=phone>\r\n“);

Now I get the following:
... snip ...
Privacy: none
P-Asserted-Identity: <sip:[email protected];user=phone>
 <sip:[email protected]:5060>From:  <sip:[email protected]:5060>;tag=94113SIPpTag001
Call-ID: [email protected]
CSeq: 2 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE, UPDATE
Content-Type: application/sdp
Supported: replaces, timer
User-Agent: XXXX
Content-Length:   252
X-CID: XXXXX
To: <sip:[email protected];user=phone>
... snip ...


Tried the same with 5.8.4:
... snip ...
Privacy: none
P-Asserted-Identity: <sip:[email protected];user=phone>
 From:  <sip:[email protected]:5060>;tag=94113SIPpTag001
Call-ID: [email protected]
CSeq: 2 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE, UPDATE
Content-Type: application/sdp
Supported: replaces, timer
User-Agent: XXXX
Content-Length:   252
X-CID: XXXXX
To: <sip:[email protected];user=phone>
... snip …

Don’t know where the leading space in the line with the From-header comes from.
I think our best option is to simply filter in front of kamailio (add the brackets on the ACME).

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!
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.