You all did well but you didn't pick the simplest method:

Add this to a user:

 <variable name="toll_allow" value="local,ld,int"/>

Then in your dialplan for the extension you wish to protect from various routes:

<condition field="${toll_allow}" expression="local"/>

/b




On Aug 6, 2008, at 12:33 AM, UV wrote:

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@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf OfRoberto Hernandez
Sent: Wednesday, August 06, 2008 2:01 PM
To: freeswitch-users@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@domain1.com <--> FS <--> Allowed PSTN
 
user2@domain1.com <--> FS <--> Not Allowed PSTN
 
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


_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org