From: Alfred Campbell [mailto:[email protected]] 
Sent: Wednesday, March 17, 2010 6:21 PM
To: Picher, Michael
Cc: [email protected]
Subject: Re: [sipX-dev] FreeSWITCH based ACD replacement --DEAD??

 

On 3/17/2010 5:47 PM, Picher, Michael wrote: 

Nobody responded to the bottom post, so the top post is sure to raise
some ire...

 

What is to become of the ACD?  Fix it or trash it?

 

From: [email protected]
[mailto:[email protected]] On Behalf Of Picher,
Michael
Sent: Sunday, March 14, 2010 9:23 AM
To: Al Campbell; [email protected]
Subject: Re: [sipX-dev] FreeSWITCH based ACD replacement --DEAD??

 

 

 

From: [email protected]
[mailto:[email protected]] On Behalf Of Al Campbell
Sent: Friday, March 12, 2010 7:50 AM
To: [email protected]
Subject: Re: [sipX-dev] FreeSWITCH based ACD replacement --DEAD??

 

On 3/11/2010 11:27 AM, James R wrote: 

In September/October of last year, information on the new release of the
ACD was available.  There were itemized tasks with progress details of
each task.  It was XX-6438, but that task doesn't seem to exist anymore.
The first link below is broken now.

I understand Martin Steinmann has left since the Avaya acquisition, and
I'm curious if the project is still moving forward with as much steam?
I spoke with some folks at the Avaya/Nortel Enterprise Solutions
Integrated Roadmap Seminar who believe things are moving forward..  but
I'm really curious if the developers are being pulled away to work on
the Aura architecture now. 

We are having problems with the 4.0.4 release running a WinSIP load test
against 15 agents and only a few calls in queue, after about 1 day the
ACD stops sending calls to the agents.  We are having a tough time
digging through logs to pinpoint what initiates this failure... In order
for us to move this into production we will need to reboot the ACD
nightly..

We need to make a decision with sticking with the main branch, or
pursuing the VoiceWorks ACD option...  If the truth is that Avaya won't
be putting resources towards sipX ACD, then the VoiceWorks option will
be an easier decision.


Information on the new ACD that seems lost now:

from XX-6438 task  http://track.sipfoundry.org/browse/XX-6438  also
here:  http://sipx-wiki.calivia.com/index.php/ACD_Proposed_Architecture
and here:  http://sipx-wiki.calivia.com/index.php/ACD_Features

 

FreeSWITCH based ACD replacement

 

In order to address both feature and scalability shortcomings of the
current sipXtapi based ACD implementation, the current ACD will be
rewritten to utilize the FreeSWITCH media / call control subsystem. The
new implementation will be a drop-in replacement for the existing ACD,
providing the end user with the same set of features and provisioning
model. In the initial release, no new features will be added, but
instead will address some major shortcomings of the existing
implementation such as the ability for an agent to transfer a caller.



Thanks,
James

 
 
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/


The project is still full steam ahead in Avaya. Focus is on Small Medium
Enterprise so some of the features we were working on before have been
re-prioritized. If you watch the check-ins and Jira activity you will
see all the work being done. Reality is we are trying to get this
pregnant release finished up so we can move on to new content. If you
are a Nortel/Avaya customer contact support as what you are describing
isn't what we see in QA load tests.  If you are open source I would
suggest putting some information on the dev list regarding your issue. 

As for the New ACD it may or may not come. Once the new release (in Jira
called New Release) is planned we will see where that fits.

[[Michael Picher]] 

I'd suggest then if we can't make ACD work in the next release that it
should get ripped out of 4.2 because in its current state it is useless.

I was afraid this would happen when it got pushed to 5.0 and then I
couldn't find the project track.

*sigh*

Mike

 

 

We have fixed several issues related to ACD. A couple in the 4.0.X
branches. This was for a couple commercial customers who use the ACD. 

I am guessing your big complaint is the transfer issues or are there
others? 

At this point there will not be a new ACD anytime soon.  So I guess you
raise an interesting question.  Is whats out there so useless that
nobody can get any value out of it? I do for a fact know of a couple
customers who use it however I can see with the transfer limitations it
being a landmine.

 

 

 

The transfer limitation is a HUGE problem.  IMHO it almost makes it
unusable in most cases.

 

The other big issue was the problem with user agents getting signed out
but showing as signed in.

 

Mike

_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to