The SIP parser was designed on purpose to be loosely in order to be able to fix broken SIP traffic. Without this "feature", making the parser very strict and dropping the traffic, Kamailio won't be that useful. I have been
But there are config functions in textops, siputils, ... or regexp options to be as stricter as you want. Not the author, but the sanity module seems also designed around the format, not the content of the parts, relying mainly on parser. Cheers, Daniel On 15.03.22 16:42, Juha Heinanen wrote: > Daniel-Constantin Mierla writes: > >> Strange! The next log message indicates that it gets to From URI check: >> >> Mar 15 14:58:42 /usr/bin/sip-proxy[3043875]: DEBUG: sanity [sanity.c:776]: >> check_parse_uris(): looking up From header >> >> But for what so ever reason is not triggering a failure, it needs to dig >> in ... > I made another test, this time with From URI sip:^@192.168.255.95:5062 > and that too was accepted, although ^ character is not allowed in > user field: > > INFO: OPTIONS <sip:t...@test.tutpro.com> from <sip:^@192.168.255.95:5062> is > OK > > -- Juha -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Online March 28-31, 2022 (Europe Timezone) * https://www.asipto.com/sw/kamailio-advanced-training-online/ __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
