Skip to content

Configure Pinsets

A Pin Set is a list of PINs used to gate access to outbound routes (or DISA, or some other feature). When a route is pin-protected, callers/users must enter a PIN before the call proceeds. Useful for tracking long-distance/international usage by user, or restricting access by code.

Before You Start

  • You know what you're gating (typically an expensive outbound route).
  • You have a list of PINs to issue (one per user, or shared codes).

Steps

Create the Pin Set

  1. Go to Trunk Attributes → Pin Sets.
  2. Click + Add Pin Set.
  3. Fill in:
    • Pin Set Description — e.g. International PIN.
    • PIN List — one PIN per line, 4-10 digits. e.g. 
      12345
67890
24681
      Each PIN can be tracked separately in CDR if Record In CDR is enabled.
    • Record In CDR — Yes (recommended) — logs which PIN was used per call.
    • Announcement — optional system recording played before the PIN prompt.
  4. Click Submit.
  5. Click Apply Config.

Apply to a route

  1. Go to Trunk Attributes → Outbound Routes → click the route to gate.
  2. Route Settings → PIN Set — pick your Pin Set.
  3. Click Submit → Apply Config.

Now any call using this route prompts for a PIN before completing.

Verify

From an extension, dial a number that uses the gated route. UnifiedBX should prompt for a PIN. Enter a valid PIN — call proceeds. Enter invalid — call rejected.

# In CDR, the accountcode field will record the PIN:
mysql -u root cdr -e "SELECT calldate,src,dst,accountcode FROM cdr ORDER BY calldate DESC LIMIT 5"

Common Issues

  • PIN prompt comes from a soft greeting that's wrong language. Customize the Announcement with a System Recording.
  • PIN doesn't track in CDR. Record In CDR is No, or you're checking the wrong CDR field. The PIN ends up in accountcode, not userfield.
  • User reads PIN aloud — replay attack. Pin Sets aren't a security boundary; they're a tracking mechanism. For real authn, use Class of Service + per-extension restrictions.
  • Forgot which PIN belongs to whom. Pin Sets don't store names. Maintain a separate spreadsheet mapping PIN → person, or use one PIN per user with the PIN being a memorable code.