Purpose and location
Block inbound or outbound numbers and patterns with tenant-aware priority.
Open Call management → Call Blocking. 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.
- Choose direction and scope.
- Enter an exact number or safe pattern.
- Select reject behavior.
- Test blocked and allowed examples before broad rules.
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.
- Direction
- Inbound, outbound or both.
- Match type
- Exact, prefix or approved regular expression.
- Action
- Reject, announce or redirect.
- Priority
- Order when several rules match.
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.
- Test an exact blocked number, a nearby allowed number and every pattern boundary.
- Confirm emergency patterns and administrator-approved exceptions cannot be shadowed.
- Verify the rejected call has an explainable cause in Calls & Reports.
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.
- Broad prefixes and regular expressions can block emergency or business-critical calls.
- Document the business owner and expiry date for temporary rules.
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.