[SR-Users] Parser error when enabling siptrace functionality

Asgaroth 00asgaroth00 at gmail.com
Fri Aug 28 15:21:26 CEST 2015


Hi,

Thanks for pointing that out (hep enabled), my module definitions are as 
follows:

modparam("siptrace", "duplicate_uri", HOMER_CAPTURE_NODE)
modparam("siptrace", "hep_version", 2)
modparam("siptrace", "hep_mode_on", 1)
modparam("siptrace", "trace_to_database", 0)
modparam("siptrace", "trace_flag", 22)
modparam("siptrace", "trace_on", 1)
modparam("siptrace", "trace_sl_acks", 1)
modparam("siptrace", "force_send_sock", SIPTRACE_ADDRESS)

I will try to disable HEP mode as I dont have a hep enabled captagent on 
the homer capture node, it is another kamailio instance that writes the 
various goodies back into the database.

Let me try disable hep and see if that corrects the issue, thanks for 
the pointer.



On 28/08/2015 14:17, Daniel-Constantin Mierla wrote:
> Hello,
>
> are you mirroring the sip packets back to you? Because they might be HEP
> and you need sipcapture module to handle that. Iirc, you can have the
> mirroring node and sipcapture node on same kamailio instance.
>
> Anyhow, you can look on the net at port 5060 to see what is received there.
>
> Cheers,
> Daniel
>
> On 28/08/15 14:08, Asgaroth wrote:
>> Hi All,
>>
>> I have a strange issue occuring, when I enable the siptrace
>> functionality within the routing logic, I begin to get a bunch of
>> parser error as show below. Is this normal behaviour or, more than
>> likely, am I doing something wrong?
>>
>> I enable siptrace as follows:
>>
>> request_route {
>>    route("InitialMessageChecks");
>>    sip_trace();
>>    setflag(22);
>>    ...
>> }
>>
>> event_route[tm:local-request] {
>>    sip_trace();
>>    ...
>> }
>>
>> When I enable this functions in the routing logic, I begin to see alot
>> of the following messages in the log file:
>>
>> ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
>> parse_first_line: bad message (offset: 39)
>> ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR:
>> parse_msg: message=<#002#020#002#021® #023ÄÔ#002 ÊÂÕ#035mùLàU{#002>
>> INFO: <core> [parser/parse_fline.c:144]: parse_first_line():
>> ERROR:parse_first_line: method not followed by SP
>> ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
>> parse_first_line: bad message (offset: 0)
>> ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR:
>> parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007>
>> ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
>> parse_first_line: bad message (offset: 39)
>> ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR:
>> parse_msg: message=<#002#020#002#021® #023ÄÔ#002 ÊÂÕ#035mùLàUÞž#002>
>> ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
>> parse_first_line: bad message (offset: 35)
>> ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR:
>> parse_msg: message=<#002#020#002#021® #023ÄÔ#002 ÊÂÕ#035mùLàU #011#003>
>> INFO: <core> [parser/parse_fline.c:144]: parse_first_line():
>> ERROR:parse_first_line: method not followed by SP
>> ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
>> parse_first_line: bad message (offset: 0)
>> ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR:
>> parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007>
>> INFO: <core> [parser/parse_fline.c:144]: parse_first_line():
>> ERROR:parse_first_line: method not followed by SP
>> ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
>> parse_first_line: bad message (offset: 0)
>> ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR:
>> parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007>
>> INFO: <core> [parser/parse_fline.c:144]: parse_first_line():
>> ERROR:parse_first_line: method not followed by SP
>> ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
>> parse_first_line: bad message (offset: 0)
>> ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR:
>> parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007>
>> INFO: <core> [parser/parse_fline.c:144]: parse_first_line():
>> ERROR:parse_first_line: method not followed by SP
>> ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
>> parse_first_line: bad message (offset: 0)
>> ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR:
>> parse_msg: message=<#002#020#002#006y|#023ÄN˜#036ÂÕ#035múLàUű#012>
>> INFO: <core> [parser/parse_fline.c:144]: parse_first_line():
>> ERROR:parse_first_line: method not followed by SP
>> ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
>> parse_first_line: bad message (offset: 0)
>> ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR:
>> parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007>
>> INFO: <core> [parser/parse_fline.c:144]: parse_first_line():
>> ERROR:parse_first_line: method not followed by SP
>> ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
>> parse_first_line: bad message (offset: 0)
>> ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR:
>> parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007>
>> INFO: <core> [parser/parse_fline.c:144]: parse_first_line():
>> ERROR:parse_first_line: method not followed by SP
>> ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
>> parse_first_line: bad message (offset: 0)
>> ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR:
>> parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007>
>> INFO: <core> [parser/parse_fline.c:144]: parse_first_line():
>> ERROR:parse_first_line: method not followed by SP
>> ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
>> parse_first_line: bad message (offset: 0)
>> ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR:
>> parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007>
>> INFO: <core> [parser/parse_fline.c:144]: parse_first_line():
>> ERROR:parse_first_line: method not followed by SP
>> ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
>> parse_first_line: bad message (offset: 0)
>> ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR:
>> parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007>
>> INFO: <core> [parser/parse_fline.c:144]: parse_first_line():
>> ERROR:parse_first_line: method not followed by SP
>> ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
>> parse_first_line: bad message (offset: 0)
>> ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR:
>> parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007>
>> INFO: <core> [parser/parse_fline.c:144]: parse_first_line():
>> ERROR:parse_first_line: method not followed by SP
>> ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
>> parse_first_line: bad message (offset: 0)
>> ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR:
>> parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007>
>>
>> Is there any way I can disable seeing these messages? What are these
>> messages?
>>
>> Any thoughts are appreciated.
>>
>> Thanks
>>
>>
>> _______________________________________________
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users at lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users




More information about the sr-users mailing list