<?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[Old ext name is appearing ]]></title><description><![CDATA[<p dir="auto">Hello,</p>
<p dir="auto">Sometimes the system is displaying the agent name wrongly on a particular extension (3311 in this case), where the current agent name on the extension is (Nora) and the system is showing the old name of the resigned agent (Abeer).</p>
<p dir="auto">we have changed this from the fop2 admin under buttons but we are still facing the issue</p>
<p dir="auto">Thank you.</p>
]]></description><link>http://localhost:4567/topic/1889/old-ext-name-is-appearing</link><generator>RSS for Node</generator><lastBuildDate>Tue, 27 Oct 2026 11:31:57 GMT</lastBuildDate><atom:link href="http://localhost:4567/topic/1889.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 25 Jan 2015 14:51:44 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Old ext name is appearing  on Thu, 29 Jan 2015 19:08:27 GMT]]></title><description><![CDATA[<p dir="auto">Whenever a dynamic member is added to a queue, the member name is set on that command also. If that name is old/incorrect/not the one you want, then it is up to modifying that action in the dialplan, or program that performs the dynamic adding, to set the correct name.</p>
<p dir="auto">So, if you use some feature code to dynamic adding agents to a queue, review that dialplan bit and see what member name is being set.</p>
<p dir="auto">Solution is in your dialplan/configuration. FOP2 is making something visible that you probably did not see before.</p>
<p dir="auto">But I insist, I do not know your setup, I do not have enough information to be conclusive, I am just mentioning something that usually happens, and that might be happening to you. Always contrast the data you see on FOP2 with actual activity on the queue_log file or the output from: asterisk -rx "queue show".</p>
<p dir="auto">Check names there also, not only in FOP2.</p>
]]></description><link>http://localhost:4567/post/8237</link><guid isPermaLink="true">http://localhost:4567/post/8237</guid><dc:creator><![CDATA[nicolas]]></dc:creator><pubDate>Thu, 29 Jan 2015 19:08:27 GMT</pubDate></item><item><title><![CDATA[Reply to Old ext name is appearing  on Thu, 29 Jan 2015 02:01:37 GMT]]></title><description><![CDATA[<p dir="auto">The member are not static on the queue, they are login dynamically so every time the agent logs to the queue he will logout later.</p>
<p dir="auto">Any solution is this case</p>
<p dir="auto">Thank you</p>
]]></description><link>http://localhost:4567/post/8236</link><guid isPermaLink="true">http://localhost:4567/post/8236</guid><dc:creator><![CDATA[ashtrexma]]></dc:creator><pubDate>Thu, 29 Jan 2015 02:01:37 GMT</pubDate></item><item><title><![CDATA[Reply to Old ext name is appearing  on Mon, 26 Jan 2015 12:52:13 GMT]]></title><description><![CDATA[<p dir="auto">What you are seeing is most probably the queue member name as set in FreePBX. When you rename an extension in FreePBX, there is a bug where the queue member name is not updated. FOP2 will rename buttons based on the queue member name, so no matter what you change in the fop2 label, it will be renamed to the queue member name.</p>
<p dir="auto">To fix the FreePBX bug, you have to edit the queue (in the freepbx gui), remove the member, save and apply, then add the member again and save and apply. That should re-add that queue member with the new extension name.</p>
<p dir="auto">Best regards,</p>
]]></description><link>http://localhost:4567/post/8235</link><guid isPermaLink="true">http://localhost:4567/post/8235</guid><dc:creator><![CDATA[nicolas]]></dc:creator><pubDate>Mon, 26 Jan 2015 12:52:13 GMT</pubDate></item></channel></rss>