Is v16 stable?

Status
Not open for further replies.

Andy294

Forum User
Joined
Mar 25, 2019
Messages
7
Reaction score
0
Hi,
I would open this post with a specific purpouse: anyone that (on purpose or by mistake) installed v16 write here if in their opinion is v16 stable and free from big problems.

Can someone give us this information?

Thank you.
 
As with all forums, you will only hear about things not working - just browse this forum and you will see issues what people are experiencing.

People without issues, will not access this forum and say how great it is


Note : V16 is still in RC version - https://www.3cx.com/blog/releases/v16-release-candidate/
 
  • Like
Reactions: StefanW
  • Like
Reactions: StefanW
And further more if you read the forums in the BETA/RC blog posts you will see many folks say it's working fine. I haven't seen anyone complain about stability and typically (other than the initial switch to Linux) stability hasn't really been a problem with 3CX. Pretty much all of the complaints I've seen have been licensing questions regarding the feature changes, and a 'fix' for queue call back handling resulting in higher (true) SC counts.
 
  • Like
Reactions: StefanW
Lots of complaints about release notes not actually saying CFD is removed...
 
  • Sad
Reactions: StefanW
This update is a giant middle finger to anyone using call flows. As far as i can tell 3cx wanted people to get pissed off, given how they've handled this so far.

How do you figure? It was stated months ago that CFW was getting changed in v16 and weeks ago that it wouldn't be available in v16 at launch. I mean who upgrades on day 1 anyways? By the time most serious companies let the release soak and plan an upgrade the new CFD would be available. Don't really see any issues.
 
CobaltIt,
I've seen this info because I was active in the forums - but where was the specific info in the v16 release that CFD is not available? The CFD webpage is still active (https://www.3cx.com/phone-system/call-flow-designer/) with download links... which probably lead to v16. They did mention "Added new 3CX Call Flow Service." - but nothing about removing and breaking existing setups. Playing devils advocate as I am not using them - but if I were... in all the reading I did about this release, did not see "CFD removed".

https://www.3cx.com/blog/releases/v16-release-candidate/
https://www.3cx.com/blog/releases/company-communications-v16/
https://www.3cx.com/ordering/pricing/ (still listed here - 'Call Flow Designer')
 
So release notes are at release time thing. Not saying it shouldn't be in there but 3CX has been saying for months in the blog posts which link to forum threads about CFD changing and needing to be re-written for the new interface and then around the beta release or shortly there after that it wouldn't be available at launch but rather Update 1. For the folks that auto-updated without having automatic updates set it sucks, but for everyone else, considering the live launch webinar was today and the the CFD time line was explained, there really is no one who should have updated already if CFD's are such an important part of the system folks should just do their due diligence.
 
Stated where? In the forums? Because it sure wasn't in the last partner email they sent out (which was when it was in Alpha, in 2018 Q4). Or do you mean the build notes/change log? Where it only says "Added new 3CX Call Flow Service" in the release candidate, but no mention of the removal of the original feature?

You're saying they were right to publish a production release of a product that silently and intentionally breaks features... because "who updates on day 1 anyways"? Wow.

So this is probably the most obvious blog post stating CFD will probably not be available before Update 1

https://www.3cx.com/blog/releases/designing-call-flows-v16/

However, it is probable that the new CFD engine will not be available before update 1 of v16. So if you depend on call flows you probably have to wait until update 1 before upgrading. This blog post serves to inform what is coming with that update.

3CX did not silently and intentionally break features. There were two different actions here. 3CX released v16 which was stated to not have CFD available. And then you either intentionally or accidentally upgraded to v16 which caused things to break. There is a small minority of folks who claim auto-updates were not enabled and it still upgraded but I haven't seen a 3CX response or confirmation that this happened or was possible. I know I don't have auto-updates enabled on any customer and we've had zero systems upgrade.

Change is always hard.
 
  • Like
Reactions: StefanW
No, I have no expectations for customers/end users. However, your tag says Gold Partner so yes I would think you would stay on top of things. I do because that's what my customers expect of me. And because of my due diligence none of my customers had problems but if they had, I wouldn't be on here complaining that 3CX broke something because I updated 3CX. While they have actually broken things before, this is not one of those cases. Now the queue call back fiasco due to the queue manager engine change is another story and that is a truly undocumented change. Could 3CX have done better, absolutely. Should it be in the change logs? Yes and I already stated that. But 3CX did not update your instances, you did. There's plenty of people still on v15.5 with working call flows. Heck I still have several customers on v14 because they didn't like the changes in v15. Measure twice, cut once.
 
Problems with Call Queues, out of hours schedules, random but often "this number is not know" on inbound calls. SSL changes proving impossible.

I strongly believe that the SSL mismatch, to which you have a own topic, is outside of 3CX. The prompt you refer to is not within 3CX which makes me believe that your SSL and not been contactable are connected by your network,isp etc... Confirming from our support and community team, office hours and queues are perfectly fine.
 
.... There is a small minority of folks who claim auto-updates were not enabled and it still upgraded but I haven't seen a 3CX response or confirmation that this happened or was possible. I know I don't have auto-updates enabled on any customer and we've had zero systems upgrade.

After investigating some reported cases it appears there was a 3rd party remote management solution installed on Debian by our customers (not included by 3CX) that was configured to run a system wide upgrade command on Linux.

For those affected: please check your machines to see if you had anything similar or any scheduled jobs that would issue an upgrade command since this will automatically force upgrade your PBX too, regardless of whether you enabled updates via our management console.
 
  • Like
Reactions: lead1
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,918
Messages
589,736
Members
164,792
Latest member
LBS Care