16 Mar
2022
16 Mar
'22
4:51 p.m.
Just noticed that the previous git push failed for what so ever reason
-- I did it again and now the commit should be in the repo.
Daniel
On 16.03.22 14:47, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
--
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/
I pushed another commit. I tested a few cases:
Which commit was it? I just built latest master and these were the new
commits that git pull found:
pdating d4af130477..dad4431726
Fast-forward
src/core/resolve.c | 2 +-
src/core/socket_info.c | 1 +
src/modules/db_berkeley/km_bdb_val.c | 8 ++++----
src/modules/db_redis/redis_dbase.c | 2 +-
src/modules/db_text/doc/db_text.cfg | 2 +-
Then I run the test and it did not fail:
INFO: OPTIONS <sip:test@test.tutpro.com> from <sip:@192.168.255.95:5062> is
OK
Are you using the same config?
modparam("sanity", "default_checks", 1024)
modparam("sanity", "uri_checks", 3) /* RURI, From */
modparam("sanity", "autodrop", 0)
if (!sanity_check()) {
xnotice("Request from <$var(src_ip)> has invalid syntax\n");
exit;
} else {
xinfo("$rm <$ru> from <$fu> is OK\n");
};
-- Juha