I'm not usually one to play by the rules. :-) -----Original Message----- From: Tony Graziano [mailto:[email protected]] Sent: Saturday, January 23, 2010 8:14 AM To: Picher, Michael; [email protected]; [email protected] Subject: Re: [sipx-users] Simplify, Simplify, Simplify
You went over 5. 3 demerits. ============================ 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/ ----- Original Message ----- From: [email protected] <[email protected]> To: Scott Lawrence <[email protected]>; sipXecs users <[email protected]> Sent: Sat Jan 23 08:06:43 2010 Subject: Re: [sipx-users] Simplify, Simplify, Simplify I'll come at this from 'not the novice' standpoint... I think, installation is pretty darned easy at the moment... the only tricky part is the wording of the DNS and DHCP questions. But really, we're talking 15 minutes to a running system at this point. There are a few things that have been mentioned that will help simplify the system (not in any particular order): 1. Bring logging out to the GUI / integrate sipXviewer into the GUI. 2. Allow users to use an IP address as their SIP domain. It seems like people have a tough time handling the simple concept of DNS. Yes, I understand it limits failover / flexibility. I'd still use DNS, but I'm talking about the noobs... and those coming from the * world. 3. Allow for an easy change to the SIP Domain. This goes hand in hand with #2, because people will realize that DNS is better. 4. Bring DHCP, DNS & NTP Management out to the GUI. Yea, it's easy stuff and you can install webmin to do it... but if you truly want an appliance this is where you have to head. 5. Add UPS management in to the system. 6. Figure out how to utilize Sangoma / Digium cards (this will help with some of the gateway mysteries). 7. A better hunt group setup would be really nice. If I want to ring one phone, bring in two more (in addition to the first) and then add two more (including the first 3), I can't do that. 8. The ability to have LIVE DAYTIME ATTENDANTS from AutoAttendant dial plans so that emergency/holiday AA's can be used. Thanks Scott & the Dev team. Mike -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Scott Lawrence Sent: Friday, January 22, 2010 4:24 PM To: sipXecs users Subject: [sipx-users] Simplify, Simplify, Simplify 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/ _______________________________________________ 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/
