14 Oct
2020
14 Oct
'20
8:13 p.m.
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:
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Funding: https://www.paypal.me/dcmierla
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