http://track.sipfoundry.org/browse/XX-7704
Josh Patten Assistant Network Administrator Brazos County IT Dept. (979) 361-4676 On 2/22/2010 6:58 AM, Scott Lawrence wrote: > On Sun, 2010-02-21 at 09:57 -0600, Josh Patten wrote: > >> We're talking about users that barely know how to check their email >> here. The personal auto attendant concept gets me blank stares every >> time I talk about it to end users. If they're savvy enough to use that >> then more power to them :-P >> >> I agree, Scott, that this should not be a "technical solution to a >> managerial problem" but telling that to elected officials and >> department heads doesn't fly. Our Meridian Option 61c is set up to >> only allow internal forwarding to all users and that's the way they >> want it so eventually I'm going to have to be able to accommodate that >> feature. If the original "forward calls external" permission could >> easily be put back in then it would be greatly appreciated. >> > File a New Feature request for this. > > Unfortunately, it's not quite as simple as putting back the old feature, > but it's certainly doable. We're going to be looking at how to > simplify/clarify lots of configuration elements in the next few months, > and this is just a configuration problem. > > To respond to the AA question - in terms of the internal sipXecs > security, anything you set up through forwarding or the AA is executed > with your permissions, so they are for all intents and purposes the > same. > > > _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
