I think somewhere in our branch considerations we'll need to think about roaming users. Therefore a branch may not just be a group but may instead be a defined set of IP's that a caller is coming from.
This consideration also will come into play with users who might be on VPN or coming in remotely through a session border controller. So, in the end, a group might really not be the best place on determining a branch location but maybe their IP or some combination thereof. The other thing that IP based branch membership could be used for would be if different vlan's were used per building location then an admin could use different IP addresses to determine building location for emergency dialing. There are probably better ways to do this but it's a consideration. Mike On Fri, Sep 9, 2011 at 8:20 AM, Douglas Hubler <[email protected]> wrote: > On Thu, Sep 8, 2011 at 9:54 AM, Niek Vlessert <[email protected]> > wrote: > > We created a SipX Plugin, Call Admission Control, to limit the amount of > > calls on a per branch level. The patch is not online yet but soon will > be, > > and please look at the ticket. > > http://track.sipfoundry.org/browse/XX-9846 > > Conceptually design makes sense. > > Comments: > > re:user branches > - A user can only belong to 1 branch, so if someone is trying to > branches for CAC and what they were originally intended for : gateway > access. then this could be a problem. I would have considered user > groups for this. > > re: including jars? > sipxecs 4.6 has been significantly refactored to allow for extending. > Almost all jars moved to sipxcommon which is just one of the > improvements. Did you base your work on 4.4 or 4.6? > > - re: Separate service > It a C plugin, that runs within the sipxregistry project, right? What > part of this is a separate service? Separate project, yes, separate > service, not sure yet. > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > -- Michael Picher eZuce Director of Technical Services O.978-296-1005 X2015 M.207-956-0262 @mpicher <http://twitter.com/mpicher> www.ezuce.com
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
