I think what is missing are the details of what is in 4.4 versus what is in 4.6. For example, I think there are limitations for agent and supervisor login right now, as well as access to any of the reports that will be available in the basic Call Center.
It's my understanding the licensed version from eZuce will have a more capable reporting package, but I suspect those using the 4.4 will need to weigh if they are able to move past 4.4 at this time, or if a future release meets their requirements more thoroughly. >From a project management standpoint, it seems that the right thing to do was to focus on next generation ACD capabilities, and not waste energy on one that is extremely limited in features, has known issues that are limiting it, and is bound for the bone yard....... Thanks for the info Douglas. Maybe someone that relies on Legacy ACD can put forward questions about features they currently use to see if they are supported, and when. From: sipx-users-boun...@list.sipfoundry.org [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Douglas Hubler Sent: Sunday, August 12, 2012 5:58 PM To: Discussion list for users of sipXecs software Subject: Re: [sipx-users] ACD (Legacy) not working in 4.6 On Sun, Aug 12, 2012 at 7:06 PM, Todd Hodgen <thod...@frontier.com> wrote: Is there a strategy for those that use the ACD as far as migration from Legacy ACD to OpenACD Call Center? I don't use it, but it seems that going from 4.4 using ACD, to 4.6 with Call Center, there are some holes with regards to agent login-logoff, reports, etc. Maybe the development team can make some recommendations to those that rely on the Legacy ACD - do they wait for 4.6 release, or will there still be some shortfalls that need to wait for another future release in order to have a stable ACD environment that meets the current specs of the legacy ACD. I've not seen a discussion on this topic on the list, and I suspect it would be beneficial to those that use ACD. The plan all along was to overlap the two, but there was so much change to 4.6 that we couldn't keep up the work to continue to port ACD. It was a tough decision, and it probably wasn't communicated to list, sorry about that. The code is all there and it wouldn't be impossible to resurrect it for 4.6 if someone was so inclined. MRTG was the other causality of the migration, i'm pretty sure we covered that.
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
