I can't seem to get Record & RecordSelf working at that same time for any user. If both permissions are given the user is only able to record themselves, for all others the option is grayed out when selected. If I remove RecordSelf and leave Record the user is able to record others without issue. We are using FOP2 v2.28 with FreePBX Distro 6.12.65-22 (FreePBX 12.0.17) and Asterisk 11.14.2.
-Brian
I did notice that both work if All permission is granted.
What happens if you only give a user RecordSelf permission? (having both is kind of contradictory)
RecordSelf works as it should. Not sure if having both is contradictory. Our floor supervisors need to record their staff as well as record their own calls at specific times (phone interviews for potential new candidates for example)
Just use Record that allows to record others and also yourself. I think the logic when doing the monitor is that if you have recordself it prevents all the others, no matter if you have also record. That is why they are contradictory in a way, like hangup and hangupself... having hangup will let you hangup anyone, including yourself, while hangupself it lets you hangup only your own calls.
With just Record I can only record others, it's grayed out when I select myself. Let me try another user and make sure their experience is the same.
Same result for the other user, they are just able to record others it's grayed out if they select themselves. If All permission is granted user can record self and others.
you are correct, recordself is not being set correctly when mixed with record. I will fix it on 2.29. You can try to contact me via the live help (i am online now) to test the fix.
Best regards,
Great news thanks!! We had tried the previous 2.29 beta version from last week and it didn't load up any buttons for us so we reverted back. We will grab the latest and try and catch you later on live help to work thru it.
Downloaded the latest 2.29 and it appears to be working correctly. Thanks!
I do see a couple of issues with 2.29. For some reason most of our buttons now are displaying the User Name rather than the Label. If I hover over the button the label does display in the tooltip that pops up. Looks like this is happening for about 2/3s of our extensions.
Not sure the other is specific to 2.29 or not. We did notice that if we make a change and reload FOP2, when the screen refreshes for the users it prompts them again for the Queue Login. I don't recall seeing that with the previous version but we have not had the Queue Login plugin installed that long.
What you see is the queue member name, and that is standard in FOP2. Whenever an extension is logged into a queue, if it has a different queue member name than the extension label, it will be renamed.
Whenever you refresh the fop2 display, some things will reappear, as you already found out. Other plugins that prompt on login will behave in a similar fashion.
Best regards,
Is there a way keep the labels we defined from being renamed (overwritten) as it is in 2.28? The queue member names are users full names and are all uppercase so they appear in reports, etc, we specifically created labels for individuals so they would be displayed properly in FOP2 buttons. For example we have two employees named Brandon, with version 2.29 installed their buttons both display "BRANDON" and the user has to hover to see which is which. To make this easier we modified their labels to be "Brandon A" and Brandon C' and with v2.28 that is what displays displays on their button regardless of them being logged in or not. We also have several people who don't use their given name or use initials only. Their labels have all been updated as well so others can find them. We have reverted back to 2.28 for now since this is impacting more people than the ability to record others and self.
There is no way for buttons to not be renamed if the Local/extension@context queue member matches an extension/context in a button definition. You could set the queuecontext=xxx in your extensions buttons something different from the queue member local device so it does not match, and then it won't be renamed.
I am not the one to say this as it is your PBX, but having two different queue members with the same name is not a good idea if you need to run any kind of queue statistics or reports. You should keep the names different, not because of fop2 but because you will need them differentiated if you run any kind of report.
Best regards,
I am confused, if it behaves as we want it v2.28 how can there be no way for v2.29 to behave the same way?
We do not have queue members with the same name, the queue member names as I stated are uppercase full names (first and last name). The buttons in FOP2 is the place where it will only display part of the name. We simply want the Label field from the FOP2 Manager / Buttons screen to be displayed on the button just as it does in v2.28.
In 2.28 there was a bug. All versions since 2.0 renames button labels for member names when local/xxx@yy matches extension=xxx, context=yyy. If you do not want that to happen, and you use different member names than extensions names, then set the queuecontext to something different.
I was attempting to test this out but can't seem to set the Queue Context field on my button in FOP2 Manager. When I modify that field it flashes like it is being saved but if I navigate away from the page and back again the Queue Context is back to the original value "from-queue". Is this something I can't change in the Manager and I have to edit the actual file?
Yep, in freepbx the queuecontext is 'hardwired', you can modify the file /var/www/html/fop2/admin/update_conf.php and look for this:
if($fop2qctx <> $dat['queuecontext']) {
$query = "UPDATE fop2buttons SET queuecontext='%s' WHERE device='%s'";
$db->consulta($query,array($dat['queuecontext'],$chan));
$need_update=1;
}Just coment the "consulta" line:
if($fop2qctx <> $dat['queuecontext']) {
$query = "UPDATE fop2buttons SET queuecontext='%s' WHERE device='%s'";
//$db->consulta($query,array($dat['queuecontext'],$chan));
$need_update=1;
}