Re: 6.0.2 to 6.1.1 Migration issue: malformed From header no longer reachable in routing script

Hello,

On 13.03.26 12:10, m.cazzola--- via sr-users wrote:
> Thank you for your response. 
>
> Actually, we are using sanity module. We call sanity_check() in our CFG which makes the other types of malformed messages correctly return 400. 
>
> However, it seems that after upgrading versions, this specific case (malformed From header) is not even reaching the CFG logic layer. I don't know if there is some sort of built in flag (like a STRICT_SIP_PARSINNG)  that can allow us to return to the previous behavior? 
>
> Here are some examples of the malformed from headers we are testing: 
>
> - from_hdr = "\"Mr.J.User <sip:[email protected]>"
> - from_hdr = "\"Mr.J.User\" <sip:j@[email protected]>"
>
> Again, thank you in advanced for your time. 

>From header being mandatory and needed pretty much everywhere on common
sip routing (authentication, authorization, transactions, dialogs, ...),
its parsing was made implicit, as it was done for To header very long
time ago. It was decided to do it for 6.1 series for the safety of the
new feature that allows applying changes based on a core param before
creating the transaction.

However, failing to parse those headers done before config execution
(first via, to, from, ...) should trigger
event_route[core:receive-parse-error] -- is it not executed?

Cheers,
Daniel

-- 
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!