<?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[Extension buttons stuck?]]></title><description><![CDATA[<p dir="auto">Hello,</p>
<p dir="auto">I installed FOP2 months ago in preparation for a bigger deployment and actually purchasing it. At the time everything seemed to work fine. I've since updated the server and updated FOP2. And before I purchased I was going to just make sure everything was still working.</p>
<p dir="auto">Well for whatever reason buttons for user extensions seem to be "stuck". For instance I types a feature code *73 and now my line 1 shows that I still have an active outbound call to that number. Another one has *79 stuck. Another has an outbound call to 11 digit North American phone #. I've tried reloading FOP2, reloading Asterisk, and a few other things but nothing worked.</p>
<p dir="auto">Any help on why this would be happening and how to fix it?</p>
]]></description><link>http://localhost:4567/topic/2115/extension-buttons-stuck</link><generator>RSS for Node</generator><lastBuildDate>Tue, 27 Oct 2026 07:48:08 GMT</lastBuildDate><atom:link href="http://localhost:4567/topic/2115.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 03 Dec 2015 23:00:48 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Extension buttons stuck? on Sat, 05 Dec 2015 02:33:39 GMT]]></title><description><![CDATA[<p dir="auto">Hint: shortcut to restart is</p>
<p dir="auto">service fop2 restart</p>
<p dir="auto">See if you still have buttons stuck after dialing feature codes...</p>
]]></description><link>http://localhost:4567/post/9304</link><guid isPermaLink="true">http://localhost:4567/post/9304</guid><dc:creator><![CDATA[nicolas]]></dc:creator><pubDate>Sat, 05 Dec 2015 02:33:39 GMT</pubDate></item><item><title><![CDATA[Reply to Extension buttons stuck? on Thu, 03 Dec 2015 23:39:45 GMT]]></title><description><![CDATA[<p dir="auto">I guess things always work this way for me. Once I post something I fix it.<br />
I thought reloading FOP2 from the manager would be the same as starting and stopping the service from the CLI. However that didn't solve my problem. As soon as I ran;</p>
<pre><code>service fop2 stop
service fop2 start
</code></pre>
<p dir="auto">The buttons cleared state and seem to be working fine again.</p>
]]></description><link>http://localhost:4567/post/9303</link><guid isPermaLink="true">http://localhost:4567/post/9303</guid><dc:creator><![CDATA[jgould]]></dc:creator><pubDate>Thu, 03 Dec 2015 23:39:45 GMT</pubDate></item></channel></rss>