From bugtracker@sip-router.org Sun May 18 21:41:54 2014
From: sip-router <bugtracker@sip-router.org>
To: sr-dev@lists.kamailio.org
Subject: [sr-dev] [tracker] Comment added: kamailio sometimes crash when
	handling failure events (Attachment added)
Date: Sun, 18 May 2014 19:41:52 +0000
Message-ID: <1400442112.53790d006ac39@sip-router.org>
In-Reply-To: <FS427@sip-router.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2128749734=="

--===============2128749734==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#427 - kamailio sometimes crash when handling failure events
User who did this - Pawel Sternal (Sternik)

----------
Today's crash.=20

<code>
May 18 14:52:28 node03 /usr/sbin/kamailio[30493]: NOTICE: <script>: LOG:7655c=
d4b0ec44f177a587dbe407ceeff(a)sip.siptrunking.pl (failure route 1) Method: IN=
VITE 486=20

May 18 14:52:28 node03 /usr/sbin/kamailio[30493]: NOTICE: <script>: LOG (fail=
ure route 1) Message: INVITE sip:+48228224631(a)sip.siptrunking.pl SIP/2.0  R=
ecord-Route: <sip:213.218.125.68:5060;ftag=3Das3b1a4879;lr>  Via: SIP/2.0/UDP=
 213.218.125.68:5060;branch=3Dz9hG4bK8afa.ce3598c6.0  Via: SIP/2.0/UDP 213.21=
8.125.68:5061;received=3D127.0.0.1;branch=3Dz9hG4bK7054260c;rport=3D5061  Fro=
m: "+48226319604" <sip:+48226319604(a)sip.siptrunking.pl>;tag=3Das3b1a4879  T=
o: <sip:+48228224631(a)sip.siptrunking.pl>  Contact: <sip:+48226319604(a)213.=
218.125.68:5061>  Call-ID: 7655cd4b0ec44f177a587dbe407ceeff(a)sip.siptrunking=
.pl  CSeq: 102 INVITE  User-Agent: FreecoNet gxgt3 _FCN_MP0  Max-Forwards: 10=
  Date: Sun, 18 May 2014 14:52:28 GMT  Allow: INVITE, ACK, CANCEL, OPTIONS, B=
YE, REFER, SUBSCRIBE, NOTIFY, INFO  Supported: replaces  X-ROUTE: 207  Conten=
t-Type: application/sdp  Content-Length: 394    v=3D0  o=3Droot 7321 7321 IN =
IP4 213.218.125.68  s=3Dsession  c=3DIN IP4 213.218.125.68  t=3D0 0  m=3Daudi=
o 19720 RTP/AVP 8 18 2 112 3 0 101  a=3Drtpmap:8 PCMA/8000  a=3Drtpmap:18 G72=
9/8000  a=3Dfmtp:18 annexb=3Dno  a=3Drtpmap:2 G726-32/8000  a=3Drtpmap:112 G7=
26-32/8000  a=3Drtpmap:3 GSM/8000  a=3Drtpmap:0 PCMU/8000  a=3Drtpmap:101 tel=
ephone-event/8000  a=3Dfmtp:101 0-16  a=3DsilenceSupp:off - - - -  a=3Dptime:=
20  a=3Dsendrecv

May 18 14:52:28 node03 /usr/sbin/kamailio[30481]: NOTICE: <script>: LOG:7655c=
d4b0ec44f177a587dbe407ceeff(a)sip.siptrunking.pl (route main) Method: ACK Mes=
sage: ACK sip:supermedia(a)212.180.155.5:5080;transport=3Dudp;gw=3D1075 SIP/2=
.0  Via: SIP/2.0/UDP 213.218.108.141;branch=3Dz9hG4bK8afa.9afea3f193bb2781c3c=
b10fa01dbaeb9.0  Route: <sip:213.218.108.142;lr;received=3Dsip:212.180.155.5:=
5080>  To: <sip:228224631(a)sip.siptrunking.pl>;tag=3D4SvcaHBmj21Ng  From: "+=
48226319604" <sip:226319604(a)sip.siptrunking.pl>;tag=3Das3b1a4879  Call-ID: =
7655cd4b0ec44f177a587dbe407ceeff(a)sip.siptrunking.pl  CSeq: 102 ACK  Max-For=
wards:  8  Content-Length: 0

May 18 14:52:28 node03 /usr/sbin/kamailio[30481]: CRITICAL: dialog [dlg_hash.=
c:842]: log_next_state_dlg(): bogus event 6 in state 1 for dlg 0xa4d3e348 [21=
7:2951] with clid '7655cd4b0ec44f177a587dbe407ceeff(a)sip.siptrunking.pl' and=
 tags 'as3b1a4879' ''

May 18 14:52:28 node03 /usr/sbin/kamailio[30481]: NOTICE: <script>: LOG:7655c=
d4b0ec44f177a587dbe407ceeff(a)sip.siptrunking.pl (route ACK) Method: ACK Dest=
ination URI: sip:212.180.155.5:5080 Destination set: <null>

May 18 14:52:28 node03 /usr/sbin/kamailio[30493]: ERROR: dialog [dlg_hash.c:7=
95]: dlg_ref(): info - dlg 0xa4d3e348 ref from 0 with 1
May 18 14:53:14 node03 /usr/sbin/kamailio[30476]: ALERT: <core> [main.c:775]:=
 handle_sigs(): child process 30493 exited by a signal 11
May 18 14:53:14 node03 /usr/sbin/kamailio[30476]: ALERT: <core> [main.c:778]:=
 handle_sigs(): core was generated
</code>
----------

One or more files have been attached.

More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=3Ddetails&task_id=3D427#comment1461

You are receiving this message because you have requested it from the Flyspra=
y bugtracking system.  If you did not expect this message or don't want to re=
ceive mails in future, you can change your notification settings at the URL s=
hown above.


--===============2128749734==--