|
Revision 6040, 1.7 kB
(checked in by Nick_Lewis, 6 months ago)
|
New Module Usersets
|
| Line | |
|---|
| 1 |
----------------------------------- |
|---|
| 2 |
The "Usersets" Module for FreePBX |
|---|
| 3 |
----------------------------------- |
|---|
| 4 |
|
|---|
| 5 |
This module provides user based access control for outbound routes |
|---|
| 6 |
|
|---|
| 7 |
|
|---|
| 8 |
Operation |
|---|
| 9 |
--------- |
|---|
| 10 |
|
|---|
| 11 |
If the use of a userset is specified by an outbound route then the route will not be accessible unless the caller is listed in the userset. |
|---|
| 12 |
If not listed the caller will hear the audible prompt "Cancelled" and the call will terminate |
|---|
| 13 |
|
|---|
| 14 |
Within a userset there are two types of users: |
|---|
| 15 |
(i) Users that are trusted - These users need to provide no authentication. The fact that they are calling from a trusted extension number gives them access to the outbound route. |
|---|
| 16 |
(ii) Users that need authentication - These users need to provide authentication to demonstrate that they are who they claim to be. These users are prompted for their voicemail password before being given access to the outbound route. |
|---|
| 17 |
|
|---|
| 18 |
If this module is enabled then it hooks into the outbound routes page (in the same way as the pinsets module). All existing usersets are displayed in a list box on the page. |
|---|
| 19 |
|
|---|
| 20 |
|
|---|
| 21 |
Preconditions |
|---|
| 22 |
------------- |
|---|
| 23 |
|
|---|
| 24 |
This module expects the ext_vmauthenticate class to be in extensions.class.php as per FreePBX Ticket #2777. |
|---|
| 25 |
If not the modules functions.inc.php will need to be modified to generate the VMAuthenticate dialplan command itself e.g. |
|---|
| 26 |
$command = "VMAuthenticate(" .($mailbox ? $mailbox : ) .($context ? '@'.$context : ) .($options ? '|'.$options : ) .")" |
|---|
| 27 |
|
|---|
| 28 |
|
|---|
| 29 |
Open Issues |
|---|
| 30 |
----------- |
|---|
| 31 |
|
|---|
| 32 |
A caller's number is tested in turn against each entry in the userset. For large usersets this can be a slow process. More time sensitive users should be put near the top of a userset list. |
|---|
| 33 |
|
|---|
| 34 |
|
|---|
| 35 |
Author |
|---|
| 36 |
------ |
|---|
| 37 |
nick.lewis@atltelecom.com |
|---|