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. Matteo Cazzola. __________________________________________________________ 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!
