<![CDATA[Limit what functions can be used per extension]]>Is there a way to limit what functions can be used per extension?

Example. I want Ext. 6000 to be able to listen to calls on Ext. 6001 but not be able to listen to calls on Ext. 6002.

]]>http://localhost:4567/topic/200/limit-what-functions-can-be-used-per-extensionRSS for NodeTue, 27 Oct 2026 04:53:16 GMTMon, 14 Dec 2009 15:36:07 GMT60<![CDATA[Reply to Limit what functions can be used per extension on Fri, 15 Jan 2010 12:54:30 GMT]]>Hi Nicolás,

If you use centos 32 bits, you can download the latest beta from http://www.fop2.com/downloads/fop2.tgz

Is it possible to have this new features on etch/lenny beta releases ? I can use groups in buttons.conf for display extensions in many boxes but I can't use groups in fop2.cfg for rights and privacy function. If you update etch beta release, please make attention to perl problems because I can't install lenny beta release anymore.

Best regards,

Nicolas.

]]>http://localhost:4567/post/907http://localhost:4567/post/907Fri, 15 Jan 2010 12:54:30 GMT<![CDATA[Reply to Limit what functions can be used per extension on Mon, 28 Dec 2009 22:29:23 GMT]]>have just tried installing beta but when I try to start I get this:

service fop2 start
Starting Flash Operator Panel 2: Can't load '/tmp/par-root/cache-f7eb787270f21cccc1fc58fb4e333050fc915c51/ab48145e.so' for module Filter::Crypto::Decrypt: libcrypto.so.6: cannot open shared object file: No such file or directory at /usr/lib/perl5/5.8.8/i386-linux-thread-multi/DynaLoader.pm line 230.
at /usr/lib/perl5/site_perl/5.8.8/PAR/Heavy.pm line 109
BEGIN failed--compilation aborted at /tmp/par-root/cache-f7eb787270f21cccc1fc58fb4e333050fc915c51/inc/lib/Filter/Crypto/Decrypt.pm line 37.
Compilation failed in require at script/fop2_server.pl line 1.
BEGIN failed--compilation aborted at script/fop2_server.pl line 1.
[FAILED]

any ideas?

]]>http://localhost:4567/post/906http://localhost:4567/post/906Mon, 28 Dec 2009 22:29:23 GMT<![CDATA[Reply to Limit what functions can be used per extension on Fri, 18 Dec 2009 13:25:17 GMT]]>As usual, it's just mistake made through lack of attention. I'm use different Manager credentials for FOP2. And after reinstall new fop2.cfg reverted it to FOP2's defaults.
After changing credentials it works as usual.
Sorry, my mistake.

]]>http://localhost:4567/post/905http://localhost:4567/post/905Fri, 18 Dec 2009 13:25:17 GMT<![CDATA[Reply to Limit what functions can be used per extension on Fri, 18 Dec 2009 12:59:20 GMT]]>After upgrading to the latest beta I can see all the extensions buttons, but no any actions. They all always green, even disconnected, and no calls displayed.
Also, no permissions defined in FreePBX (in VM Options field) works. All users has full control (all buttons active).
What could be wrong?

]]>http://localhost:4567/post/904http://localhost:4567/post/904Fri, 18 Dec 2009 12:59:20 GMT<![CDATA[Reply to Limit what functions can be used per extension on Wed, 16 Dec 2009 14:01:39 GMT]]>If you use centos 32 bits, you can download the latest beta from http://www.fop2.com/downloads/fop2.tgz

Crash course on new features:

In fop2.cfg:

group=GROUPNAME:SIP/100,SIP/200
For defining group of buttons/channels, you can assign a group to a user so he can only see that group.

user=extension㊙permissions:group
You can assign groups to a user after the permissions. If no group is specified it will show all buttons.

New permissions:

queue: for letting the user manipulate queue members (Add/remove/pause)
phonebook: for granting access to the phonebook

In the button definition:

group=GROUPNAME
not related to the user groups, this will just group visually the extensions on their own box.

privacy=all | clid | monitor
For limiting that button from being spied/monitored or displaying clid or both

queuecontext=from-queue
(for freepbx 2.6, context for the queue members when using Local, if different than the regular extension context)

**originatechannel=Local/xxxx@custom-fop2-originate **
So you can originate calls to your dialplan instead of the channel, so you can use autoanswer features for the phone, having something like this in freepbx:

[custom-fop2-originate]
exten => _X.,1,Goto(ext-intercom,*80${EXTEN},1)

queuechannel=Local/xxxx@from-queue/n
For setting the channel you want to use for adding a queue member if different from the main channel.

There are several other features that I am forgetting, but you get the idea.

Best regards,

]]>http://localhost:4567/post/903http://localhost:4567/post/903Wed, 16 Dec 2009 14:01:39 GMT<![CDATA[Reply to Limit what functions can be used per extension on Wed, 16 Dec 2009 13:15:43 GMT]]>Those new features sound great. Do you have a release date? Do you need beta testers?

]]>http://localhost:4567/post/902http://localhost:4567/post/902Wed, 16 Dec 2009 13:15:43 GMT<![CDATA[Reply to Limit what functions can be used per extension on Tue, 15 Dec 2009 17:19:17 GMT]]>No, you cannot limit actions that way right now.

The next version has a privacy option that can be set to any button that lets you prevent that button from being monitored (chanspy, monitor to disk) and the clid or dialed number will be also hidden.

By using panel contexts you can have different permissions for the same extension, but they will apply to all buttons.

Best regards,

]]>http://localhost:4567/post/901http://localhost:4567/post/901Tue, 15 Dec 2009 17:19:17 GMT