With current master, event_route [xhttp:request] is not run. Instead error message shows up:
Oct 14 20:00:48 lohi /usr/bin/sip-proxy[8820]: ERROR: <core> [core/receive.c:356]: receive_msg(): no via found in request
After spending one hour in trying to figure out, what is wrong in my config, I build K using 5.4 instead of master and the problem disappeared.
So I suspect something is broken in master.
-- Juha
For the moment set core parameter:
sip_parser_mode=0
I will update the code to detect is http and skip strict checking. It is work-in-progress done during the last days when I added also faster flag-based protocol detection...
Cheers, Daniel
On 14.10.20 19:09, Juha Heinanen wrote:
With current master, event_route [xhttp:request] is not run. Instead error message shows up:
Oct 14 20:00:48 lohi /usr/bin/sip-proxy[8820]: ERROR: <core> [core/receive.c:356]: receive_msg(): no via found in request
After spending one hour in trying to figure out, what is wrong in my config, I build K using 5.4 instead of master and the problem disappeared.
So I suspect something is broken in master.
-- Juha
Kamailio (SER) - Development Mailing List sr-dev@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
Actually that error message log is after non-sip msg callback. That part should not be affected by my changes and execution should not get there if xhttp module is properly loaded and configured. Can you check if other error messages are printed? Maybe the regression was introduced with flag-based detection of sip/http protocols...
Cheers, Daniel
On 14.10.20 19:54, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
For the moment set core parameter:
sip_parser_mode=0
Didn't help. Still
Oct 14 20:53:47 lohi /usr/bin/sip-proxy[23198]: ERROR: <core> [core/receive.c:356]: receive_msg(): no via found in request
-- Juha
Daniel-Constantin Mierla writes:
Actually that error message log is after non-sip msg callback. That part should not be affected by my changes and execution should not get there if xhttp module is properly loaded and configured. Can you check if other error messages are printed? Maybe the regression was introduced with flag-based detection of sip/http protocols...
No other error message. I'm using 5.4 for now, so there is no hurry to find a fix.
-- Juha
I looked at the code and indeed there was an issue with the flag-based protocol detection. I pushed a commit to fix it, let me know if works ok now.
Cheers, Daniel
On 14.10.20 20:16, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
Actually that error message log is after non-sip msg callback. That part should not be affected by my changes and execution should not get there if xhttp module is properly loaded and configured. Can you check if other error messages are printed? Maybe the regression was introduced with flag-based detection of sip/http protocols...
No other error message. I'm using 5.4 for now, so there is no hurry to find a fix.
-- Juha
-
Daniel-Constantin Mierla -
Juha Heinanen