If 3.10 was working for you I'd setup a separate 3.10 system and route ACD calls over to it.
I've stopped using ACD because of the problems with it and there is no work being done on the current ACD. There is work being done to replace it. Mike > -----Original Message----- > From: sipx-users-boun...@list.sipfoundry.org [mailto:sipx-users- > boun...@list.sipfoundry.org] On Behalf Of Sergio Cortes > Sent: Friday, June 04, 2010 12:09 PM > To: sipx-users@list.sipfoundry.org > Subject: [sipx-users] ACD sign-in fails > > Hi. > Im having some problems in the ACD using sipx version 4.2 > > Agents signed-in using sipXpresence (xml-rpc,calling to *88 or using > the web ui) are not being reflected in ACD (queue-statistics) even > when they are displayed as signed-in in the Agent-status. > > The ACD seems to work fine when the number of total agents in a queue > is low (20 or less), but as we add agents to the queue the process > starts to take longer, finally when the agents in a queue are 70 or > more the ACD no longer update the number of available agents in > queue-statistics. > > Here are the steps to reproduce this behavior: > > 1 - Add some agents to the queue (less than 20) > > 2 - Activate the ACD Server. > > 3 - Restart the afected services and wait for the "Running" status. > > 4 - Try to sign-in some of the agents added to the queue. The agents > should be present in the queue-statistics view and the file > "sipxacd_events.log" also displays the sign-in-agent event. > > 5 - Sign out the agents. > > 6 - Add more agents to the queue and repeat the process steps 1 to 5. > When the number of agents in the queue is 70 or more the > queue-statistics view stops updating the signed-in agents and the > file "sipxacd_events.log" no longer logs the sign-in-agent event. > > Once this problem is present cant be fixed, deleting agents from the > queue or creating another queue dont correct the problem. > > This problem was not present in version 3.10. But now is present in > all versions of sipx from 4.0 to 4.3 > > Someone else is having this problem or something similar? Any know > solutions or workarounds?. > Should i report this issue in the issue tracker. > > Thanks in advance > _______________________________________________ > sipx-users mailing list sipx-users@list.sipfoundry.org > 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 sipx-users@list.sipfoundry.org 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/
