Discussion:
ACD (Legacy) not working in 4.6
Ali Dashti
2012-08-11 10:32:59 UTC
Permalink
Hi,
In
System -> Servers -> Experimental
When you enable ACD (legacy) and ACD Presence (Legacy); It give you an
"Configuration generation - Internal Error Null" message in Job Status.
Now when you try to activate the ACD it gives you this message in Job
Status: "ACD Server Configuration" and it Failed to start.

Any hint on this? Can we still work with the old 4.4 ACD?

Regards,
Douglas Hubler
2012-08-12 22:12:59 UTC
Permalink
Post by Ali Dashti
System -> Servers -> Experimental
When you enable ACD (legacy) and ACD Presence (Legacy); It give you an
"Configuration generation - Internal Error Null" message in Job Status.
Now when you try to activate the ACD it gives you this message in Job
Status: "ACD Server Configuration" and it Failed to start.
Any hint on this? Can we still work with the old 4.4 ACD?
No, we need to remove ACD. You need to use the new Call Center feature.
Todd Hodgen
2012-08-12 22:43:13 UTC
Permalink
4.6 is not a stable product release yet. It would seem that if you want to
use the old legacy ACD, you should remain on 4.4. It's a stable release.

-----Original Message-----
From: sipx-users-***@list.sipfoundry.org
[mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of Douglas Hubler
Sent: Sunday, August 12, 2012 3:13 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] ACD (Legacy) not working in 4.6
Post by Ali Dashti
System -> Servers -> Experimental
When you enable ACD (legacy) and ACD Presence (Legacy); It give you an
"Configuration generation - Internal Error Null" message in Job Status.
Now when you try to activate the ACD it gives you this message in Job
Status: "ACD Server Configuration" and it Failed to start.
Any hint on this? Can we still work with the old 4.4 ACD?
No, we need to remove ACD. You need to use the new Call Center feature.
Tony Graziano
2012-08-12 22:56:48 UTC
Permalink
and we need to pull out all the SIPXACD_HISTORY database and related stuff
too.
Post by Douglas Hubler
Post by Ali Dashti
System -> Servers -> Experimental
When you enable ACD (legacy) and ACD Presence (Legacy); It give you an
"Configuration generation - Internal Error Null" message in Job Status.
Now when you try to activate the ACD it gives you this message in Job
Status: "ACD Server Configuration" and it Failed to start.
Any hint on this? Can we still work with the old 4.4 ACD?
No, we need to remove ACD. You need to use the new Call Center feature.
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/
--
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: ***@voice.myitdepartment.net
Fax: 434.465.6833
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~

Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
2013!
<http://sipxcolab2013.eventbrite.com/?discount=tony2013>
--
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: ***@voice.myitdepartment.net

Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net
Todd Hodgen
2012-08-12 23:06:46 UTC
Permalink
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.



From: sipx-users-***@list.sipfoundry.org
[mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of Tony Graziano
Sent: Sunday, August 12, 2012 3:57 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] ACD (Legacy) not working in 4.6



and we need to pull out all the SIPXACD_HISTORY database and related stuff
too.
Post by Ali Dashti
System -> Servers -> Experimental
When you enable ACD (legacy) and ACD Presence (Legacy); It give you an
"Configuration generation - Internal Error Null" message in Job Status.
Now when you try to activate the ACD it gives you this message in Job
Status: "ACD Server Configuration" and it Failed to start.
Any hint on this? Can we still work with the old 4.4 ACD?
No, we need to remove ACD. You need to use the new Call Center feature.
_______________________________________________
sipx-users mailing list
sipx-***@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
--
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: ***@voice.myitdepartment.net
Fax: 434.465.6833
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~



Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
2013! <http://sipxcolab2013.eventbrite.com/?discount=tony2013>




LAN/Telephony/Security and Control Systems Helpdesk:

Telephone: 434.984.8426

sip: ***@voice.myitdepartment.net



Helpdesk Customers: http://myhelp.myitdepartment.net

Blog: http://blog.myitdepartment.net
Tony Graziano
2012-08-12 23:31:07 UTC
Permalink
I think there should be a generic "readme" for anyone moving from 4.4 to
4.6, period.
Post by Todd Hodgen
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.****
** **
*Sent:* Sunday, August 12, 2012 3:57 PM
*To:* Discussion list for users of sipXecs software
*Subject:* Re: [sipx-users] ACD (Legacy) not working in 4.6****
** **
and we need to pull out all the SIPXACD_HISTORY database and related stuff
too.****
****
Post by Ali Dashti
System -> Servers -> Experimental
When you enable ACD (legacy) and ACD Presence (Legacy); It give you an
"Configuration generation - Internal Error Null" message in Job Status.
Now when you try to activate the ACD it gives you this message in Job
Status: "ACD Server Configuration" and it Failed to start.
Any hint on this? Can we still work with the old 4.4 ACD?****
No, we need to remove ACD. You need to use the new Call Center feature.
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/****
****
** **
--
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: 434.984.8430
Fax: 434.465.6833
~~~~~~~~~~~~~~~~~~
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~****
** **
Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
2013!
<http://sipxcolab2013.eventbrite.com/?discount=tony2013>****
** **
LAN/Telephony/Security and Control Systems Helpdesk:****
Telephone: 434.984.8426****
** **
Helpdesk Customers: http://myhelp.myitdepartment.net****
Blog: http://blog.myitdepartment.net****
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/
--
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: ***@voice.myitdepartment.net
Fax: 434.465.6833
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~

Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
2013!
<http://sipxcolab2013.eventbrite.com/?discount=tony2013>
--
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: ***@voice.myitdepartment.net

Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net
Douglas Hubler
2012-08-13 00:58:03 UTC
Permalink
Post by Todd Hodgen
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.
Todd Hodgen
2012-08-13 02:02:13 UTC
Permalink
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-***@list.sipfoundry.org
[mailto:sipx-users-***@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 <***@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.
Ali Dashti
2012-08-13 06:13:48 UTC
Permalink
I agree with you, I think eventually the new Contact Server or the eZuce
version works better but for now there are some limitations that prevents
me from using the new ACD.

Specially the lake of showing the DNID when the call reaches any agent
(which I have posted in separate post as well!). I think what happens is
the DNID changes to the agent's extension number when transferred our of a
queue!

Some documents would be very helpful on Contact Server.

Thanks guys,
Post by Todd Hodgen
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.****
** **
*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****
** **
****
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
List Archive: http://list.sipfoundry.org/archive/sipx-users/
Matt White
2012-08-13 20:39:17 UTC
Permalink
Post by Todd Hodgen
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.
Post by Todd Hodgen
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.
Post by Todd Hodgen
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




..
Post by Todd Hodgen
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.

For us the removal of the "classic ACD" has been a real show stopper for
our clients in regards to 4.6.
Right now we are telling our clients we will not be moving any ACD
clients to 4.6. Rather we are looking to move them to alternative ACD
platform.

We have some very heavy ACD clients and the new features of OpenACD
don't fit the use pattern and unfortunately leave too much to be
desired.

-M
Michael Picher
2012-08-13 21:41:45 UTC
Permalink
We're really looking to a fancy hunt group app to meet the needs of those
who think they want an acd. Unfortunately it isn't ready yet.

--------------------------------------------------------------------------------------
Michael Picher

"There are 10 types of people in this world, those who understand binary
and those who don't."
Post by Todd Hodgen
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.
Post by Todd Hodgen
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.
Post by Todd Hodgen
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……………..
Post by Todd Hodgen
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.


For us the removal of the "classic ACD" has been a real show stopper for
our clients in regards to 4.6.
Right now we are telling our clients we will not be moving any ACD clients
to 4.6. Rather we are looking to move them to alternative ACD platform.

We have some very heavy ACD clients and the new features of OpenACD don't
fit the use pattern and unfortunately leave too much to be desired.

-M

Loading...