<?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[Transfer to Queue Failes with Hangup]]></title><description><![CDATA[<p dir="auto">Having an issue with transfering to queues from FOP2.</p>
<p dir="auto">Asterisk 11 on FreePBX Distro 5.211.65-15  with FOP2 2.28</p>
<p dir="auto">Getting this in Asterisk log.</p>
<pre><code>[2014-08-21 14:01:15] WARNING[22364][C-00000116]: pbx.c:6646 __ast_pbx_run: Channel 'Local/6001@from-queue-00000011;2' sent to invalid extension but no invalid handler: context,exten,priority=from-queue-exten-only,6001,1
</code></pre>
<p dir="auto">This is FOP2 AMI command being executed.</p>
<pre><code>127.0.0.1            -&gt; Action: Redirect
127.0.0.1            -&gt; Channel: SIP/5004-000000c2
127.0.0.1            -&gt; Exten: 6001
127.0.0.1            -&gt; Context: from-queue
127.0.0.1            -&gt; Priority: 1
127.0.0.1            -&gt; Async: True

127.0.0.1            &lt;- Response: Success
127.0.0.1            &lt;- Message: Redirect successful
</code></pre>
<p dir="auto">I followed the trail and the "from-queue" context is for the queue to originate a call to an extension, not for putting a call into the queue.  I updated the database table fop2buttons and set context for the queue buttons to "ext-queues" and the transfer works as expected.</p>
<p dir="auto">Just wanted to put this out there so it could possibly be fixed or so that others could fix this if they have the same problem.</p>
]]></description><link>http://localhost:4567/topic/1808/transfer-to-queue-failes-with-hangup</link><generator>RSS for Node</generator><lastBuildDate>Tue, 27 Oct 2026 14:01:22 GMT</lastBuildDate><atom:link href="http://localhost:4567/topic/1808.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 21 Aug 2014 19:23:58 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Transfer to Queue Failes with Hangup on Sun, 28 Sep 2014 01:39:37 GMT]]></title><description><![CDATA[<p dir="auto">I had this problem, but when I looked in functions-freepbx.php, I saw that the code block above was already commented out, and the <strong>$context="from-internal";</strong> line was already added above it. Maybe I downloaded 2.28 after you found and fixed that bug, but I still had the issue. What I was missing was the database update. Thanks for the info.</p>
]]></description><link>http://localhost:4567/post/7843</link><guid isPermaLink="true">http://localhost:4567/post/7843</guid><dc:creator><![CDATA[CoreyFlies]]></dc:creator><pubDate>Sun, 28 Sep 2014 01:39:37 GMT</pubDate></item><item><title><![CDATA[Reply to Transfer to Queue Failes with Hangup on Thu, 21 Aug 2014 19:58:13 GMT]]></title><description><![CDATA[<p dir="auto">You are right, the context should be from-internal. It is a bug in the fop2manger.</p>
<p dir="auto">Look at the /var/www/html/fop2/admin/functions-freepbx.php file aournd line 360:</p>
<pre><code>    $fpbx_version = preg_replace('/[^0-9]/','',freepbx_get_version());
    if($fpbx_version &lt;= 260) {
        $context="from-internal";
    } else {
        $context="from-queue";
    }
</code></pre>
<p dir="auto">Replace all of that with just:</p>
<pre><code>$context='from-internal';
</code></pre>
<p dir="auto">That should fix the problem for newly created buttons. For your existing ones, you will have to update the fop2buttons table and update the context field, something like this:</p>
<pre><code>mysql -u root -p asterisk -e "UPDATE fop2buttons SET context='from-internal' WHERE type='queue'
</code></pre>
]]></description><link>http://localhost:4567/post/7842</link><guid isPermaLink="true">http://localhost:4567/post/7842</guid><dc:creator><![CDATA[nicolas]]></dc:creator><pubDate>Thu, 21 Aug 2014 19:58:13 GMT</pubDate></item></channel></rss>