Caller ID Encryption & Masking in Issabel PBX and Free PBX

This project implements Caller ID Encryption and Masking in Issabel PBX for secure handling of inbound and outbound calls across Japan, USA, and Germany. The objective is to ensure customer privacy, prevent data leakage, and provide agents with a seamless way to handle callbacks without ever exposing the full phone number.

• Agents can currently see full customer numbers, which creates privacy and compliance risks.
  - Callback attempts may leak customer identity if full Caller ID is displayed.
  - Manual dialing of masked codes is error-prone and difficult to manage at scale.

• The PBX introduces a secure aliasing mechanism:
  1. **Inbound Calls:** When a customer calls, PBX generates a random alias or masked ID. The real number is stored in a secure mapping table inside PBX.
     - Example (Agent sees): Cust •••123 [742] or a random alias string.
     - Example (Dialable): *7742.
  2. **Callback Flow:** Agent double-clicks the recent call entry in Zoiper (which dials *7742). PBX looks up the mapping and completes the call to the real customer number.
  3. **Outbound CLI Masking:** PBX selects a Caller ID from the outbound number pool (US, DE, JP) to present to the customer, instead of the agent’s extension or PBX IP.
  4. **Data Retention:** Aliases and mapping codes expire automatically (TTL), ensuring long-term privacy.

• Agents never see or store real customer numbers.
  - Callback is fully automated with double-click, no manual entry.
  - Outbound Caller ID rotates from country-specific pools (Japan, USA, Germany).
  - Long-term durability: mappings auto-expire, minimizing data risk.
  - Low maintenance: implemented with Issabel dialplan, ODBC mapping, and cron cleanup.

NOTE::: I need a your PBX access to setup the following dialplan and configuration..
also SSH if applicable.