Keylock
This module allows the user to lock or unlock his or her extension by dialing the appropriate code and a pin. When the extension is locked, only calls destined to numbers specified in the module's configuration can be made.
The module generates the appropriate hints to have ip phones show the keylock state by subscribing to the <toggle code><ext number> extension.
The first time the user tries to lock his or her extension the module will ask for a new password, which will be used thereafter to lock or unlock the extension.
The latest release can be found at:
http://www.freepbx.org/trac/browser/contributed_modules/modules
- Printer-friendly version
- Login or register to post comments
Keylock Module not working
Hello,
I just installed the latest version of Keylock 0.4.1 and the installation was straight forward no issues at all, my testing environment is a PiaF box running CentOS 5.2, FreePBX 2.8 and Asterisk 1.4. Got 7 Grandstream GXP280 IP Phones.
When dialing the *59 asks for the PIN code, and it says security is enabled (blocked), however you can still dial outside(mobile, international, fixed), I first removed the patterns by default and just placed 105 and 116 as these are the emergency numbers for Police and Firemen in Peru, but as mentioned before calls to mobile, fixed or any other phone number is completed which souldn't as I enabled the keylock with *57 + PINCode.
The phone is responding the feature code (including the voice messages) however not performing the desired action to block/unlock the IP phone keypad. Is there any option or setting I need to do on the IP phone itself?
Any help will be much appreciated.
Regards,
Eduardo Fernandez
Keylock Module
Hello
This is intended as feedback for the author of the keylock module 0.4.1. I tried it out on freepbx 2.7.0.6, and found the following:
1. The Key Lock page needs to be more informative, with comments to the effect of:
"These are the dial patterns that are BLOCKED when the Keylock is activated.
Note: The patterns used determine the effectiveness of this feature. Set these with care."
2. The *59 change password command only works once. Subsequent attempts fail.
There is a rough fix for this, which is to comment out line 131 in functions.inc.php.
3. There is no way to retrieve extension passwords or reset them using a master password; the only way to get or reset a password is through direct AstDB queries.
4. If the dial patterns table is left empty, calls fail.
5. The VM authentication messages used are the same as the ones used when a pincode is set on an outbound route. This could confuse end users.
6. Keylock hints wrongly show Dahdi extensions as SIP.
This would be a highly useful module if the above issues were addressed.
Regards,
John
That module is maintained by
That module is maintained by the author.
If you create a feature request in the ticket system (set type to Feature Request and set Component to Third Party Module) the author will see this and can decide if he wants to implement the changes.
OK
Thanks, Micke. I will give that a go.
The module would be fine with a liitle more work.