<div dir="ltr">Re: Contents of asterisk-dev digest...</div><div class="gmail_extra"><br><div class="gmail_quote">2017-02-22 1:00 GMT+07:00 <span dir="ltr"><<a href="mailto:asterisk-dev-request@lists.digium.com" target="_blank">asterisk-dev-request@lists.digium.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send asterisk-dev mailing list submissions to<br>
<a href="mailto:asterisk-dev@lists.digium.com">asterisk-dev@lists.digium.com</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" rel="noreferrer" target="_blank">http://lists.digium.com/<wbr>mailman/listinfo/asterisk-dev</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:asterisk-dev-request@lists.digium.com">asterisk-dev-request@lists.<wbr>digium.com</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:asterisk-dev-owner@lists.digium.com">asterisk-dev-owner@lists.<wbr>digium.com</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of asterisk-dev digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. from <a href="mailto:sandeep.ananthula@gmail.com">sandeep.ananthula@gmail.com</a> (sandeep.ananthula)<br>
2. crashes when bridging opus channels (Moritz Maisel)<br>
3. Re: crashes when bridging opus channels (Joshua Colp)<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>----------<br>
<br>
Message: 1<br>
Date: Mon, 20 Feb 2017 10:27:03 -0800<br>
From: sandeep.ananthula <<a href="mailto:sandeep.ananthula@gmail.com">sandeep.ananthula@gmail.com</a>><br>
To: "Matt Jordan" <<a href="mailto:mjordan@digium.com">mjordan@digium.com</a>>, "wdoekes"<br>
<<a href="mailto:reviewboard@asterisk.org">reviewboard@asterisk.org</a>>, "Asterisk Developers"<br>
<<a href="mailto:asterisk-dev@lists.digium.com">asterisk-dev@lists.digium.com</a><wbr>>, "SANDEEP ANANTHULA"<br>
<<a href="mailto:SANDEEP.ANANTHULA@GMAIL.COM">SANDEEP.ANANTHULA@GMAIL.COM</a>>, "Santhosh Kumar"<br>
<<a href="mailto:dsanthosh38@gmail.com">dsanthosh38@gmail.com</a>><br>
Subject: [asterisk-dev] from <a href="mailto:sandeep.ananthula@gmail.com">sandeep.ananthula@gmail.com</a><br>
Message-ID: <94cc1f17a91b$306779f7$<wbr>ec8eb338$@<a href="http://gmail.com" rel="noreferrer" target="_blank">gmail.com</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Hi!<br>
<br>
Have you already seen it? <a href="http://goryla.info.pl/aklgcbq.php?sandeep_ananthula_gmail_com" rel="noreferrer" target="_blank">http://goryla.info.pl/aklgcbq.<wbr>php?sandeep_ananthula_gmail_<wbr>com</a><br>
<br>
<br>
<br>
<br>
<br>
<a href="mailto:sandeep.ananthula@gmail.com">sandeep.ananthula@gmail.com</a><br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.digium.com/pipermail/asterisk-dev/attachments/20170220/6859f4d5/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.digium.com/<wbr>pipermail/asterisk-dev/<wbr>attachments/20170220/6859f4d5/<wbr>attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 21 Feb 2017 17:13:27 +0100<br>
From: Moritz Maisel <<a href="mailto:maisel@sipgate.de">maisel@sipgate.de</a>><br>
To: asterisk-dev <<a href="mailto:asterisk-dev@lists.digium.com">asterisk-dev@lists.digium.com</a><wbr>><br>
Subject: [asterisk-dev] crashes when bridging opus channels<br>
Message-ID:<br>
<CANgsjSAUxT+G_avOYRaZdOM9G1=<wbr>Mtqoa=<a href="mailto:xdEB55YOYtKeR%2BdbQ@mail.gmail.com">xdEB55YOYtKeR+dbQ@mail.<wbr>gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi,<br>
<br>
we experience reproducable crashes of asterisk with codec_opus. While<br>
asterisks successfully processes a couple of calls (about 8-10) when<br>
bridging two OPUS/48000/2 channels before it crashes, it reproducably<br>
crashes on the first call bridging PCMA/8000 to OPUS/48000/2.<br>
<br>
The setup is asterisk 14.3.0 with bundled pjsip and<br>
codec_opus-14.0_1.1.0-x86_64. The environment is debian 8.7 on amd64<br>
architecture with kernel version 3.16.0-4-amd64.<br>
<br>
To reduce traffic on the list, I only append parts of the backtrace as well<br>
as the last lines of log output below. I appreciate any suggestions for<br>
debugging this scenario. I'm a bit lost, as the backtrace points into the<br>
codec_opus.so binary blob. Is it recommended to open an issue in the<br>
bugtracker or should we first provide more information on the list?<br>
<br>
Kind regards,<br>
Moritz<br>
<br>
---------- CLI output --- BEGIN ----------<br>
-- Called PJSIP/sipgate/<a href="mailto:sip%3A2483816e2@sipgate.de">sip:2483816e2@<wbr>sipgate.de</a><br>
-- PJSIP/sipgate-00000003 is ringing<br>
-- PJSIP/sipgate-00000003 is ringing<br>
-- PJSIP/sipgate-00000003 answered PJSIP/proxy-00000002<br>
-- Channel PJSIP/sipgate-00000003 joined 'simple_bridge' basic-bridge<br>
<d58089f3-c996-4fc7-9678-<wbr>0fd124b1389e><br>
-- Channel PJSIP/proxy-00000002 joined 'simple_bridge' basic-bridge<br>
<d58089f3-c996-4fc7-9678-<wbr>0fd124b1389e><br>
> 0x7f1c200257f0 -- Probation passed - setting RTP source address to<br>
<a href="http://217.10.77.244:26918" rel="noreferrer" target="_blank">217.10.77.244:26918</a><br>
---------- CLI output --- END ----------<br>
<br>
---------- backtrace --- BEGIN ----------<br>
Thread 1 (Thread 0x7f60fe49f700 (LWP 27298)):<br>
#0 0x00007f6147ad1952 in ?? () from /usr/lib/asterisk/modules/<wbr>codec_opus.so<br>
#1 0x00007f6147ac5f26 in ?? () from /usr/lib/asterisk/modules/<wbr>codec_opus.so<br>
#2 0x00000000005f436e in ast_translate ()<br>
#3 0x00000000004bf15c in ast_write ()<br>
#4 0x0000000000483553 in bridge_channel_internal_join ()<br>
#5 0x000000000046d49e in ?? ()<br>
#6 0x00000000005fa32a in ?? ()<br>
#7 0x00007f615df57064 in start_thread () from<br>
/lib/x86_64-linux-gnu/<wbr>libpthread.so.0<br>
#8 0x00007f615d00662d in clone () from /lib/x86_64-linux-gnu/libc.so.<wbr>6<br>
---------- backtrace --- END ----------<br>
<br>
--<br>
sipgate GmbH - Gladbacher Str. 74 - 40219 D?sseldorf<br>
HRB D?sseldorf 39841 - Gesch?ftsf?hrer: Thilo Salmon, Tim Mois<br>
Steuernummer: 106/5724/7147, Umsatzsteuer-ID: DE219349391<br>
<br>
<a href="http://www.sipgate.de" rel="noreferrer" target="_blank">www.sipgate.de</a> - <a href="http://www.sipgate.co.uk" rel="noreferrer" target="_blank">www.sipgate.co.uk</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.digium.com/pipermail/asterisk-dev/attachments/20170221/78e24956/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.digium.com/<wbr>pipermail/asterisk-dev/<wbr>attachments/20170221/78e24956/<wbr>attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 21 Feb 2017 12:23:37 -0400<br>
From: Joshua Colp <<a href="mailto:jcolp@digium.com">jcolp@digium.com</a>><br>
To: <a href="mailto:asterisk-dev@lists.digium.com">asterisk-dev@lists.digium.com</a><br>
Subject: Re: [asterisk-dev] crashes when bridging opus channels<br>
Message-ID:<br>
<<a href="mailto:1487694217.1825127.888139120.6B5D543B@webmail.messagingengine.com">1487694217.1825127.888139120.<wbr>6B5D543B@webmail.<wbr>messagingengine.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
On Tue, Feb 21, 2017, at 12:13 PM, Moritz Maisel wrote:<br>
> Hi,<br>
><br>
> we experience reproducable crashes of asterisk with codec_opus. While<br>
> asterisks successfully processes a couple of calls (about 8-10) when<br>
> bridging two OPUS/48000/2 channels before it crashes, it reproducably<br>
> crashes on the first call bridging PCMA/8000 to OPUS/48000/2.<br>
><br>
> The setup is asterisk 14.3.0 with bundled pjsip and<br>
> codec_opus-14.0_1.1.0-x86_64. The environment is debian 8.7 on amd64<br>
> architecture with kernel version 3.16.0-4-amd64.<br>
><br>
> To reduce traffic on the list, I only append parts of the backtrace as<br>
> well<br>
> as the last lines of log output below. I appreciate any suggestions for<br>
> debugging this scenario. I'm a bit lost, as the backtrace points into the<br>
> codec_opus.so binary blob. Is it recommended to open an issue in the<br>
> bugtracker or should we first provide more information on the list?<br>
<br>
Please file an issue on the issue tracker[1] and use codec_opus as the<br>
component. We'll triage and ask for the needed information there.<br>
<br>
[1] <a href="https://issues.asterisk.org/jira" rel="noreferrer" target="_blank">https://issues.asterisk.org/<wbr>jira</a><br>
<br>
--<br>
Joshua Colp<br>
Digium, Inc. | Senior Software Developer<br>
445 Jan Davis Drive NW - Huntsville, AL 35806 - US<br>
Check us out at: <a href="http://www.digium.com" rel="noreferrer" target="_blank">www.digium.com</a> & <a href="http://www.asterisk.org" rel="noreferrer" target="_blank">www.asterisk.org</a><br>
<br>
<br>
<br>
------------------------------<br>
<br>
______________________________<wbr>_________________<br>
--Bandwidth and Colocation Provided by <a href="http://www.api-digital.com--" rel="noreferrer" target="_blank">http://www.api-digital.com--</a><br>
<br>
asterisk-dev mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" rel="noreferrer" target="_blank">http://lists.digium.com/<wbr>mailman/listinfo/asterisk-dev</a><br>
<br>
End of asterisk-dev Digest, Vol 151, Issue 14<br>
******************************<wbr>***************<br>
</blockquote></div><br></div>