From bugtracker@sip-router.org Thu May 15 11:59:56 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: Thu, 15 May 2014 09:59:54 +0000
Message-ID: <1400147994.5374901a3d0df@sip-router.org>
In-Reply-To: <FS427@sip-router.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1733261266=="

--===============1733261266==
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)

----------
And another two from today ;-) I'm considering going back to 3.3.7 :|

<code>
May 15 09:20:29 node02 /usr/sbin/kamailio[23033]: NOTICE: <script>: LOG:32721=
2a84c5feaf4601b031370034781(a)sip.vanbergsystems.pl (route main) Method: ACK =
Message: ACK sip:centranet2(a)192.168.0.11:1027 SIP/2.0  Via: SIP/2.0/UDP 213=
.218.108.142;branch=3Dz9hG4bK0aaf.0ddf844dfed8727ec99275dc65ccf088.0  Route: =
<sip:213.218.108.141;lr;received=3Dsip:79.184.45.133:1027>  To: <sip:06141551=
23(a)sip.vanbergsystems.pl>;tag=3D878aec3d33cad2a0f77a7a21e24411cb-75d6  From=
: "+48784054101" <sip:784054101(a)sip.vanbergsystems.pl>;tag=3Das01ee9649  Ca=
ll-ID: 327212a84c5feaf4601b031370034781(a)sip.vanbergsystems.pl  CSeq: 102 AC=
K  Max-Forwards:  8  Content-Length: 0
May 15 09:20:29 node02 /usr/sbin/kamailio[23033]: CRITICAL: dialog [dlg_hash.=
c:841]: log_next_state_dlg(): bogus event 6 in state 1 for dlg 0xa5200c58 [30=
26:4532] with clid '327212a84c5feaf4601b031370034781(a)sip.vanbergsystems.pl'=
 and tags 'as01ee9649' ''
</code>

<code>
May 15 09:22:20 node03 /usr/sbin/kamailio[9462]: NOTICE: <script>: LOG:301fb8=
cd03fb56753bb4bae44bd2e3c0(a)sip.siptrunking.pl (route main) Method: ACK Mess=
age: 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=3Dz9hG4bK7972.61ff154a2f1859ee1d86=
f8ffc6c46302.0  Route: <sip:213.218.108.142;lr;received=3Dsip:212.180.155.5:5=
080>  To: <sip:224582719(a)sip.siptrunking.pl>;tag=3Dp7e6957ZtcKBp  From: "+4=
8228345260" <sip:228345260(a)sip.siptrunking.pl>;tag=3Das360a0b5b  Call-ID: 3=
01fb8cd03fb56753bb4bae44bd2e3c0(a)sip.siptrunking.pl  CSeq: 102 ACK  Max-Forw=
ards:  8  Content-Length: 0
May 15 09:22:20 node03 /usr/sbin/kamailio[9462]: CRITICAL: dialog [dlg_hash.c=
:841]: log_next_state_dlg(): bogus event 6 in state 1 for dlg 0xa4fb2890 [224=
8:12181] with clid '301fb8cd03fb56753bb4bae44bd2e3c0(a)sip.siptrunking.pl' an=
d tags 'as360a0b5b' ''
</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#comment1449

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.


--===============1733261266==--