>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... >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. _______________________________________________ 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/
