hi daniel,
Hello,
are you using the latest git version of branch kamailio_3.0? It was a fix to dialog after the 3.0.0 release, adding some sanity checks for broken messages:
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=787fabb1e0085355aa1eeb77d5f17e7940f4ed3c
On the other hand, I see you got a core dump file:
Apr 21 10:19:57 kamvm-1 /usr/local/sbin/kamailio[28507]: ALERT: <core> [main.c:722]: child process 28511 exited by a signal 11Locate the core file and sent the backtrace. The core is either in root '/' folder or in working directory (if you provided by -w parameter).
Apr 21 10:19:57 kamvm-1 /usr/local/sbin/kamailio[28507]: ALERT: <core> [main.c:725]: core was generated
Use the gdb:
gdb /path/to/kamailio core_file
then do bt and send here.
Thanks,
Daniel
On 4/21/10 11:38 AM, Kelvin Chua wrote:_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing listok, i'll enable debug for now.but if it's indeed a buggy UA, the dialog module should not have crashedbut instead dropped the dialog/session and moved on, something i thinkwe need to address to be more resilient.
i hope i catch the culprit when this happens again.
Kelvin Chua
On Wed, Apr 21, 2010 at 5:33 PM, Iñaki Baz Castillo <ibc@aliax.net> wrote:
2010/4/21 Kelvin Chua <kelchy@gmail.com>:> i wonder if anybody from list is also experiencing this?
Perhaps in your case you have a buggy UA setting an invalid Contact
header and it causes Kamailio to crash, maybe the reason others have
not detected same issue.
Could you get some SIP traces until the problem occurs again?
or perhaps could you enable the debug?
--
--
Daniel-Constantin Mierla * http://www.asipto.com/ * http://twitter.com/miconda * http://www.linkedin.com/in/danielconstantinmierla