In my experience, what makes a system easy to use is not minimization of the number of options, etc. but rather how easy it is for someone who does not have experience to get from "what I want to do" to "what to do".
(Or as the traditional story goes, "There is a Toyota in the driveway. I'm holding the keys in my hand. What do I do next?") In that regard, providing a large number of configurable parameters isn't such a problem. I.e., allowing the admin to specify the SIP parameter is OK, because sipXecs propagates that decision to all the places it need to be. The problem is that when the user changes the SIP password, the system doesn't hold his hand to let him know that he has to regenerate certain IMDB tables and reload certain phone profiles. The most demanding situation is initial installation, where what the user really needs is an exhaustive list of *all* the things he needs to do to get his VoIP system going to the point that he can make the first phone call. Dale _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
