- Joined
- Nov 16, 2015
- Messages
- 20
- Reaction score
- 0
Here’s a draft for your post on the 3CX forum:
Hi 3CX Community,
We are currently running over five instances of 3CX across different countries/markets. All of these are self-hosted in our respective local data centers, and we operate on Professional Annual licenses. As a sales-driven company, 3CX is the backbone of our contact centers, and any downtime or untested changes directly impact our revenue.
To optimize our operations, we’ve built custom applications that deeply integrate with 3CX into our internal systems and workflows. These integrations are critical to our processes, but they require significant engineering effort to develop, test, and validate thoroughly before deploying to production. We have been testing these integrations with Version 20 in our staging environment, but they are not yet production ready.
Given that 3CX has announced the End of Life (EOL) for Version 18 by December 2024, I’m concerned about the following:
We understand the importance of keeping software updated, but with the engineering effort required to ensure our custom integrations remain intact, we need more time to transition fully to Version 20. Ideally, we’d like to migrate when our integrations are production-ready.
I would greatly appreciate guidance from the 3CX experts or anyone with experience in similar scenarios. Any advice on managing this transition or mitigating risks while staying on Version 18 beyond the EOL date would be invaluable.
Thanks in advance for your support!
Hi 3CX Community,
We are currently running over five instances of 3CX across different countries/markets. All of these are self-hosted in our respective local data centers, and we operate on Professional Annual licenses. As a sales-driven company, 3CX is the backbone of our contact centers, and any downtime or untested changes directly impact our revenue.
To optimize our operations, we’ve built custom applications that deeply integrate with 3CX into our internal systems and workflows. These integrations are critical to our processes, but they require significant engineering effort to develop, test, and validate thoroughly before deploying to production. We have been testing these integrations with Version 20 in our staging environment, but they are not yet production ready.
Given that 3CX has announced the End of Life (EOL) for Version 18 by December 2024, I’m concerned about the following:
- If we do not migrate by the EOL date, what will happen to our self-hosted instances?
- Will the systems continue functioning as they are without updates?
- Are there specific features or services that will stop working entirely after the EOL?
- Is there any risk of our Professional Annual licenses becoming invalid if we don’t migrate to Version 20 by the EOL date?
- What are the security implications of running an unsupported version (Version 18) beyond December 2024?
We understand the importance of keeping software updated, but with the engineering effort required to ensure our custom integrations remain intact, we need more time to transition fully to Version 20. Ideally, we’d like to migrate when our integrations are production-ready.
I would greatly appreciate guidance from the 3CX experts or anyone with experience in similar scenarios. Any advice on managing this transition or mitigating risks while staying on Version 18 beyond the EOL date would be invaluable.
Thanks in advance for your support!