ewww... very easy to punch holes in it..., digit map is bypassed on polycom if you dial on-hook....
mike On Wed, Jan 25, 2012 at 10:54 AM, Todd Hodgen <[email protected]> wrote: > One very limited option you might consider is with the dial strings in the > devices. For example, if you limit strings from being dials, something > like |2xxx|[4-9]xxx| should disallow the dialing of 3xxx numbers.**** > > ** ** > > Not that this would be pretty, but I’ve used similar to control access to > a range of extensions. This could get ugly fast, and I suspect easy to > punch holes in it.**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Michael Picher > *Sent:* Wednesday, January 25, 2012 2:51 AM > *To:* Discussion list for users of sipXecs software > *Subject:* Re: [sipx-users] Disallowing site-to-site calls**** > > ** ** > > Well, this isn't a tenanted system, so that's first and foremost.**** > > ** ** > > Since user extensions and user aliases are processed before dial plan > entries, there's no way to prevent this.**** > > ** ** > > User permissions secure an entire dial plan entry.**** > > ** ** > > Locations (or branches) secure gateways inside a dial plan entry.**** > > ** ** > > There's no way on a single system to prevent user 2050 from calling user > 3050.**** > > ** ** > > Mike**** > > On Wed, Jan 25, 2012 at 2:51 AM, Paul Kramer <[email protected]> > wrote:**** > > Hello, I was wondering if anyone knows how to segment sites in a way that > will disallow all users from a given site to make calls to all users from > other sites. This question has surfaced due to a multi-tenanting query from > a customer. > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/**** > > > > **** > > ** ** > > -- > Michael Picher, Director of Technical Services > eZuce, Inc.**** > > 300 Brickstone Square**** > > Suite 201**** > > Andover, MA. 01810**** > > O.978-296-1005 X2015 > M.207-956-0262 > @mpicher <http://twitter.com/mpicher> > www.ezuce.com**** > > ** ** > > > ------------------------------------------------------------------------------------------------------------ > **** > > Hope to see you at the sipX CoLab! http://www.sipfoundry.org/sipx-colab*** > * > > A gathering for - open source users, eZuce customers & eZuce partners**** > > Get the inside track on 4.6 and a glimpse at the future of sipXecs!**** > > ** ** > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- Michael Picher, Director of Technical Services eZuce, Inc. 300 Brickstone Square**** Suite 201**** Andover, MA. 01810 O.978-296-1005 X2015 M.207-956-0262 @mpicher <http://twitter.com/mpicher> www.ezuce.com ------------------------------------------------------------------------------------------------------------ Hope to see you at the sipX CoLab! http://www.sipfoundry.org/sipx-colab A gathering for - open source users, eZuce customers & eZuce partners Get the inside track on 4.6 and a glimpse at the future of sipXecs!
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
