* Advanced audiocodes gateway configurations, such as manipulation tables. * Better CDR's. Right now I'm having to get our on-staff programmer to write me out a parser to sift through all the CDR records to generate a comprehensive report. * Voice notification of new voicemails, not just email. Some people don't have data or SMS on their phones. * Auto Attendant Dial by name directory is currently just bad, namely due to the 10 second delay issue. * make backup and restore a little more comprehensive, such as making sure all SSL certs are in order. * Wildcard SSL certificates. * Bring back the remote call forwarding restriction, sometimes there is a need to keep certain users from forwarding calls off-site. * Hunt group pickup code shortcut. A speed dial has to be used for hunt group pickup because users can't remember the entire *78XXXX pickup code. * Call pickup/hunt group pickup permissions. It is somewhat unnerving that anyone can set up a presence monitor on any extension they want to and intercept their calls. * Allow different alarms to be sent to different email addresses * (sipXconfig) Allow more than 20 phones/users to be displayed at one time.
+1 For end users: allow a different phonebook in the web portal than on the phone so the entire directory can be searched in the web portal but only a small departmental subset will be seen on the phone. * Better dial plans. The current ones are a bit watered down. * Transferring calls to park requires three button presses on Polycom handsets (transfer, blind, park button). Could this possibly be whittled down? * If a Jabra or Plantronics headset with EHS adapters is used on a phone with BLF then every time a BLF button shows a monitored extension to be ringing, the headset also rings. Polycom and Jabra have basically ignored me on this. I am almost 100% positive this has to do with the "alerting" state with enhanced BLF. * I've had to write EFK's for Intercom, Group Page, Transfer To Voicemail, and Blind Transfer on Polycom phones. Perhaps these could be included by default and turned on/off at the group phone level? * Allow for a pickup time shorter than 1 second for *78XXXX call pickup. Users are used to the call immediately being picked up on older systems. I have trained users to wait for the short "beep" sound but sometimes they forget :-( * Voicemail quotas so the packrats will get rid of voicemails from 5 years ago or archive them to their computer * 64 bit CentOS installation ISO. * Polycom config overrides upload. It's frustrating after a firmware update having annoyed users because their ringtone, background, etc. got reset. * Troubleshooting has got to become a bit easier. A scrolling CLI would definitely help. OK, that seems to be more than just a few. I'm sure there are more that I'm not thinking about right now. I'm really glad to hear Avaya is committed to the project. Josh Patten Assistant Network Administrator Brazos County IT Dept. (979) 361-4676 On 1/22/2010 3: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/
