Purpose and location
Isolate access to routes, number patterns, feature codes and services.
Open Call management → Class of Service. The available controls depend on the active edition, module entitlement, role and tenant scope.
Before you start
Write down the current source and destination path before editing it. Keep a registered test extension, a rollback destination and Calls & Reports open for validation.
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.
- Create a restrictive baseline.
- Allow required route and feature groups.
- Assign it to service plans or extensions.
- Test an allowed and denied number.
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.
- Routes
- Outbound routes available to members.
- Patterns
- Allowed or denied number classes.
- Feature codes
- PBX service codes exposed to members.
- Assignments
- Plans and extensions using the class.
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.
- Call one allowed and one denied destination from an assigned extension.
- Verify disabled feature codes are rejected even when dialed directly.
- Check that moving an extension between plans updates its effective class of service.
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.
- Start restrictive and add explicit access; a permissive default is difficult to audit.
- Emergency routing must remain governed by the dedicated emergency policy.
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.