> Hi, > Not all openfire configuration parameters are exposed in sipXconfig. > For those that are not exposed, we need to make sure that the > out-of-the-box default values line up with sipXecs's requirements. To > that end, I went through the entire openfire management pages and noted > 8 parameters that I feel we need to reconfigure from their openfire > defaults. Please find the list below. Squawk now if you do not > agree > with that list. > > Thanks, > bob > > > Here is the list of openfire-provided defaults that I believe we need > to > override in sipXecs: > > Setting #1- The server will automatically check for server or plugins > updates. > openfire-provided default: enabled > new suggested default value: disabled > Justification: sipXecs will be the master of software upgrades > including > those for openfire. As such, we do not want the openfire component to > go out and request automatic updates > Agreed
> Setting #2- Administrators will receive notifications when new updates > are available. > openfire-provided default: enabled > new suggested default value: disabled > Justification: Same as #1. > Agreed > Setting #3- Users can automatically create new accounts. > openfire-provided default: enabled > new suggested default value: disabled > Justification: In order to keep databases consistent, sipXconfig is the > sole controller of IM users on the system. Allowing users to create > new > accounts would circumvent this which is not a good thing. > Agreed > Setting #4-Users can change their password. > openfire-provided default: enabled > new suggested default value: disabled > Justification: Existing sipXecs model is that users cannot change their > passwords - administrator is in control of that piece of information. > Agreed > Setting #5- Clients can only connect to the server using secured > connections. > openfire-provided default: optional > new suggested default value: required > Justification: Privacy concern > Agreed > Setting #6- Connections between servers always use secured connections. > openfire-provided default: optional > new suggested default value: required > Justification: : Privacy concern > > Setting #7- Show the entire chat history to users joining a multi-user > chat room. > openfire-provided default: show last 25 entries > new suggested default value: Don't Show History > Justification: Privacy concern. When someone enters my chat room, I do > not want that person to see what the last 25 entries were. Imagine this > conversation: > -Joe: Simon is just not pulling his weight, I think we should fire him > -Mike: I agree about the performance issues but let's give him one last > chance > -Joe: Ok fine. Let me invite him to this room to chat about > performance > improvement. > [Joe has invited Thomas] > [Thomas just entered the room].... > ---- > Now, at this point, it would not be desirable for Thomas to be shown > the > last 25 lines of that conversation... > Agreed > Setting #8- who can create group chat rooms > openfire-provided default: Anyone can create a chat room. > new suggested default value: Only admin can create chatrooms > Justification: In order to keep databases consistent, sipXconfig > controls the chatrooms creation. > Wouldn't this mean we could do adhoc group chat? We may want to reconsider this one. > > _______________________________________________ > 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/ _______________________________________________ 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/
