-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kamailio errors: message too short, bad message, bad header field #6
Comments
I am also troubling with same issue with Kamailio service, Please help how to fix the issue. Jan 17 18:47:06 vaglxc01.goautodial.com /usr/sbin/kamailio[17676]: ERROR: [core/parser/msg_parser.c:671]: parse_msg(): ERROR: parse_msg: message= |
Hi there,
Got everything working (awesome stuff!), but some Kamailio errors are cluttering up the messages log when an agent is logged in (websockets based dailer):
call /usr/sbin/kamailio[2766]: INFO: <core> [core/parser/parse_fline.c:87]: parse_first_line(): ERROR: parse_first_line: message too short: 4 call /usr/sbin/kamailio[2766]: ERROR: <core> [core/parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) call /usr/sbin/kamailio[2766]: ERROR: <core> [core/parser/msg_parser.c:671]: parse_msg(): ERROR: parse_msg: message=<PING> call /usr/sbin/kamailio[2766]: ERROR: <core> [core/parser/msg_parser.c:330]: parse_headers(): bad header field [(null)]
It doesn't really seem to influence the functionality, but since it's an "ERROR" it might be good to have it on the issue list.
The text was updated successfully, but these errors were encountered: