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