Hello, Ability to use IP addresses instead of having to deal with domains at all, I can see the benefit of this approach but it becomes a serious obstacle to those who want to use SIPX on a small scale, and slows adoption of the platform compared to other solutions in my opinion.
Thanks for all of your hard work. On 1/22/2010 4:23 PM, Scott Lawrence wrote: > As we begin to home in on release 4.2, we're starting to formulate plans > for what comes next... > > First, I want to reassure the community - Avaya is very much committed > both to the SCS commercial product (see roadmap announcements made this > week), and to leading, contributing to, and materially supporting the > sipXecs open source project. There most assuredly will be versions > beyond 4.2, and we're committed to making them better with every > release. > > Which brings me to the Subject of this request for community input. One > of the major strategic goals of the release after 4.2 is to make sipXecs > simpler. Simpler to install, simpler to administer, simpler for end > users to use. Nice goal, huh? Motherhood is good, Apple Pie is very > good, and Simplicity is great - I'm glad we all agree :-) > > Now comes the challenging part - what is simplicity? We'd like to hear > what the community thinks... > > Specifically, what are your top 5 suggestions for how to simplify > sipXecs? For this thread, we are _not_ asking for what your favorite > missing power telephony features are (we'll do some of those too) - we > want to know how to make the features we've got easier to understand and > use. What are the things that you have to jump through hoops to do > (especially if you have to do them more than once)? What are the things > you constantly have to explain to users? What are the things you know > how to do but it's just a little irritating ever time you have to do > them? Try to think back to your first experiences - what was hard > before you knew what you were doing (newbies - this is your chance to > jump in and contribute even before you know what you're doing!) ? > > This is not like those dumb Microsoft advertisements where one doofus > after another takes credit for Windows 7 (really - would anyone actually > want to take _credit_ for Windows?) - we really want to know. > > I'm going to suggest one more thing for this thread - that developers > just read and not post. In particular, in this thread: don't explain > that something our users think is hard is actually easy, or tell them > why it's hard, or suggest how we might fix it, or chime in here and now > with your ideas. We'll have our turns to process all this more actively > later and elsewhere - this thread is about listening to our users pain. > Hear, be inspired, and get motivated. > > > > > _______________________________________________ > 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/ > > > _______________________________________________ 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/
