[OpenSIPS-Users] Opensips Errors

[Rodrigo Ferreira]

[Solved]

I found the problem, i have a few Grandstream ATA, and those empty SIP messages were coming from them. I change a NAT Traversal configuration on them and everything is working fine now.

From: Rodrigo Ferreira 
Sent: Tuesday, June 19, 2012 5:54 PM
To: users at lists.opensips.org 
Subject: Re: [OpenSIPS-Users] Opensips Errors

I did the patch, but the file is too big to attach it here ..

From: Vlad Paiu 
Sent: Wednesday, June 13, 2012 9:13 AM
To: users at lists.opensips.org 
Subject: Re: [OpenSIPS-Users] Opensips Errors

Hello,

On second thought, there might be something strange here. Received messages shorter that 20 bytes should be discarded automatically, and never tried to be parsed.

What protocol are you using to receive SIP traffic ?
Can you please apply the attached patch here, and return with the OpenSIPS full debug log ?


Regards,

Vlad Paiu
OpenSIPS Developer
http://www.opensips-solutions.com 
On 06/12/2012 12:24 PM, Vlad Paiu wrote: 
  Hello,

  It seems your server has received an empty SIP message, and obviously parsing has failed on it :)
  Nothing to worry about.

  Regards,

Vlad Paiu
OpenSIPS Developer
http://www.opensips-solutions.com 
  On 06/11/2012 10:33 PM, Rodrigo Ferreira wrote: 
    Hey guys,

    I’m getting a lot of those messages on my Opensips.

    Jun 11 16:26:22 caos /sbin/opensips[15028]: ERROR:core:parse_msg: message=<>
    Jun 11 16:26:22 caos /sbin/opensips[15028]: ERROR:core:receive_msg: parse_msg failed
    Jun 11 16:26:30 caos /sbin/opensips[15024]: INFO:core:parse_first_line: method not followed by SP
    Jun 11 16:26:30 caos /sbin/opensips[15024]: INFO:core:parse_first_line: bad message
    Jun 11 16:26:30 caos /sbin/opensips[15024]: ERROR:core:parse_msg: message=<>
    Jun 11 16:26:30 caos /sbin/opensips[15024]: ERROR:core:receive_msg: parse_msg failed
    Jun 11 16:26:30 caos /sbin/opensips[15027]: INFO:core:parse_first_line: empty  or bad first line
    Jun 11 16:26:30 caos /sbin/opensips[15027]: INFO:core:parse_first_line: bad message
    Jun 11 16:26:30 caos /sbin/opensips[15027]: ERROR:core:parse_msg: message=<>
    Jun 11 16:26:30 caos /sbin/opensips[15027]: ERROR:core:receive_msg: parse_msg failed
    Jun 11 16:26:42 caos /sbin/opensips[15027]: INFO:core:parse_first_line: empty  or bad first line
    Jun 11 16:26:42 caos /sbin/opensips[15027]: INFO:core:parse_first_line: bad message
    Jun 11 16:26:42 caos /sbin/opensips[15027]: ERROR:core:parse_msg: message=<>
    Jun 11 16:26:42 caos /sbin/opensips[15027]: ERROR:core:receive_msg: parse_msg failed

    anyone know what this means?


    Thanks.

_______________________________________________
Users mailing list
Users at lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
Users at lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


--------------------------------------------------------------------------------
_______________________________________________
Users mailing list
Users at lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



--------------------------------------------------------------------------------

Nenhum vírus encontrado nessa mensagem.
Verificado por AVG - www.avgbrasil.com.br
Versão: 2012.0.2177 / Banco de dados de vírus: 2433/5064 - Data de Lançamento: 06/12/12



--------------------------------------------------------------------------------
_______________________________________________
Users mailing list
Users at lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



--------------------------------------------------------------------------------

Nenhum vírus encontrado nessa mensagem.
Verificado por AVG - www.avgbrasil.com.br
Versão: 2012.0.2179 / Banco de dados de vírus: 2437/5079 - Data de Lançamento: 06/19/12
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20120622/d5c6c294/attachment.htm>