not that it matters... We have a site with a need for a flexible attendant to be able to forward their calls off site. There is no set schedule for this, because they have someone in at various times at night and weekends to handle calls without forwarding them.
We use the polycom forward button, but have a phanton user (user with no phone and a permanent call forward) that they forward to as needed. This method has never posed any permissions based issues, however, it is not nearly as flexible as the userui. On Wed, Jan 13, 2010 at 3:01 PM, Robert Joly <[email protected]> wrote: > > >Openfire portal is currently available mainly for ease-of-development > > and testing but will be shut down come >the stable release. > > > > It would be nice if it could be "re-activated" by a power > > admin for access to some features that might not be available > > via SipX... for per user federation for example... > > The danger here is that in our current integration model, sipXonfig is > the master for all configuration. It is through it that IM users, > Multi-user chatrooms and IM groups can be provisioned. Having the > sipXconfig as the master makes it very easy to tie the openfire config > into our existing backup and restore scheme and concentrates all the > system's config information in one place which makes thing generally > simpler. If we were to allow a backdoor (such as the openfire web > portal) through which openfire config can be modified without > sipXconfig's knowledge, sipXconfig would no longer be the complete > master of the configuration and its view of the current openfire > configuration would only be partial. This creates backup & restore > issues, loss of config data and opens the door for invalid > configurations. > > On top of that, it is our understanding that there are licensing > implications surrounding the bundling of the openfire web portal into > other products like sipXecs. The main contention point is around the > copyrighted openfire logo I believe. > > Over time, we will extend the amount of openfire settings that are > accessible via sipXconfig to address the users needs. For our first > release we picked a modest subset that still delivered a lot of > functionality. > > > > > >We are questioning the 'per user' part right now. This is currently > > achieved via the Kraken plug-in but it >has some pretty ugly > > bugs and is not well maintained. That functionality may end > > up being pulled out before >4.2 is released. I would like to > > understand what aspects of that feature make it compelling for you. > > > > By per user I mean that we would like to be able to control > > federation ourselves, not give the user direct access. We > > don't want most users to be able to do it. Internal IM for > > most users or with selected extranet partners etc. > > > > Openfire was seen as a solution prior to it even being > > announced as being integrated with SipX. For me, I would be > > love to see a plug in that integrated user setup etc, but > > allowed the full use of Openfire. > > Probably a bit much, but I can always hope... :) > > > > Bottom line is we want internal IM, with the for some > > selected users to be able to federate with public services. > > I get it. The 'per-user federation' in openfire is delivered by an open > source plug-in called Kraken but unfortunately, this plug-in has a > number of fairly major bugs and is not well maintained. You may find > that your users will not be satisfied with its performance and > reliability... > > > _______________________________________________ > sipx-dev mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > sipXecs IP PBX -- http://www.sipfoundry.org/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec.
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
