On Wed, 15 Jul 2009 17:30:08 -0400, Andy Spitzer <[email protected]> wrote:
> Implementation 2:
>
> A second way is to view a group as being a distribution list
> defined as all the users in that group, and allowing the user to
> specify groups as destinations in his personal list. Represented
> by something like this:
>
> <distributions>
> <list>
> <index>1</index>
> <destination>201</destination>
> <group>administrators/group>
> <group>group1/group>
> </list>
> <list>
> <index>2</index>
> <destination>200</destination>
> </list>
> </distributions>
>
> This defines that distribution list "1" is sent to user 201, all users
> in the "administrators" group, and all users in "group1".
An addition to this, is to add a permissions check for certain groups.
sipXconfig will not allow a user to add selected groups to a distribution list
unless that user also has some permissions. This can be used to restrict users
from selecting restricted groups.
For the system wide list, (which is admin configured), an additional flag per
index could restrict usage of that group to only users with certain
permissions, like this:
<distributions>
<list>
<index privileged="true">1</index>
<group>allusers/group>
</list>
<list>
<index>2</index>
<destination>200</destination>
</list>
</distributions>
If a unprivileged user tried to send a voicemail to index one, the IVR would
disallow it.
What "privileged" maps to in terms of permssions, I'm open to suggestions. My
suggestion is users with "Record System Prompts" can access the privileged
system lists, and can add the privileged groups to their personal lists.
--Woof!
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
