[Amportal-users] How to restrict certain extensions to local

system · June 1, 2006, 6:58pm

if you wnat to do it in the admin interface you can protect the trunk with a
password. this way users of the trunk would be prompted for a password
inorder to access it.

I don’t know what version of Freepbx you are running but
extensions.conf has the context [from-internal]
[from-internal] has the context [from-internal-additional]

extensions_additional.conf has the context [from-internal-additional] which
inturn has a whole bunch of apps and [outbound-allroutes]

in [outbound-allroutes] you will see the definition of the outbound routes.
the extensions coming thru [from-internal] call out via this context.

So for the extensions that dial local and long distance it would be ok to
use from-internal for the guys who can only dial local you will have to do
a custom-context that includes the apps you wnat and only the local route
but you can’t use or end up using [from-internal-additional] because it
references [outbound-allroutes] which uses all the outboud routes.

From: Chuck Bunn [email protected]
Reply-To: [email protected]
To: [email protected]
Subject: Re: [Amportal-users] How to restrict certain extensions to local
callsonly?
Date: Thu, 01 Jun 2006 09:26:36 -0600

Hi,

Can this be done from inside the free-PBX administrator? What’s odd is
that my zapata.conf has the context listed as ‘from-zaptel’ (I
understand that this is interchangeable with from-pstn - I set them to
from-zaptel since this is required if using the zap channel to identify
inbound routes) for fxs signaling. I all also have one fxo using a
context of ‘local’ and one fxo with a context of ‘longdistance’. All of
my SIP extensions have the context ‘from-internal’. I have one Zap
extension that has the context listed as ‘local’. I have an outbound
route called ‘local’ that has a local dial pattern only and I have a
outbound route called ‘longdistance’ that has both a local and long
distance dial pattern. Before FreePBX all of my sip extensions were part
of the longdistance context except for one that had a local context. I
also had on fxo port that was limited to local calls and one that was
limited to longdistance. I have no context called ‘outbound-allroutes’.

Thanks

Amportal-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amportal-users

Post generated using Mail2Forum (http://www.mail2forum.com)