i was working today in the Chrome extension adding panel context functionality, I have to see if I will work on adding more features or try to make a small update first with the panel context and work on prefixes or perhaps some number normalization, like replacing + with 00 or 011, etc.
Expect an update this week but not sure if it will have the dial prefix option yet.
The Chrome FOP2 extension is an awesome cool feature. I love it!
I noticed a simple problem which I could not solve. When I put a user into a permission group other than "all", click-to-dial- does not work.
I need to exclude "record" option for users. But when I create a new permission group, even when I include all permissions including "record", the click-to-dial does not work. It seems that "all" has more permissions that all the permissions listed.
The permission needed is "dial". I have just tested it and it works fine. You need the straight dial permission, not the dial permission within a custom permission. This is because a custom permissions is done to prevent an action from working on a group of extensions, if you set dial within a custom permission, you will only be able to dial those extensions and not external numbers. So, just regular "dial" in the permissions must work.
Comments
I will see if I can add it for the next release.
Expect an update this week but not sure if it will have the dial prefix option yet.
Best regards,
Best regards,
The Chrome FOP2 extension is an awesome cool feature. I love it!
I noticed a simple problem which I could not solve. When I put a user into a permission group other than "all", click-to-dial- does not work.
I need to exclude "record" option for users. But when I create a new permission group, even when I include all permissions including "record", the click-to-dial does not work. It seems that "all" has more permissions that all the permissions listed.
I'll appreciate any suggestion and advise.
Thank you,
_Joseph