> > Interesting idea: are you thinking about sipXconfig UI for managing > that > ACD? You probably have 2 options: reuse existing UI or add a plug-in > for a > new one. Let me know on sipx-devel when you need some help with that. > D.
No help needed at this stage, currently my ACD has no extra options as it is plug&play. I reuse current UI and XML/RPC provisioning. Everything is done in PHP + postgres + FreeSwitch and no files get overwritten during RPM install. Only the original sipXpresence & sipXacd & agent & report are being disabled. The clustered version that will be Java + Tokyo Tyrant as a shared cache and this one will need some UI tweaking for cluster provisioning. But it will come after we finish JTAPI for FreeSwitch and only if my php prototype will be too slow to handle cluster. The only performance bottleneck is multi-site cluster-aware agent allocation everything else sucks into local FreeSwitch instance and can be scaled indefinitely. There are extra options already implemented (like line priority, MOH, etc) and am thinking of releasing a custom ISO with bug fixed FreeSwitch and several extra options inside UI so ppl can play with it without having to wait for all patches to reach branch or trunk even. Anyways You can track it @ my private wiki http://wiki.voiceworks.pl/display/ ~pawel/. All my ideas about making current ACD stable are there as well. Pawel, _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
