Skip to content

Set Outbound Caller ID

Outbound CID is what the called party sees when an extension on UnifiedBX dials out. UnifiedBX resolves outbound CID through a chain — first non-empty wins:

  1. Trunk with CID Options = Force Trunk CID — overrides everything.
  2. Outbound Route → Route CID (if Override Extension = Yes).
  3. Extension → Outbound CID.
  4. Outbound Route → Route CID (if Override Extension = No).
  5. Trunk → Outbound CallerID — default fallback.

The Set CallerID module gives you a 4th layer for special cases — overriding CID just before the call hits the trunk, after all other layers.

Before You Start

  • You know which CID resolution layer to set on (per-extension is the most common).
  • The carrier permits the CID you intend to send (most require the CID to be a DID provisioned on your account; foreign DIDs may be rewritten or blocked).

Set Per-Extension Outbound CID

See Configure Caller ID → "Set Outbound CID" section.

Set Per-Route Outbound CID

  1. Go to Trunk Attributes → Outbound Routes.
  2. Click the route.
  3. Route Settings → Route CID — "Display Name" <NPANXXXXXX>.
  4. Override Extension — Yes to force this CID over per-extension settings; No to fall back when extension CID is empty.
  5. Click Submit → Apply Config.

Set Per-Trunk Default Outbound CID

  1. Go to Trunk Attributes → Trunks → click trunk.
  2. General → Outbound CallerID — "Display Name" <NPANXXXXXX>.
  3. CID Options:
    • Allow Any CID — pass through whatever the upstream sets.
    • Force Trunk CID — overwrite ALL outbound CIDs with this trunk's value (use sparingly).
    • Block Foreign CIDs — only allow CIDs that match a DID on this trunk.
  4. Click Submit → Apply Config.

Use the Set CallerID Module (advanced override)

For per-call CID logic that depends on which route, time, or destination is being used:

  1. Go to Trunk Attributes → Set CallerID (the setcid module).
  2. Click + Add Set CallerID Number.
  3. Configure:
    • Description — e.g. Force After-Hours CID.
    • CallerID Name — display name to set.
    • CallerID Number — number to set.
    • Destination after Set — where the call goes after CID is forced (typically the same trunk or route).
  4. Click Submit → Apply Config.
  5. Use the new entry as a destination from any route or time condition.

Verify

Place a test outbound call. On the receiving end (a cell phone or another carrier's number), confirm the CID matches.

asterisk -rvvvv
# Look for "Generating new CID" / "CallerID set to" in the trace.

Common Issues

  • CID change ignored. Higher-priority layer is overriding (Force Trunk CID, or Override Extension on route). Walk the resolution chain top to bottom.
  • Carrier rewrites CID anyway. Some carriers replace foreign CIDs for spoofing-prevention reasons. They usually offer "CID verification" — register your DIDs with them.
  • CNAM (caller ID name) shows wrong on cell phones. Cell carriers do their own CNAM lookup against the number, not what UnifiedBX sends. To control CNAM, register the DID with a CNAM database via the carrier.
  • Internal calls show outbound CID. Outbound CID only applies to external calls. Internal calls use Display Name. If they're conflated, your dialplan might be routing internal calls through outbound — fix the dial pattern.