You should probably avoid giving incoming access to outgoing.. PaulH
Lee, John (Sydney) wrote: >> With an ISDN10/20/30/etc, I would just put all the lines into an >> 'incoming' context - and make sure that incoming context doesn't have >> any includes (unless you really need them...) >> > > Can someone please have a look at below to see if this would be the best > and secure practice of using context in dialplan for a PRI environment? > > I just want to mention that the [incoming] context needs to include the > [outgoing] and [internal] contexts or else the extensions won't work. > > I'd appreciate any comments. Thanks. > > In zapata.conf, ... > > [channels] > context=incoming > channel=>... > > In extensions.conf, ... > > [general] > ... > #include "extensions.incoming" > #include "extensions.internal" > #include "extensions.outgoing" > > In extensions.incoming, ... > > [incoming] > ... > include => internal > include => outgoing > ... > > In extensions.internal, ... > > [internal] > ... > > In extensions.outgoing, ... > > [outgoing] > ... > > > > _______________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > AstriCon 2008 - September 22 - 25 Phoenix, Arizona > Register Now: http://www.astricon.net > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2008 - September 22 - 25 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
