[Freeswitch-users] user access
UV
uv at talknet.com.au
Tue Aug 5 22:33:58 PDT 2008
I think the proper way of doing that is by assigning users to different
dialplan user contexts according to their Class of Service.
For example, an easy way of doing that is to define a user_context
“Not_Allowed_PSTN” for a specific directory user 1010
(conf/directory/default/1010.xml):
<variable name="user_context" value=" Not_Allowed_PSTN "/>
Create a new context called “Not_Allowed_PSTN” and handle those calls as you
like or just add a prefix 0001 and send to the default context:
<condition field="destination_number" expression="^(.*)$">
<action application="transfer" data="0001$1 XML default"/>
</condition>
_____
From: freeswitch-users-bounces at lists.freeswitch.org
[mailto:freeswitch-users-bounces at lists.freeswitch.org] On Behalf Of Roberto
Hernandez
Sent: Wednesday, August 06, 2008 2:01 PM
To: freeswitch-users at lists.freeswitch.org
Subject: [Freeswitch-users] user access
Anyone have suggestions on how to the enable the following scenario? Allow
internal but control external per user.
More importantly how to disable or enable PSTN access for a specific user in
a domain (profile)?
user1 at domain1.com <--> FS <--> Allowed PSTN
user1 at domain1.com <--> FS <--> user2 at domain1.com
user2 at domain1.com <--> FS <--> Not Allowed PSTN
user2 at domain1.com <--> FS <--> user1 at domain1.com
Thanks,
Roberto
No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.138 / Virus Database: 270.5.12/1594 - Release Date: 05/08/2008
21:49
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20080806/493ae0cd/attachment-0002.html
More information about the FreeSWITCH-users
mailing list