[OpenSIPS-Users] parse_msg errors in the log

[Bogdan-Andrei Iancu]

Happy New Year to you too.

Maybe it is doing default STUN to the SIP server :)

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com


On 01/09/2013 05:55 PM, Филиппов Юрий wrote:
>
> Thank you Bogdan,
>
> Will do it definitely.
>
> Strange thing, the  client I'm using is not configured with STUN 
> settings (All STUN settings are empty) meanwhile the STUN packets are 
> coming in.
>
> Happy New Year!
>
> *From:*Bogdan-Andrei Iancu [mailto:bogdan at opensips.org]
> *Sent:* Tuesday, January 08, 2013 2:18 PM
> *To:* Филиппов Юрий; users at lists.opensips.org
> *Subject:* Re: [OpenSIPS-Users] parse_msg errors in the log
>
> Hi Yury,
>
> Check frame 13 - indeed, you receive some STUN packages on port 5060. 
> The best thing to do is to load the stun module and to configure it to 
> use also ip+5060 as primary listener.
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> http://www.opensips-solutions.com
>
>
> On 12/31/2012 01:11 PM, Филиппов Юрий wrote:
>
> Hello Bogdan-Andrei,
>
> Merry Christmas
>
> and
>
> Happy New  Year!
>
> Thank you very much.
>
> I made the capture and it looks like garbage comes from my client 
> itself. There are STUN requests that comes from my test SIP client. 
> Would you please help me to tell opensips to ignore that frames?
>
> I also see double records in the sip trace window of my opensips 
> server.  Is that normal?
>
> Kind regards,
>
> Yury
>
> *From:*Bogdan-Andrei Iancu [mailto:bogdan at opensips.org]
> *Sent:* Tuesday, December 11, 2012 2:44 PM
> *To:* OpenSIPS users mailling list
> *Cc:* Филиппов Юрий
> *Subject:* Re: [OpenSIPS-Users] parse_msg errors in the log
>
> Hi Yuriy,
>
> By default, OpenSIPS silently discards any UDP packages less than 20 
> bytes.
>
> Looking at the logs you posted, I would say your opensips receives 
> packages longer than 20 bytes and starting with a 0 ASCII byte 
> (probably some binary stuff ?? ); because of that 0 the message is not 
> printed at all (considered a EOS).
>
> Maybe there are some STUN requests or so ? try to make a pcap capture 
> to see if there is some valid but non-SIP traffic or it is garbage.
>
> Regards,
>
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> http://www.opensips-solutions.com
>
>
> On 12/10/2012 10:16 PM, Филиппов Юрий wrote:
>
> Hello,
>
> I have(opensips v.1.8) lots of errors in my opensips.log  like :
>
> INFO:core:parse_first_line: empty or bad first line
>
> INFO:core:parse_first_line: bad message
>
> ERROR:core:parse_msg: message=<>
> ERROR:core:receive_msg: parse_msg failed
>
> Have searched the internet and found an answer:
>
> >>opensips is reading garbage from the network and not even able to 
> parse it a a SIP message
> >>(not recognizing the first line at all), so it cannot trigger the error
> >>route - the error route is trigger for malformed SIP messages.
>
> Is there any way to eliminate that Error records in the log?
>
> Thanks
>
> Yuriy
>
>   
>   
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org  <mailto:Users at lists.opensips.org>
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20130109/fbb55121/attachment.htm>