Yes, opensips is a bit strict on the message received. Opensips does not try to fix broken messages (just like broken xml, throw fire) as soon as it is not what it should really look like, it will error. More specifically this is what bites you https://github.com/OpenSIPS/opensips/blob/master/parser/parse_fline.c#L1179
Try capturing all data without any filters and look with a hex editor. I don't think this is a bug. Hope this helps. On Sun, Jul 12, 2015 at 1:12 PM, John Nash <john.nash...@gmail.com> wrote: > With one SIP Client opensips logs show me messages like > > ERROR:core:receive_msg: Unable to parse msg received from [XX.XX.XX.XX] > Jul 12 16:41:06 centos opensips[7455]: INFO:core:parse_first_line: method > not followed by SP > Jul 12 16:41:06 centos opensips[7455]: INFO:core:parse_first_line: bad > message > Jul 12 16:41:06 centos opensips[7455]: ERROR:core:parse_msg: > message=<#010g|#016P]*ê#015wh#"<0#002ARiL#034*#177Is#027WZ]b#011#020}i*²Z©C#026+#015#002js#027#024#031zs#031 > ôj#02186;<#021j#026#036}#013WähÈf#0011#031ULFb#025#033ja*±D¬BPkPPM#001%IB]\rîQ$I#027#016s{|#016'mn#017(¾> > > > But when i trace messages from wireshark i see correct SIP messages. > > I am using pike and sipmsg_validate functions. If I disable both I no > longer see error messages? > > where should I check to find out root cause ? > > John > > > > > > _______________________________________________ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -- Aron Podrigal - //Be happy :-)
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users