Would be nice if this could be a springboard for an ACD replacement…
From: [email protected] [mailto:[email protected]] On Behalf Of Pawel Pierscionek Sent: Saturday, May 30, 2009 7:27 AM To: [email protected] Subject: [sipX-dev] Fwd: There is an ACD Queue License limit? Begin forwarded message: From: Paweł Pierścionek <[email protected]> Date: 29 maja 2009 19:42:00 GMT+02:00 To: Damian Dowling <[email protected]> Cc: sipx-dev <[email protected]> Subject: Re: [sipX-dev] There is an ACD Queue License limit? On 2009-05-29, at 18:03, Damian Dowling wrote: Paweł Pierścionek wrote: Can you confirm what you mean by a "hardcoded limit of 30 calls to ACD server". Does this 30 call limit mean that only a maximum of 30 calls can be queued at any one time, and if so what happens if you try to queue call 31? Queued + bridged to agents = 30. [ cut ] Is it possible to increase this limit? The reason I ask is that a max of 30 queued is a bit on the smallish side for us. Even if we split the queues and run a second ACD Server we could easily hit the 30 call limit on busy days. Damian You will have to create Your own binaries but they will not be stable. The limit is there for a reason. With the restrictions removed and other tweaks to the core libraries I get 50% chance of no audio for new calls with 100 agents talking :( I have created my own ACD implementation from scratch based on FreeSwitch for the purpose of having a stable sipXacd replacement for deployments in 100-500 range. It's feature complete but not out of internal tests yet so I have no magic solution for You at the moment :( 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
