On 2009-06-19, at 18:07, James R wrote:
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.
This was a lab setup, three quad core desktops. One with freeswitch
simulating a 1000 registered agents + call injector script, one with
oreka recorder to monitor call quality and one for sipX.
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)
I have new RPMs finally and they are being tested as we speak. Will
upload them to our colo later in the day using our 21st Century
Internet access of 512kbps :((((((
As a bonus the patched sipXacd RPM along with some config tweak will
be XX-5648 free :)
Ungly hack but serves as temp workaround. I am curious as to how this
one is going to be resolved the proper way as I could think of any
clean and simple patch to work around the current sipxtapi behaviour.
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/
