Pawel, This is great! Thank You! We are willing to give this a try. I am curious what kind of hardware you were running sipX on when you had the audio issues at 300 agents. Initially our goal is around 150 agents, so hopefully we will be ok for now. Eventually we would like to scale this to a few thousand agents.. even if we can do that cleanly on multiple ACD servers.
We are sort of stuck right now with 4.0.0... since the ANI isn't getting passed properly (http://track.sipfoundry.org/browse/XX-5648), this really blows up our transfers/call completion (We have billing & routing issues without the customers ANI on the transfer call leg). We are considering going back to 3.10 just to get this functionality back... but if we go back, we can't move ahead with your RPM's.... Ugh! I wish XX-5648 got into 4.0.1! Thanks again! (oh also thanks for the ACD wallboard, that works great) James 2009/6/19 Paweł Pierścionek <[email protected]> > > > > I can build a custom RPMs for You with this limit increased to like > 600 calls + other tweaks that > allow the sipXecs internal message queue to survive increased number > of calls/agents in ACD. > > But : > > - this will not make the ACD any more stable > - You'll have to wait 3 seconds times number of agents before the > server becomes operational each time You activate a new config > - All Your agents will still have to logout/login after each config > activation > - Also I am getting errors with port allocation for RTP streams that > results in one way audio. This is with 300 agents talking. Had no time > to do bisecting to see when the problems start to show up. > > > > Pawel, > >
_______________________________________________ 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/
