Purpose and location
Require individual, shared-pool or global PINs for controlled call classes.
Open Call management → PIN Authorization. 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 hashed PIN identities or a reusable pool.
- Attach a policy to outbound patterns.
- Set retry and lockout limits.
- Verify audit attribution without exposing the PIN.
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.
- Mode
- Individual, pool or tenant-global authorization.
- Protected pattern
- Destination class requiring a PIN.
- Retry/lockout
- Failed-attempt limit and recovery interval.
- Account attribution
- User or account code recorded after successful authorization.
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.
- Place a focused acceptance call through the changed route.
- Confirm two-way audio, remote hangup and the expected module path 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.
- Saving a form is not proof that a call path works. Always validate the success path and its timeout or failure path.
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.