3CX Update 9 RC2 Should Be Tested Before It Touches Production Calls
3CX V20 Update 9 Release Candidate 2 was published in May 2026 as one of the final steps before the Update 9 final release. The RC2 notes focus on smaller corrections, including Grok transcription language behaviour, a Windows installer dependency issue, archived recording downloads when transcripts already exist, and presence-view permission changes.
That sounds like a tidy release candidate. It still should not be pushed casually into a live phone system.
Why phone system updates need discipline
A phone system touches more daily work than people remember:
- inbound sales calls
- support queues
- after-hours routing
- call recordings
- SIP trunks
- mobile apps
- receptionist workflows
- voicemail and transcription
- presence and transfer behaviour
When an update changes AI transcription, routing behaviour, permissions, installers, or archived recordings, the safe approach is to test before production users discover the edge cases.
What to test
Before moving a production 3CX system to a release candidate, confirm the basic call path first:
- inbound call to main number
- outbound call through each SIP trunk
- queue call with agent answer
- transfer to another extension
- voicemail delivery
- recording playback and download
- mobile app registration
- desk phone registration
- presence visibility for normal users
- transcription language behaviour if AI transcription is enabled
If the system uses custom SIP trunk templates or non-standard routing, test those separately.
Release candidate does not mean production default
Release candidates are useful. They let administrators validate the upcoming release and catch issues before the final version lands.
But a release candidate is still a release candidate. For client-facing phone systems, the default should be caution unless there is a specific reason to adopt it early.
Good reasons to test early include:
- the update fixes an issue you are actively facing
- the business needs a new feature before final release
- the system is non-critical or has a maintenance window
- you have a rollback and backup plan
"It appeared in the updates screen" is not a good enough reason.
The practical takeaway
3CX Update 9 RC2 looks like a useful step toward the final Update 9 release, especially for environments using AI transcription and newer administrative features.
Just treat it like phone-system change control. Backup first, schedule the window, test the call flows, verify recordings and permissions, then document the result.
The phones are too visible to update on vibes.
Source: 3CX Blog - V20 Update 9 Release Candidate 2.
