On Fri, 2008-08-22 at 17:02 +0300, Andrei Cristian Niculae wrote: > Hello, > > I've been talking with Mircea Carasel about a JIRA issue he's been > working on - [1] - an issue about, among other things, introducing the > concept of user site location, as described in [2]. The user > site-location would represent physical location of the user. > We've been thinking of a way of expanding this concept to a more general > "site-location". > This new concept would act like a general group not just for users, but > also for devices, like phones, gateways or SBCs. The first benefit for > this is that the administrator could make settings based on site > location, settings like timezone, or NTP server, these being the > starting point of our discussion (because of [3]). > The site location would be available in a different page, let's say > under System->Site Locations. > Here, one would have the possibility to display users, phones, gateways > and SBCs from a specific location and make settings based on that > location just like with group settings. > > I'm sure that besides time-zone settings and per-user gateways there are > a lot of other things that could use from this concept. So please share > your opinions. > > This e-mail is mainly about collecting opinions whether or not we should > open a JIRA to implement this feature and the benefits this would bring. > As soon as there is an agreement upon this, I'll come back with details > about what we thought would be the first phase in implementing this.
What is 'special' about site location as opposed to any other Group that the administrator chooses to implement and put a user or phone in? I'm concerned that making a distinct sort of group for this will cause us backwards-compatibility issues when we implement a multiple-system (federated) management framework (in which one sipXconfig instance manages multiple sipXecs domains). Let's put this discussion on just one list, please... I suggest sipx-dev _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
