Sweet Sixteen… 3CX v16 ALPHA

[nb]

We chose this platform because we could customize the call flow through the CDF apps.
Now you tell us that they were removed from version 16 !!!
I'm expect the backwards compatibility with what has already been developed (spending much time and money), waiting to migrate to the new scripting solution that you have introduced in this version.

Massimo

The new scripting solution introduced is the standard the world uses - You dont need to spend time and money to learn. Its Batch files, Python, powershell etc.
That's why we removed it - because the cfd had a learning curve.
Give me an example of what your current cfd does let me see.

 

[maxmino]

The new scripting solution introduced is the standard the world uses - You dont need to spend time and money to learn. Its Batch files, Python, powershell etc.
That's why we removed it - because the cfd had a learning curve.
Give me an example of what your current cfd does let me see.

Based on what you say, everything that now works in version 15.5 will no longer work in version 16 without having been given any notice regarding the decommission of this technology (voice apps).
I do not dispute the fact that you are introducing a simpler way to manage the call flow but I think it isn't correct to change on the fly a core feature of the product without giving proper notice to its customers and forcing them to either stay on an outdated platform or to have to re-engineer what has already been developed.
For example, Microsoft announced with the release of Exchange 2010 that with the next version would have decommissioned the public folders and discouraged the use of this feature but provided at least 3 years before removing such an important feature (which never happens because they reviewed their choice)

 

[nb]

Based on what you say, everything that now works in version 15.5 will no longer work in version 16 without having been given any notice regarding the decommission of this technology (voice apps).
I do not dispute the fact that you are introducing a simpler way to manage the call flow but I think it isn't correct to change on the fly a core feature of the product without giving proper notice to its customers and forcing them to either stay on an outdated platform or to have to re-engineer what has already been developed.
For example, Microsoft announced with the release of Exchange 2010 that with the next version would have decommissioned the public folders and discouraged the use of this feature but provided at least 3 years before removing such an important feature (which never happens because they reviewed their choice)

We released an alpha. We have couple of more alphas to go, beta, release candidates, final releases. This procedure will take 2 months for sure.
After this, to date, I have never seen an admin that goes running to update his production pbx when the alpha is released. People prepare themselves for the update.
Exchange 2010 is a completely different example, with a completely different user base. Plus Exchange is a humongous prehistoric whale compared to a tiny cfd script that sets a parameter to 1 and checks a number to a database.
So before you alarm yourself and the rest of the community, why don't you tell me what your cfd's do in point form so that we can help you prepare yourself by telling you how much time you need to convert your cfd into a script that is a couple of lines long.

 

[maxmino]

We released an alpha. We have couple of more alphas to go, beta, release candidates, final releases. This procedure will take 2 months for sure.
After this, to date, I have never seen an admin that goes running to update his production pbx when the alpha is released. People prepare themselves for the update.
Exchange 2010 is a completely different example, with a completely different user base. Plus Exchange is a humongous prehistoric whale compared to a tiny cfd script that sets a parameter to 1 and checks a number to a database.
So before you alarm yourself and the rest of the community, why don't you tell me what your cfd's do in point form so that we can help you prepare yourself by telling you how much time you need to convert your cfd into a script that is a couple of lines long.

It is not my intention to alarm anyone, the purpose of this thread is to understand in time the news that will be introduced, give their own suggestions and points of view.
I do not want to compare whales to scripts because it would not be correct, it was just an example to say that before abandoning technologies that were the basis of choices and comparisons with other platforms it would be appropriate to give more time and discuss with their customers who have invested time and money in your product.
Thanks for the feedback and we will update as soon as we can try the new features announced.

 

[Federico Moschini]

You can make a batch file, example start chrome.exe http://www.website.com
But then you need to pass return codes to explain to the ivr what and where it should route the call based on the exit codes.
We will release some samples soon.

Thank you and where I can put this batch file? I am using OVH server with Debian.

 

[Gioal]

The new scripting solution introduced is the standard the world uses - You dont need to spend time and money to learn. Its Batch files, Python, powershell etc.
That's why we removed it - because the cfd had a learning curve.
Give me an example of what your current cfd does let me see.

I want to know if the script can do this.

I have a CFD in operation that takes the ANI of an external incoming call, consult the 3CX call log and route the call to the last extension that called to that number. It will be possible to do this using new scripting?

 

[Gioal]

Another one:

It will be possible do parallel execution with script?
An example for this, play a music during webservice consult.

 

[plochu]

We released an alpha. We have couple of more alphas to go, beta, release candidates, final releases. This procedure will take 2 months for sure.

Maybe it is not right place and it will be off topic but I think that 3CX has a great problem to share informations about plans for the future. Almost 100% of my 3CX Phone System deployments and maintenances uses CFD and other ways of integration with external services.

Take a look at this picture that shows Ubuntu lifetime:

It would be very helpful if 3CX will be able to provide such information.
@Nick Galea, @nb please think about this - this can help to avoid a lot of stress

 

[Jeremy Bero]

Thanks for your comments safemode.
Copy blf to other extensions in the pipeline.
However something you might find interesting will be the ability to at least allow users to configure their own blf from the Webclient. This is coming in the next update.

I'm guessing user configuration of BLF is still only for Pro or better licenses?

 

[BrenttG]

I need to give whichever 3CX team member prepared the screenshots of the chat and sending documents some props for the names and companies used, Nice to see some fellow Nikola Tesla fans floating about. Nice little throw back there.

 

[tresearch]

I agree with what the other posters are saying regarding the CFD. It's a great tool to have and is the goal that most programmable voice systems long for. Look at any other "programmable voice" platform; they have a visual tool or are actively working on one (ever hear of Twilio?). It is extremely useful to be able to visually see the call flow rather than rely entirely on python or powershell. CFD apps can already launch scripts so what is the real benefit here besides 3CX corporate wanting to abandon development of the tool?

We are in the process of launching 3CX for a larger 128 SC client and need to rely on the CFD apps to replicate functionality they already have with their existing system. One such app is recreating the callback functionality but adding a message that can be left by the caller and automatically played to the extension that is being autodialed out by the callback dialer queue.

I also second the idea of not forcing us to move to the web client for everything. In a corporate environment it very useful having the softphone be its own software. This means the custom plugins for the softphone will go away and also that the softphone will just be lost in the sea of other Chrome tabs. Hopefully the web client is setup so that Chrome knows it can export it as an application so it can have it's own icon in the taskbar and ALT + TAB application switching.

 

[plochu]

So before you alarm yourself and the rest of the community, why don't you tell me what your cfd's do in point form so that we can help you prepare yourself by telling you how much time you need to convert your cfd into a script that is a couple of lines long.

@nb so maybe I will give and example of very simple but useful script in CFD that I'm using.
It is based on CFD and allows to Listen/Barge/Whisper other extension using any deskphone.


Variable1 is named "callflow$.ListenTo"



And in external script properties I have:


External script needs two parameters named ext1 and ext2 and is about 20 lines long but the most important is:
"PhoneSystem.Root.BargeinCall(ext1, ac, PBXConnection.BargeInMode.Listen);"

I think that you understand how it works.
Can You please give example how to do this using 3CX v16? I know you wrote that some examples will be avaliable soon but I'm really courious how to do this.

 

[clarityscg]

Not thrilled by the web client. Need Drop and Drag feature ... need to keep 3CX Phone

 

[safemode]

Not thrilled by the web client. Need Drop and Drag feature ... need to keep 3CX Phone

Drop and drag isn't an issue to add to modern web apps, it would be worth putting this as a post in the ideas forum, I would certainly vote for it.

 

[nb]

@federico - You will put it on the server. We will explain everything in the coming days. We will release an article.
@Gioal - Thanks for your current existing cfd examples. I will definitely use them in the samples. Prompt playback during script execution we do not have. I will consult internally.
@plochu - We need to improve this you are correct. Of course Ubuntu and other applications are completely different - with community support and thousands of maintainers worldwide, they are able to support OSs for longer terms. However we will try our best to inform the community. Also thank you for your CFD Sample. We will do our best to incorporate it in the samples soon. For sure in the coming days.
@Jereny Bero - Yes Pro and ENT
@BrenttG - thanks some humor is greatly appreciated right now..
tresearch - Thank you for your comments. We will provide as much help as we can. re webclient - We are working so the webclient is not lost in tabs as you correctly explained.

 

[hogan71088]

Has there been any functionality added to the wall board? Option for individual agent wall board statistics?

 

[TBWD]

Yes existing users will get upgraded...

Thank you for the update

 

[luckystrikes]

Looks amazing , go 3CX team your hard work puts everyone of us ahead of the game. @plochu I think it's unfair to compare 3CX dev to linux dev. The way the market is demanding innovation and the pace the team here is going deserves some applause

Could you provide some details on what you mean by this in call reports?

• Revised and optimized reporting engine towards standards-based reports.

 

[[email protected]]

We chose this platform because we could customize the call flow through the CDF apps.
Now you tell us that they were removed from version 16 !!!
I'm expect the backwards compatibility with what has already been developed (spending much time and money), waiting to migrate to the new scripting solution that you have introduced in this version.

Massimo

I fully agree to this. We have created some complex CFDs. We can solve it with a single IVR that calls one scipt.

 

[plochu]

@plochu I think it's unfair to compare 3CX dev to linux dev.

@luckystrikes I don't compare them to show weakness I don't compare them at all This was just an example of good practise. Every DEV needs to have own policy adapted to the software development methodology used. I do not require from 3CX to support parallel 2 LTS versions and have 3 other for testing... Just some information about product lifecycle and features roadmap will help us a lot.