Thank you all for the great feedback! And thank you for the Xmas to do list info@matic-tec
We we're wondering what we could do on our Xmas holiday but you have solved that problem!
But seriously, I will try to answer as many questions as possible. Many of the things you have raised are in the works for the release version or update 1/2. Here goes:
1. First off the CFD and Call API. We are well aware that programmability is key for larger installs and so we have set about to drastically improve this part of 3CX. We are working on a solution which will be infinitely more powerful, performant and integrated natively into the PBX. Finishing this will take at least another few months - its going to be worth the wait. Meanwhile you can use the new script IVR which allows you to script at least 90% of what the CFD could do. Furthermore of course you can use 15.5 as its fully up to date and supported.
2. In addition we want to create more configurability in the IVR and the queue so that many call scenarios can be done without any scripting at all.
> re CFD and API - please await a new post (we will try to do this before xmas, but more likely second week of January) and continue the discussion on that thread. Rest assured that scripting / programmability /API is a focus point for us. Meanwhile do feel free to prepare some things that you do with the CFD so that we can discuss those and show you how they can be done in the new solution.
3. Outbound caller ID - we are working on making this much more configurable (just like inbound caller ID) and should be out in an update soon after release.
4. Web client - Not in this alpha but in alpha 2 / beta 1 (hopefully out before xmas), you will see that we have added BLF configuration from the web client as well as a new switchboard view. We will also be working on a new compact view which allows you to replace the windows manager view.
5. Provisioning options including OPUS - Re Opus be aware that some yealink models dont reliably implement it, even if it says so on the brochure/website. We will be rechecking with newer firmwares but when we released OPUS support some phones had problems with it (it has to work across the board and interop with different phones). We did not disable it for fun.
> lets start a new thread about provisioning options.
6. I did not understand this comment "If I use the webclient as "Chrome App" (create link) and i get a windows notification for a new chat for example and click on answer, a new chrome tab opens, but not the webclient on the "Chrome App" - Let us know as we are working to improve usability of web client and also considering a chrome extension.
7. TAPI will remain available for windows client but you really should look for modern solutions that implement a REST Web API because this dinosaur technology will go away at some point.
I hope this helps!