Skip to content

Run a Pinset Report

The Pinset Report shows usage history for PINs configured in Trunk Attributes → Pin Sets — which PIN was used, when, who dialed (extension), and what was dialed.

Before You Start

  • Pin Sets are configured (see Configure Pinsets).
  • The relevant Pin Set has Record In CDR = Yes.

Steps

  1. Go to Reports → Pinset Reports (or Reports menu — name may vary slightly).
  2. Filter by:
    • Pin Set — the named set to query.
    • Date Range.
    • PIN — specific PIN value.
    • Extension — extension that dialed.
  3. Click Search.
  4. Results show calldate, src extension, dst (number called), PIN used, duration.

Use Cases

  • Audit international call usage by user. Filter by Pin Set = "International PIN", group by PIN.
  • Investigate a billing dispute. Look up a specific PIN over a billing period.
  • Detect a leaked PIN. Filter by PIN — if it's used from an unexpected extension or off-hours, it may be compromised.

Direct DB Query

PIN usage is in CDR's accountcode column when Record In CDR is on:

mysql -u root cdr -e "
  SELECT calldate,src,dst,duration,accountcode
  FROM cdr
  WHERE accountcode IS NOT NULL AND accountcode != ''
  ORDER BY calldate DESC LIMIT 100"

Common Issues

  • No data shows. Record In CDR is No on the Pin Set. Re-enable, but historical data won't backfill.
  • PIN appears in CDR but not in report. The report module may filter to specific Pin Sets — confirm the Pin Set is selectable in the dropdown.
  • Same PIN used by multiple people. Pin Sets are tracking, not authentication. To attribute calls to people, issue one PIN per person and maintain a name-to-PIN map outside the system.