My 2 cents... bear in mind that I'm still running 3.10.x so I may not be quite up to date on some things, plus I have a very small setup so once I'm done configuring thing I can generally leave them alone for months...
- Some extra back end options for phones, specifically volume settings. I have a bunch of Polycoms which work like champs, but when doing speakerphone it's almost impossible to get the gain settings right. My current course of action is to go into the shell, find the correct config file, then manually edit the various settings. Save, restart the phone, test. Someone else then goes into the GUI, changes some settings on that phone and then my config gets overwritten. I would imagine that I'm not the only one who has similar issues, especially when folks are using FXO gateways and the like. It would be great if there were some simple adjustments in the GUI. - CDR. I think that developing a full reporting system is outside the scope of the current roadmap. It's not a trivial thing, and there's lots of commercial packages out there. However, gettings those commercial packages to read SipX CDR format would probably be a challenge. I had a call reporting package which claimed to work perfectly with a Toshiba DK system and I spent 2 weeks doing nothing but deciphering the CDR output from that then sending off parts to the developers to prove to them that they had their format all wrong. How about having SipX "emulate" CDR formats... so, for example, I could have SipX output CDR in the same format as Definity G3. That format has been around for years so I would imagine it's pretty pervasive by now. - An "extras" section for gateway config. Let's say I've configured an Audiocodes gateway via the GUI. For whatever reason I go to Audiocodes for support and they tell me I need the line "Setting X = 1" in my config file. If I could just copy and paste that into SipX instead of messing with the file on the gateway that would be pretty nifty. I realize it's easy to do on the gateway itself, but then we have one config in SipX and a different one in the gateway which always makes for an entertaining day. Thanks Pete Burgess On 1/24/2010 1:21 PM, [email protected]<mailto:[email protected]> wrote: 1) 64 bit ISO install 2) Ability to automate and/or delegate CDRs. I either need to have a preset one emailed out to dept heads or give them the ability to log in and only see their employees data 3) PIN numbers for long distance authorization 4) Clean up CDR data. This has been said already. There is too much work to get them in a good format. 5) Better GUI based troubleshooting/diagnostics. 6) Sorry, had to add one more. Check box type option when user forwards to internal extension. This would let them select where it goes if nobody answers. Sometimes they want it to come back to their voicemail, sometimes they want it to go to the forward recipients voicemail. It would be nice for them to be able to accomplish this with a check box instead of explaining they need to ad 8XXX as a second forward if they want it to go to the other persons voicemail if nobody answers. **Not included because I was told it is in 4.2 already. Better tools for external SSL certs. Sent via BlackBerry from T-Mobile -----Original Message----- From: "Scott Lawrence"<[email protected]><mailto:[email protected]> Date: Fri, 22 Jan 2010 16:23:34 To: sipXecs users<[email protected]><mailto:[email protected]> 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]<mailto:[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]<mailto:[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/
