VoIP.infoThe independent guide to business communications.
VoIP.info Troubleshooting

FreePBX Set CallerID is not applied or is overwritten

Locate the first divergence among upstream selection, saved rule, generated and loaded app-setcid context, channel caller ID, downstream FreePBX policy, SIP signaling and provider presentation.

Reviewed 2026-10-14Current FreePBX Set CallerID release/17.0 metadata and generated dialplan plus Sangoma module and current Asterisk CALLERID and party-ID documentation reviewed October 14, 2026; the module metadata identifies version 17.0.1.2 on the standard repository and the source sets channel caller name and number before a configured destination, but installed module version, generated and loaded dialplan, upstream selection, later FreePBX caller-ID precedence, provider authorization, SIP signaling and destination presentation remain deployment specific, and no PBX, module, caller-ID value, destination, provider, packet, endpoint or live call was inspected or testedAdvancedDocumentation based · not lab tested

Freeze one call and classify the first wrong observation

Record timestamp and timezone, source, upstream destination, Set CallerID rule and intended name and number, configured next destination, installed module version and signature, generated configuration revision, loaded dialplan revision, channel and SIP Call-ID, selected outbound route and trunk when applicable, provider response and final display. Redact values while preserving a stable mapping.

Classify the first divergence as rule not selected, saved value wrong, configuration not generated, stale loaded context, channel value wrong, downstream rewrite, provider-facing header wrong, provider rejection or remote presentation difference. Do not begin with the final handset display and work backward by changing every caller-ID field.

Prove the module and upstream handoff

Confirm the Set CallerID module is installed, enabled and signed under the selected repository policy. Verify the upstream IVR, time condition, inbound route or other destination actually points to the intended rule, then identify the rule in the generated and loaded app-setcid context.

The repository documents possible source behavior, not the running instance. If the rule is missing or the loaded revision is stale, correct Module Admin or Apply Config state before investigating carrier headers.

Compare saved fields with the channel transition

The reviewed source writes caller name and number and then goes to the configured destination. Compare the saved description, name, number and destination with the generated instructions and a bounded call trace. Capture caller-ID state immediately before the rule, after both assignments and at the first instruction in the downstream destination.

Preserve empty strings, quoting, variable expansion and character encoding exactly. If a value is already wrong immediately after app-setcid, fix that rule or the demonstrated expansion input; do not compensate with a trunk-wide override.

Find the first downstream owner that changes it

If Set CallerID produces the intended channel value, follow the same channel into the downstream application. For an outbound leg, prove the matched route, selected trunk and active FreePBX caller-ID branch, then compare channel state with the first provider-facing INVITE. Extension, emergency, route, trunk, forwarding, privacy and endpoint policy can create different results.

Keep caller ID, connected-line identity and redirecting identity separate. A correct channel caller ID does not show that Diversion, P-Asserted-Identity, privacy or the far-end display is correct, and a later rewrite does not prove the Set CallerID rule failed.

Place provider acceptance after PBX egress

When the egress signaling carries the intended organization-controlled identity, preserve the response code, provider call identifier and timestamp. Confirm the provider-authorized number set and documented header and privacy rules. An accepted call, rejected identity and final destination display are different evidence objects.

Do not test arbitrary identities or add every caller-ID header. If the provider accepts the call but presentation differs remotely, use the carrier-path evidence rather than adding another Set CallerID rule.

Correct one boundary and repeat a control call

Change only the first demonstrated mismatch: upstream destination, rule fields, generated or loaded state, downstream caller-ID policy or provider-authorized configuration. Preserve rollback values and repeat the original call plus one control call that bypasses the rule.

Record channel values at the same boundaries and the final result. If the first divergence does not move, roll back and reopen the earlier hypothesis. No PBX, module, caller-ID value, destination, provider, packet, endpoint or live call was inspected or tested for this diagnostic.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Examples require adaptation to your topology. No live PBX or hardware testing is claimed.

Continue your research

Guide · Current FreePBX Set CallerID release/17.0 metadata and generated dialplan plus Sangoma module and current Asterisk CALLERID and party-ID documentation reviewed October 14, 2026; the module metadata identifies version 17.0.1.2 on the standard repository and the source sets channel caller name and number before a configured destination, but installed module version, generated and loaded dialplan, upstream selection, later FreePBX caller-ID precedence, provider authorization, SIP signaling and destination presentation remain deployment specific, and no PBX, module, caller-ID value, destination, provider, packet, endpoint or live call was inspected or tested

FreePBX Set CallerID: change one call-flow identity deliberately

Use the Set CallerID destination to change channel name and number before one documented handoff, while keeping downstream FreePBX precedence, SIP identity and carrier acceptance separate.

Read guide →
Guide · Current Sangoma Core API, outbound-route, trunk, caller-ID customization and emergency-service documentation plus current Asterisk res_pjsip and party-ID documentation reviewed October 11, 2026; several detailed Sangoma GUI guides retain older PBX GUI examples, and no PBX, extension, route, trunk, provider account, number, header, identity, privacy state, presentation, emergency service or live call was inspected or tested

FreePBX outbound caller ID: identity precedence and carrier acceptance

Trace extension, emergency, route, trunk and PJSIP identity policy into the exact outbound INVITE and the carrier's authorized presentation.

Read guide →
Guide · FreePBX 17 on Debian 12; route semantics cross-checked against Sangoma PBX GUI 13 guides and current FreePBX Blacklist 17.0.1.2 release/17.0 source on October 11, 2026; exact installed modules, generated or loaded route hooks and calls were not tested

FreePBX inbound and outbound routes

Follow the incoming number and outgoing dial pattern as two separate routing decisions.

Read guide →
Guide · FreePBX 17 on Debian 12; Bulk Handler 17.0.7.1 release/17.0 metadata and Sangoma Bulk Handler workflow reviewed October 11, 2026; repository state does not prove the installed module or runtime, and no import or Apply Config operation was tested

FreePBX changes: submit, apply and verify

Keep GUI settings, generated configuration and runtime behavior aligned during routine administration.

Read guide →
Troubleshooting · Current Asterisk res_pjsip, party-ID, CALLERID and BLACKLIST references; FreePBX Blacklist 17.0.1.2 release/17.0 metadata and current source; plus FreePBX 17 on Debian 12 reviewed October 11, 2026; Sangoma GUI 13 screen guidance is version-scoped, and no PBX, carrier, blacklist rule or live call was inspected or tested

Caller ID is missing or wrong

Trace calling, connected and redirecting identity across FreePBX policy, Asterisk channel state, SIP headers and carrier treatment.

Read guide →
Troubleshooting · Current Sangoma Core API, outbound-route, trunk, caller-ID customization and emergency-service documentation plus current Asterisk res_pjsip and party-ID documentation reviewed October 11, 2026; several detailed Sangoma GUI guides retain older PBX GUI examples, and no PBX, extension, route, trunk, provider account, number, header, identity, privacy state, presentation, emergency service or live call was inspected or tested

FreePBX outbound caller ID is wrong or rejected: trace the active owner

Bind one call to the selected route and trunk, resolve FreePBX identity precedence, inspect the egress headers and separate carrier authorization from destination display.

Read guide →
Diagnostic · Current Sangoma fwconsole and Asterisk CLI, dialplan and PJSIP troubleshooting documentation reviewed September 27, 2026; no FreePBX, Asterisk or call path lab tested

FreePBX Apply Config failed: isolate generation from reload

Preserve the failed change, capture the supported fwconsole reload error and prove which generated object reached Asterisk before attempting repair.

Read guide →