Member
Last active 9 years ago
Can you tell me what email address the activation codes would come from. I purchased this on Friday and want to make sure the codes make it to us. We have had issues in the past with our spam filter stopping fop2 email but I know I white listed house.com.ar.
Thanks
One question, it states "...last received a call" in the description, is this limited to inbound calls or will outbound calls also reset this timer?
Fantastic news!! We actually are running FOP2 v2.29 (you fixed an issue with Record and RecordSelf working together in that version for us) and we are running Asterisk 12 so we should not have the compatibility issues. I am assuming we should download a latest version of 2.29 before trying to use this Plugin.
I see an Idle Timer plugin is now available for FOP2. The description states "Displays an idle timer on extensions, to know how long since they last received a call." Is this counter the same value we would see on the Realtime tab of Call Center Stats labeled there as "Last In Call"? So idle is relative only to inbound queue calls. I don't believe Asterisk actually tracks an actual idle time for a user so I expect this is the case. Although I would be very happy if this is something more.
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?
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.
Fantastic, I wasn't aware templates were able to be update all uses like that now. Thanks
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.
Thanks, we currently don't have any groups defined in FOP2 for this but the action submenu only show queues that the user is a Dynamic member just as we want. If there is no way to get these both to function the same I can look into setting up groups, I was hoping for one less place to have to maintain our 100 plus user extensions.
I assume it is the expected behavior for the Queue Login popup box to include all queues defined on the system (if not I guess we have an issue with our install). We would like to see that popup box only display the queues that are available for the user logging in. This would be the same list that currently shows up for the Add to and Remove from menus on the users button.