<?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[Recordings Visibility for different users/contexts]]></title><description><![CDATA[<p dir="auto">Hi !</p>
<p dir="auto">We have several users with own contexts. If the "user 1" with context "user1" make record of his call, he can see it in VisualPhonebook - Recordings, but the "user2" with context "user2" can also see it. Is it a bug or a future ? <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">The records in mysql table come with empty "context" field... But if i fill this field with context name "user1" or "user2" nothing changes - all recoring are visible to all users.</p>
<p dir="auto">2.27 version - asterisk 1.4</p>
<p dir="auto">Any ideas ?</p>
]]></description><link>http://localhost:4567/topic/1638/recordings-visibility-for-different-users-contexts</link><generator>RSS for Node</generator><lastBuildDate>Tue, 27 Oct 2026 13:10:02 GMT</lastBuildDate><atom:link href="http://localhost:4567/topic/1638.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 08 Nov 2013 08:20:10 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Recordings Visibility for different users/contexts on Sun, 10 Nov 2013 11:16:34 GMT]]></title><description><![CDATA[<p dir="auto">Thanks for the feedback, I understand your need, and you have fixed it already to suit you.</p>
<p dir="auto">Anyways, I think that in regular cases, the "admin" user should be limited by panel context, as the panel context is thought to be used in multi tenant setups, and the admin granting access to other contexts is indeed a bug/problem.</p>
<p dir="auto">Be sure you backup your recordings.php file so it does not get overwritten if you upgrade fop2 in the future!</p>
<p dir="auto">Best regards,</p>
]]></description><link>http://localhost:4567/post/7036</link><guid isPermaLink="true">http://localhost:4567/post/7036</guid><dc:creator><![CDATA[nicolas]]></dc:creator><pubDate>Sun, 10 Nov 2013 11:16:34 GMT</pubDate></item><item><title><![CDATA[Reply to Recordings Visibility for different users/contexts on Sun, 10 Nov 2013 05:34:11 GMT]]></title><description><![CDATA[<p dir="auto">It doesn't separate the contexts in this way , it separates by originate exten. So if the call was made from "user1" exten, than the "ownerexten=user1" and only "user1" can see these recordings. No need to add ${FOP@CONTEXT} in monitor_exec file name...</p>
<p dir="auto">My system work as the following - I have about 100 users and every user can make recordings, can see them and can delete ( add a button "delete" to the page ). Every night the script cleans /var/spool/asterisk/monitor/fop2 folder and mysql table so  Users who need their records, must download them and store on local hosts. On my opinion it's the best way to give the ability to record and to keep server clean.</p>
<p dir="auto">Best regards,<br />
Sergio.</p>
]]></description><link>http://localhost:4567/post/7035</link><guid isPermaLink="true">http://localhost:4567/post/7035</guid><dc:creator><![CDATA[seregh]]></dc:creator><pubDate>Sun, 10 Nov 2013 05:34:11 GMT</pubDate></item><item><title><![CDATA[Reply to Recordings Visibility for different users/contexts on Sat, 09 Nov 2013 20:57:01 GMT]]></title><description><![CDATA[<p dir="auto">having "all" permissions is treated as an "admin", anyways, I will see if I will modify the script so it separates the contexts.</p>
]]></description><link>http://localhost:4567/post/7034</link><guid isPermaLink="true">http://localhost:4567/post/7034</guid><dc:creator><![CDATA[nicolas]]></dc:creator><pubDate>Sat, 09 Nov 2013 20:57:01 GMT</pubDate></item><item><title><![CDATA[Reply to Recordings Visibility for different users/contexts on Sat, 09 Nov 2013 18:25:29 GMT]]></title><description><![CDATA[<p dir="auto">Well, it's really add context in mysql table, but it didn't solve the problem. The recordings are still visible to everybody from different contexts.</p>
<p dir="auto">But i found the solution. I cut <em><strong>OR $admin=1</strong></em> part from  recordings.php<br />
$grid-&gt;set_condition("(ownerextension='$extension' OR $admin=1)");</p>
<p dir="auto">and now only owner of current extension can see these recordings.</p>
<p dir="auto">By the way, what kind of "admin" was here ?</p>
<p dir="auto">Best regards,<br />
Sergio.</p>
]]></description><link>http://localhost:4567/post/7033</link><guid isPermaLink="true">http://localhost:4567/post/7033</guid><dc:creator><![CDATA[seregh]]></dc:creator><pubDate>Sat, 09 Nov 2013 18:25:29 GMT</pubDate></item><item><title><![CDATA[Reply to Recordings Visibility for different users/contexts on Fri, 08 Nov 2013 12:37:31 GMT]]></title><description><![CDATA[<p dir="auto">Add the context to the filename so it gets populated, in fop2.cfg:</p>
<pre><code>monitor_filename=/var/spool/asterisk/monitor/${ORIG_EXTENSION}_${DEST_EXTENSION}_%h%i%s_${UNIQUEID}_${FOP2CONTEXT}
</code></pre>
<p dir="auto">Best regards,</p>
]]></description><link>http://localhost:4567/post/7032</link><guid isPermaLink="true">http://localhost:4567/post/7032</guid><dc:creator><![CDATA[nicolas]]></dc:creator><pubDate>Fri, 08 Nov 2013 12:37:31 GMT</pubDate></item></channel></rss>