Yes, it seems from the chatter that they might be getting closer, but so far ... nothing there. FYI - I spoke to their team last November when they said V5 would be released in January ... still waiting. I'm progressing along with 4.3 still in test phase, but its been solid from testing and I plan to put a live client on it soon.We are still waiting with no further news about when v5.0 will be released. They had an announcement (changelog) about 5.0.(151) and also with 4.3.(240). So it seems there are no new github updates to the 4.3 branch also.
I am sure the CentOS fiasco threw a wrench into their plans for release. Some of the packages needed to install are only available for CentOS.Yes, it seems from the chatter that they might be getting closer, but so far ... nothing there. FYI - I spoke to their team last November when they said V5 would be released in January ... still waiting. I'm progressing along with 4.3 still in test phase, but its been solid from testing and I plan to put a live client on it soon.
must be because with multi-tenant when tenant A is down, tenant B and tenant C is down also. At least they have consistent problem to fix.With cloud-based platforms down to a few bucks a month, I'm not sure why multi-tenant is that necessary any more. But... to each his own.
which goes back to this statementFor that there is white label and horizontal scalability
The only reason I can figure why multi-tenant is that necessary any more is because a person needs to have the same problem across all tenants. They must like having all their businesses calling their cell phone and complaining that phone service is down all at the same timeWith cloud-based platforms down to a few bucks a month, I'm not sure why multi-tenant is that necessary any more. But... to each his own.
One of my reasons for exploring this is that Kazoo has multi homed instances so if one goes down the other handles the load immediately. Also - when you are managing many PBX (let's say hundred or more) - when you need to make changes, its a pain in the butt to change all hundred PBX, whereas Kazoo allows you to do it quickly. Even if you were to use it as your carrier routing and then you make a change to carriers - just change in one place instead of 100. Right now, I plan to initially utilize it for failover for all my PBX, hopefully more later down the road. Also ... anyone that wants to know more details I endorse and utilize the services of @fmateo05. He understands many of the complexities associated with Kazoo.With cloud-based platforms down to a few bucks a month, I'm not sure why multi-tenant is that necessary any more. But... to each his own.
so you don't have to fwconsole ma upgradeall, reload, and sig-fix 2 times on 100 servers?With cloud-based platforms down to a few bucks a month, I'm not sure why multi-tenant is that necessary any more. But... to each his own.
That's what cron jobs are for.so you don't have to fwconsole ma upgradeall, reload, and sig-fix 2 times on 100 servers?

Moving back to another platform?
Give priority for eploring another solutions?
Link up your team and customers Phone System
Live Chat
Video Conferencing
Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.
Check your inbox!
We’ve sent you an email. Click on the button in the email body to verify your email address – (if you can not find it, check your spam folder).
Upon verification you will be directed to the 3CX setup wizard.