<?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[Feature request from client]]></title><description><![CDATA[<p dir="auto">I have a client with about 40 extensions asking if there is a way to organize them into groups, i.e. Sales, Service, Rooms, etc.<br />
So instead of all the extensions appearing in the Extensions section of the FOP2 UI, they'd appear in separate sections (like Trunks, Conferences, Parks, etc. do now).</p>
<p dir="auto">I thought I might be able to do this using the existing Groups, but it doesn't work that way.</p>
]]></description><link>http://localhost:4567/topic/1867/feature-request-from-client</link><generator>RSS for Node</generator><lastBuildDate>Tue, 27 Oct 2026 09:30:32 GMT</lastBuildDate><atom:link href="http://localhost:4567/topic/1867.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 10 Dec 2014 15:38:07 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Feature request from client on Thu, 18 Dec 2014 17:48:44 GMT]]></title><description><![CDATA[<p dir="auto">Perfect. Thank you Nicolas!</p>
]]></description><link>http://localhost:4567/post/8124</link><guid isPermaLink="true">http://localhost:4567/post/8124</guid><dc:creator><![CDATA[FreerPBXer]]></dc:creator><pubDate>Thu, 18 Dec 2014 17:48:44 GMT</pubDate></item><item><title><![CDATA[Reply to Feature request from client on Wed, 10 Dec 2014 21:28:59 GMT]]></title><description><![CDATA[<p dir="auto">In the "Fop2 buttons" page you can edit all your buttons, and you will see that for Extension buttons there is a "group" field. That field is the one that is used to organize the display (and not filter like the 'fop2 groups' tab). So, you can edit your buttons, fill the group field with any name, and all extensions with the same group name will be shown in its own group. Check the screencast to get an idea:</p>
<p dir="auto"><a href="https://www.youtube.com/watch?v=0xDosgh2t78" rel="nofollow ugc">https://www.youtube.com/watch?v=0xDosgh2t78</a></p>
]]></description><link>http://localhost:4567/post/8123</link><guid isPermaLink="true">http://localhost:4567/post/8123</guid><dc:creator><![CDATA[nicolas]]></dc:creator><pubDate>Wed, 10 Dec 2014 21:28:59 GMT</pubDate></item><item><title><![CDATA[Reply to Feature request from client on Wed, 10 Dec 2014 17:25:58 GMT]]></title><description><![CDATA[<p dir="auto">That's what I thought. But in my testing the groups appeared to function to limit which extensions are shown, but not group them; like permission groups, not organizational groups.</p>
<p dir="auto">I setup three groups, each with a small subset of buttons. The user to which I assigned these group saw ONLY the extensions in those groups, and all appeared in the "Extensions" section of the UI.</p>
]]></description><link>http://localhost:4567/post/8122</link><guid isPermaLink="true">http://localhost:4567/post/8122</guid><dc:creator><![CDATA[FreerPBXer]]></dc:creator><pubDate>Wed, 10 Dec 2014 17:25:58 GMT</pubDate></item><item><title><![CDATA[Reply to Feature request from client on Wed, 10 Dec 2014 17:01:25 GMT]]></title><description><![CDATA[<p dir="auto">Thats exactly what the "group" parameter is for:<br />
<a href="http://www.fop2.com/docs/#ConfiguringButtons" rel="nofollow ugc">http://www.fop2.com/docs/#ConfiguringButtons</a></p>
<p dir="auto">group=Sales<br />
…<br />
group=Service</p>
]]></description><link>http://localhost:4567/post/8121</link><guid isPermaLink="true">http://localhost:4567/post/8121</guid><dc:creator><![CDATA[mkeuter]]></dc:creator><pubDate>Wed, 10 Dec 2014 17:01:25 GMT</pubDate></item></channel></rss>