Identify which identity is wrong
Record whether the issue is the calling number, a display name, privacy handling or the identity after forwarding. Different networks can obtain names and validate numbers through different systems. A locally configured display name is not guaranteed to appear unchanged on every external phone.
Compare the call legs
Check the extension's intended identity, route or trunk overrides and the identity sent toward the carrier. For a forwarded call, document whether the system presents the original caller or the business identity under the provider's rules.
Do not copy arbitrary identity headers from another provider guide. The carrier may require authorized numbers and a particular privacy or diversion treatment.
Ask the right party
If the PBX sends the intended authorized identity but the receiver sees something else, preserve timestamps and carrier call IDs for escalation. Compare two destinations to determine whether the difference is destination-network specific.
Verify legitimate presentation
Correct the source of the mismatch and test ordinary, withheld and forwarded cases relevant to the business. Never use spoofed identities as a diagnostic shortcut. Keep emergency-service identity requirements separate and confirm them through the carrier's approved process.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- IETF RFC 3261 — SIP, including linked updates ↗
- IETF RFC 3550 — RTP and RTCP ↗
- Asterisk res_pjsip configuration ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.