<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<tt>Hi Marcos,<br>
<br>
Kamailio v5.1.7 will be available in the following upcoming
releases: mr6.5.4, mr7.0.2, mr7.1.2, mr7.2.1<br>
<br>
<br>
Regards<br>
Marco<br>
</tt><br>
<div class="moz-cite-prefix">On 2/5/19 1:09 PM, Marcos Pytel wrote:<br>
</div>
<blockquote type="cite"
cite="mid:011801d4bd4b$a7a7b5d0$f6f72170$@cotesma.com.ar">
<pre class="moz-quote-pre" wrap="">Hi Andrew!
The versión mr7.1.1 already have Kamailio v5.1.7?
Thank you!
-----Mensaje original-----
De: Andrew Pogrebennyk <a class="moz-txt-link-rfc2396E" href="mailto:apogrebennyk@sipwise.com"><apogrebennyk@sipwise.com></a>
Enviado el: martes 5 de febrero del 2019 05:34
Para: Marcos Pytel <a class="moz-txt-link-rfc2396E" href="mailto:marcos.pytel@cotesma.com.ar"><marcos.pytel@cotesma.com.ar></a>; <a class="moz-txt-link-abbreviated" href="mailto:spce-user@lists.sipwise.com">spce-user@lists.sipwise.com</a>
CC: Marco Capetta <a class="moz-txt-link-rfc2396E" href="mailto:mcapetta@sipwise.com"><mcapetta@sipwise.com></a>
Asunto: Re: [Spce-user] TOPOS error
Hi,
I think that this could be same issue or related to
<a class="moz-txt-link-freetext" href="https://github.com/kamailio/kamailio/issues/1784">https://github.com/kamailio/kamailio/issues/1784</a>
This will be fixed in v5.1.7. We are planning to upgrade mr6.5 LTS once it passes all tests.
BR, Andrew
On 2/4/19 5:02 PM, Marcos Pytel wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Thank you for your reply! It's very strange.
Marcos.
-----Mensaje original-----
De: Andrew Pogrebennyk <a class="moz-txt-link-rfc2396E" href="mailto:apogrebennyk@sipwise.com"><apogrebennyk@sipwise.com></a> Enviado el: lunes 4
de febrero del 2019 12:56
Para: Marcos Pytel <a class="moz-txt-link-rfc2396E" href="mailto:marcos.pytel@cotesma.com.ar"><marcos.pytel@cotesma.com.ar></a>;
<a class="moz-txt-link-abbreviated" href="mailto:spce-user@lists.sipwise.com">spce-user@lists.sipwise.com</a>
Asunto: Re: [Spce-user] TOPOS error
Hi,
that doesn't ring the bell, but we are preparing to update kamailio to latest build v5.1.7, which includes fixes for some topos-related crashes/bugs, so i would suggest you to upgrade and if that doesn't solve the issue we can probably raise this request with the upstream.
Regards,
Andrew
On 2/4/19 4:51 PM, Marcos Pytel wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Hi all!
I'm still with this problem. Any clue to fix it?
Program terminated with signal SIGABRT, Aborted.
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) backtrace
#0 __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:51
#1 0x00007f66d5aab42a in __GI_abort () at abort.c:89
#2 0x00007f66d5ae7c00 in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f66d5bdb305 "*** %s ***: %s terminated\n")
at ../sysdeps/posix/libc_fatal.c:175
#3 0x00007f66d5b701f7 in __GI___fortify_fail
(msg=msg@entry=0x7f66d5bdb29c "buffer overflow detected") at
fortify_fail.c:30
#4 0x00007f66d5b6e330 in __GI___chk_fail () at chk_fail.c:28
#5 0x00007f66b867e097 in memcpy (__len=<optimized out>, __src=<optimized out>, __dest=0x7f66b8892524 <_tps_redis_cbuf+4>)
at /usr/include/x86_64-linux-gnu/bits/string3.h:53
#6 tps_redis_load_branch (msg=<optimized out>, md=<optimized out>,
sd=0x7ffed3993d30, mode=<optimized out>) at topos_redis_storage.c:744
#7 0x00007f66b88b35c0 in tps_request_received
(msg=msg@entry=0x7ffed3995f80, dialog=dialog@entry=1) at
tps_msg.c:786
#8 0x00007f66b88b9255 in tps_msg_received (evp=<optimized out>) at
topos_mod.c:332
#9 0x000055e1dc07da88 in sr_event_exec (type=<optimized out>,
evp=<optimized out>) at core/events.c:211
#10 0x000055e1dc0415f5 in receive_msg (
buf=buf@entry=0x55e1dc511d40 <buf> "BYE
<a class="moz-txt-link-abbreviated" href="mailto:sip:atpsh-5c4b0f6e-25b2-9@10.10.10.2">sip:atpsh-5c4b0f6e-25b2-9@10.10.10.2</a> SIP/2.0\r\nVia: SIP/2.0/UDP
10.10.10.1:5060;branch=z9hG4bK898122669\r\nFrom:
<a class="moz-txt-link-rfc2396E" href="mailto:sip:2972426338@10.10.10.1"><sip:2972426338@10.10.10.1></a>;tag=3296734298\r\nTo:
<a class="moz-txt-link-rfc2396E" href="mailto:sip:414533@10.10.10.2"><sip:414533@10.10.10.2></a>;tag=03D2CCF0-5"..., len=381,
rcv_info=rcv_info@entry=0x7ffed3996980) at core/receive.c:157
#11 0x000055e1dbf5e6e3 in udp_rcv_loop () at core/udp_server.c:554
#12 0x000055e1dbef3a9f in main_loop () at main.c:1619
#13 0x000055e1dbeea8cb in main (argc=<optimized out>,
argv=0x7ffed3996f38) at main.c:2638
Thanks,
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<div style="line-height:16px; margin:6px 0; padding:8px 8px 8px
8px; border-top:1px #aeb1a6 dotted; border-bottom:1px #aeb1a6
dotted; font-family: 'Lucida Sans', Lucida Grande, Verdana,
Arial, Sans-Serif; font-size:11px; color:#555555;"> <strong
style="color:#333333; text-transform:uppercase;
font-size:10px;"> Marco Capetta </strong> <br>
Operations Engineer
<p> <a href="http://www.sipwise.com" style="color:rgb(0, 136,
204) !important; text-decoration:none !important;
border-bottom:1px dotted #AAA;"> Sipwise GmbH </a> , Campus
21/Europaring F15<br>
AT-2345 Brunn am Gebirge </p>
<p> Phone: <a href="tel:+4313012044" style="color:rgb(0, 136,
204) !important; text-decoration:none !important;
border-bottom:1px dotted #AAA;"> +43(0)1 301 2044 </a> <br>
Email: <a href="mailto:mcapetta@sipwise.com"
style="color:rgb(0, 136, 204) !important;
text-decoration:none !important; border-bottom:1px dotted
#AAA;"> mcapetta@sipwise.com </a> <br>
Website: <a href="http://www.sipwise.com"
style="color:rgb(0, 136, 204) !important;
text-decoration:none !important; border-bottom:1px dotted
#AAA;"> www.sipwise.com </a> </p>
<p>
Particulars according Austrian Companies Code paragraph 14<br>
"Sipwise GmbH" - Europaring F15 - 2345 Brunn am Gebirge<br>
FN:305595f, Commercial Court Vienna, ATU64002206
</p>
</div>
</div>
</body>
</html>