Purpose and location
Inspect signed entitlements, limits, activation state and renewal dates.
Open Platform → License & Edition. 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.
- Verify installation identity.
- Select Upgrade edition to open the customer portal with this PBX preselected.
- Compare the higher edition, capacity, support and current-subscription credit before payment.
- Activate the one-time code in the existing PBX or import a signed offline license.
- Review module and capacity entitlements.
- Resolve expiry before grace mode ends.
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.
- Edition
- Free, paid package or custom entitlement set.
- Installation ID
- Stable identity bound to the deployed instance and passed to the upgrade wizard.
- Upgrade edition
- Opens the authenticated customer portal without reinstalling or replacing PBX configuration.
- One-time activation code
- Single-use code issued after payment and accepted only by the target installation.
- Entitlements
- Modules and capacity limits authorized by the license.
- Status
- Active, grace, expired or validation error.
- Renewal
- Subscription period and next renewal date.
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.
- Verify the edition badge, enabled modules and capacity limits match the purchased order.
- Switch to a Community test license and confirm paid pages and APIs are denied.
- Simulate license-service loss and confirm enforcement fails closed without interrupting established calls.
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.
- A menu item is not entitlement enforcement; the backend must reject every unlicensed operation.
- Never edit signed license payloads or copy an installation-bound license to another host.
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.