Purpose and location
Update PBX core, FreeSWITCH and add-ons through signed, compatible releases.
Open Platform → Update Center. The available controls depend on the active edition, module entitlement, role and tenant scope.
Before you start
Platform changes can affect every tenant. Confirm a recent verified backup, an audit owner and a maintenance window whenever the operation can restart services or change entitlement.
Capture the current value or export the affected records before a bulk or routing change. This gives the operator a precise comparison point and makes a supported transaction undo easier to assess.
Step-by-step workflow
Complete the steps in order. Do not combine an initial configuration with unrelated cleanup; small, attributable changes are easier to test and reverse.
- Refresh and verify the signed catalog from downloads.relaypbx.com.
- Review Core, FreeSWITCH and add-on compatibility and restart impact independently.
- Create and verify a fresh backup.
- Apply in a maintenance window, watch the update job and run post-update calls.
- Use the recorded rollback point if any mandatory acceptance check fails.
Field reference
Use the reference below while completing the form. Fields hidden by edition, module entitlement or role are intentionally unavailable to the signed-in user.
- Component
- RelayPBX Core, FreeSWITCH engine or individual add-on.
- Installed / available
- Current immutable package version and the newest compatible signed release.
- Channel
- Stable or approved release stream.
- Signed catalog
- Trusted release manifest and package digests verified before a job can start.
- Compatibility
- Required core and dependency versions.
- Restart impact
- Services or call traffic affected.
- Update history
- Audited state, timestamps and safe failure detail for every job.
- Rollback
- Supported previous image/package and the verified restore point.
Acceptance checks
A saved record is only the beginning of validation. Run every relevant check below and retain the call-session ID, time and result when telephony is involved.
- Confirm an unsigned, altered or incompatible package is rejected before installation.
- Verify registration, inbound/outbound calling, RTP, DTMF and remote BYE after the update.
- Perform a release-candidate drill that proves backup and rollback on a disposable or approved empty production host.
Common mistakes and safe recovery
If a check fails, stop adding changes. Restore the previous value or use a supported transaction undo, regenerate PBX configuration, then repeat the smallest failing test.
- Never bypass signature or compatibility checks to force a release.
- A FreeSWITCH update can interrupt active calls; drain traffic when the release requires a telephony restart.
What to include in a support case
Provide the tenant, module and object name, local time with timezone, expected result, observed result and the most recent successful state. For a call problem, include the logical call-session ID and the redacted SIP/SDP text diagnostic before requesting PCAP.
Never paste passwords, private keys, raw license payloads or unredacted customer media into a ticket. Use the one-time diagnostic grant and attachment controls when support requests additional evidence.