<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Asterisk --> segfault-->]]></title><description><![CDATA[<h2>I followed these instructions :</h2>
<p dir="auto">/etc/asterisk/sip.conf</p>
<p dir="auto">callevents=yes</p>
<h2>It will send hold/unhold events to FOP2.</h2>
<p dir="auto">This caused Asterisk to segfault.</p>
<p dir="auto">I removed the 'callevents=yes' from sip.conf, and no segfaults.</p>
<p dir="auto">I am running :</p>
<pre><code>        PBX in a Flash Version 1.2 Daemon Status                
</code></pre>
<hr />
<ul>
<li>Asterisk  * ONLINE  * Zaptel    * ONLINE  * MySQL      * ONLINE  *</li>
<li>SSH       * ONLINE  * Apache    * ONLINE  * Iptables   * ONLINE  *</li>
<li>Fail2ban  * ONLINE  * IP Connect* ONLINE  * Ip6tables  * ONLINE  *</li>
<li>BlueTooth * ONLINE  * Hidd      * ONLINE  * NTPD       * OFFLINE *</li>
<li>Sendmail  * ONLINE  * Samba     * OFFLINE * Webmin     * ONLINE  *</li>
<li>Ethernet0 * ONLINE  * Ethernet1 *   N/A   * Wlan0      *   N/A   *</li>
</ul>
<hr />
<ul>
<li>Running Asterisk Version : Asterisk 1.4.21.2</li>
<li>Asterisk Source Version  : 1.4.21.2</li>
<li>Zaptel Source Version    : 1.4.12.1</li>
<li>Libpri Source Version    : 1.4.7</li>
<li>Addons Source Version    : 1.4.7</li>
</ul>
<hr />
<p dir="auto">pbx.local on 192.168.6.159 - eth0<br />
CentOS release 5.2 (Final) :64 Bit Kernel: 2.6.18-92.1.10.el5</p>
<hr />
<p dir="auto">Need any additional info?</p>
]]></description><link>http://localhost:4567/topic/10/asterisk-segfault</link><generator>RSS for Node</generator><lastBuildDate>Tue, 27 Oct 2026 04:39:16 GMT</lastBuildDate><atom:link href="http://localhost:4567/topic/10.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 01 Jul 2009 14:22:31 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Asterisk --> segfault--> on Wed, 01 Jul 2009 21:17:51 GMT]]></title><description><![CDATA[<p dir="auto">If its asterisk segfaulting, then you will have to follow their guidelines to submit the issue to their bugtracking system. What I can recommend is to test with a more recent asterisk version that might have already fixed that segfault.</p>
<p dir="auto">If the segfault is in fop2_server, then I would need to see the error when it crashes. You can start fop2_server from command line instead of an init script to watch for the error.</p>
<p dir="auto">Best regards,</p>
<p dir="auto">--<br />
Nicolás</p>
]]></description><link>http://localhost:4567/post/61</link><guid isPermaLink="true">http://localhost:4567/post/61</guid><dc:creator><![CDATA[nicolas]]></dc:creator><pubDate>Wed, 01 Jul 2009 21:17:51 GMT</pubDate></item><item><title><![CDATA[Reply to Asterisk --> segfault--> on Wed, 01 Jul 2009 17:11:45 GMT]]></title><description><![CDATA[<blockquote>
<p dir="auto">Hi,</p>
<p dir="auto">If asterisk is segfaulting because of callevents in sip.conf, then turn it off.. you will loose hold status on fop, but the pbx will be stable  <img src="http://localhost:4567/assets/plugins/nodebb-plugin-emoji/emoji/android/1f642.png?v=9c14fadbfa0" class="not-responsive emoji emoji-android emoji--slightly_smiling_face" style="height:1.4em;width:auto;vertical-align:middle" title=":)" alt="🙂" /></p>
<p dir="auto">Now, I have not seen any segfault due to that sip option. What asterisk version are you running? Maybe updating asterisk will fix the issue...</p>
<p dir="auto">Best regards,</p>
</blockquote>
<p dir="auto">I am running Asterisk 1.4.21.2</p>
<p dir="auto">I'll test it a bit more this evening.  I am running this as a VM with ESXi 3.5u4, but that shouldn't really matter.</p>
<p dir="auto">Before I installed FOP2, I just made a snapshot, to make it easier for testing, adding, and removing, etc. Plus, when it gets late at night, I can just move back and forth between the images quickly.</p>
<p dir="auto">If I redo this, test, and get the segfaults, are there any logs you want, or any debugging you would like me to enable?  Just trying to help out...</p>
]]></description><link>http://localhost:4567/post/60</link><guid isPermaLink="true">http://localhost:4567/post/60</guid><dc:creator><![CDATA[rapidnet]]></dc:creator><pubDate>Wed, 01 Jul 2009 17:11:45 GMT</pubDate></item><item><title><![CDATA[Reply to Asterisk --> segfault--> on Wed, 01 Jul 2009 16:14:45 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">If asterisk is segfaulting because of callevents in sip.conf, then turn it off.. you will loose hold status on fop, but the pbx will be stable  <img src="http://localhost:4567/assets/plugins/nodebb-plugin-emoji/emoji/android/1f642.png?v=9c14fadbfa0" class="not-responsive emoji emoji-android emoji--slightly_smiling_face" style="height:1.4em;width:auto;vertical-align:middle" title=":)" alt="🙂" /></p>
<p dir="auto">Now, I have not seen any segfault due to that sip option. What asterisk version are you running? Maybe updating asterisk will fix the issue...</p>
<p dir="auto">Best regards,</p>
]]></description><link>http://localhost:4567/post/59</link><guid isPermaLink="true">http://localhost:4567/post/59</guid><dc:creator><![CDATA[nicolas]]></dc:creator><pubDate>Wed, 01 Jul 2009 16:14:45 GMT</pubDate></item><item><title><![CDATA[Reply to Asterisk --> segfault--> on Wed, 01 Jul 2009 14:32:11 GMT]]></title><description><![CDATA[<p dir="auto">Not sure what the error is so hopefully Nicolas will be about soon but I wouldn't put it in the sip.conf as this will get over written by freePBX sooner or later, pop it into the sip_custom.conf</p>
]]></description><link>http://localhost:4567/post/58</link><guid isPermaLink="true">http://localhost:4567/post/58</guid><dc:creator><![CDATA[Thomas]]></dc:creator><pubDate>Wed, 01 Jul 2009 14:32:11 GMT</pubDate></item></channel></rss>