Forwarded calls show wrong caller ID: why and how to fix

If your forwarded calls show wrong caller ID, the usual reason is that the forwarding creates a second call and sets the caller ID to your business number, not the original caller. The first thing to try is a setting in your forwarding service or PBX labeled “pass original caller ID” or “preserve caller ID” rather than “show my number.” If that setting doesn’t exist, change how you forward (use a platform/PBX instead of a star code on the line) and understand that some carriers block or rewrite foreign caller ID for anti-spoofing, so perfect passthrough isn’t always possible.

Why forwarded calls show wrong caller ID

Forwarding methods fall into two buckets: switch-level forwarding (star codes like *72 on a mobile or landline) and platform/PBX-based forwarding (a cloud number or on-prem system that dials out). In both cases a second leg is created to your destination phone. By default many networks and trunks stamp that outbound leg with your business line’s caller ID. The result is predictable: your cell shows your own number, or it shows the forwarding number if the service has a “show service number” toggle turned on.

Look first for an explicit option to “pass original caller ID on forwarded/bridged calls” in your PBX or cloud number. If you only use star-code forwarding, ask your carrier if they support forwarding with original caller ID on unconditional (*72) or conditional forwards (codes vary by carrier). STIR/SHAKEN validates the presented caller ID; forwarding that presents the original number needs the trunk to sign appropriately, and it should include Diversion or P-Asserted-Identity so downstream networks understand the call was forwarded. For background, see the FCC’s STIR/SHAKEN resources: https://www.fcc.gov/call-authentication.

What the receiving phone can and can’t display on a forwarded call

Your handset can’t force the network to display the original number on a forwarded call. iPhone and Android will show whatever the terminating carrier sends. If the forwarding method sets the From/CLI to your business line, the destination device will display your number. That’s why toggles inside some apps (for example, “show my service number as caller ID when forwarding”) change what you see without any change on the phone itself. It’s a service-side choice.

Star codes like *72 (unconditional call forward) run at the carrier switch tied to your SIM or landline. Many mobile and landline providers present your business number on the final destination for these forwards. A cloud number or PBX, by contrast, answers the inbound call to your business DID (the number you advertise), then originates a new outbound call to your cell or SIP phone, where the platform can choose to present the original or your business number—subject to trunk policy and what the next network allows.

Use a concrete yardstick. Say your dental practice forwards after-hours calls to the owner’s cell. If the cell shows your own main line every time, callbacks the next morning are harder and missed-name voicemails pile up. If you can make the forwarded call caller ID show the original number, you can call patients back quickly and your CRM can pop the right record.

How call forwarding presents caller ID under the hood

Most forwarding is a two-leg bridge:

• Leg A: Caller dials your business DID (the number you advertise). That call lands on your carrier or platform.
• Leg B: Your system dials out to the destination (cell, landline, SIP phone) and bridges the audio.

The outbound (Leg B) needs a caller identity. The simplest, and often default, is to use the account or trunk’s caller ID for every outbound call. That’s why forwarded calls show your number instead of the caller on many setups.

To preserve the original caller on Leg B, the forwarding system typically sets the From header to the original caller’s number, and adds a Diversion header containing your business number to show the reason and original destination. Some SIP trunks also use P-Asserted-Identity (PAI) to assert the caller to the next hop. Those headers tell downstream networks “this isn’t us spoofing; we’re forwarding a call originally placed to this business number.”

Why do some networks still rewrite or block it? Anti-spoofing checks and STIR/SHAKEN policies mean an outbound call that shows a foreign From number must be handled carefully. STIR/SHAKEN validates the presented caller ID; forwarding that presents the original number needs the trunk to sign appropriately, and it should include Diversion or P-Asserted-Identity so downstream networks understand the call was forwarded. For background, see the FCC’s STIR/SHAKEN resources: https://www.fcc.gov/call-authentication. In practice, consistent caller ID passthrough depends on two things: your forwarding platform actually sending the right headers, and the outbound routes accepting and passing them.

If you’re using SIP, or want to understand the signaling path, see SIP trunking basics for a primer on From, PAI, and Diversion behavior.

When to show your business number vs the original caller

Showing the original caller number is best when you need fast callbacks, CRM screen pops keyed off the caller number, and context about who is on the line without waiting for IVR or intake. For a small practice or service business that returns missed calls in batches, seeing “(415) 555-0123” instead of “Dental Main Line” is tangible time saved.

Showing your business number can be smart if you want staff to instantly recognize a business call, keep personal numbers private on return calls, or avoid downstream blocking when your trunk or carrier frowns on foreign From numbers. Some providers add an option to show the platform’s own number on forwarded calls, useful for training and for tracking.

There is a middle ground. A short whisper message can announce “After-hours line” or the campaign name to the agent before audio connects to the caller. Some systems can prefix the caller’s number or a tag in the display name (for example, “AH: 4155550123”), which helps where phones display name and number from SIP Caller-Name. Be aware that not all devices show prefixed names cleanly, and prefixes don’t travel to a mobile network’s caller ID screen on a PSTN leg.

Be clear about the limits. Even if the number is correct, CNAM lookup results vary. Your device might show a local contact match, a third-party app tag, or the terminating network’s database result. Don’t chase a perfect caller name; prioritize presenting the correct number.

Make forwarded calls show the original caller ID: your options

If you rely on star-code forwarding on a mobile or landline:

• Ask your carrier if they support forwarding with original caller ID on unconditional (*72) and conditional forwards (codes vary by carrier). The exact wording that helps: “Can you forward my line while presenting the original caller’s CLI, not my own, on the forwarded leg?”
• If they can’t, move the forwarding into a cloud routing platform or PBX where caller ID presentation on the outbound leg can be controlled. You’ll point your published number to the platform and let it forward out to your cell or SIP device.

If you use a cloud number or PBX today:

• Look for a setting like “pass original caller ID on forwarded/bridged calls” and enable it.
• Confirm your outbound trunk allows a foreign From number when accompanied by a Diversion header containing your business DID, or by P-Asserted-Identity. The ask to your provider should be explicit: “Enable caller ID passthrough on forwarded calls and pass the original CLI with a Diversion header containing my business DID.” If they require PAI, ask them to honor PAI from your PBX or to insert it based on your authenticated trunk.

If passthrough is blocked for any route:

• Use whispers to identify the destination line or campaign before connecting so staff still know it’s a business call.
• Choose to display your business number, but make sure your call records capture the original caller ID for callbacks and reporting. Most call logs store the inbound caller even if the outbound leg cannot present it.

Some services let you choose whether the forwarded call caller ID shows the service’s number or the original caller. If you see a toggle like “show my service number as caller ID when forwarding,” turn it off to attempt passthrough. Google Voice and similar products document this behavior in their settings; the phone itself can’t override it.

If you’re evaluating platforms because caller ID not passing through call forwarding is a blocker, compare how they handle outbound presentation on forwarded legs and whether they support Diversion and PAI on their direct SIP trunks. A good place to start is this overview of options in call forwarding software and the broader business call forwarding guide.

A brief aside: CallFlow forwards to any phone, SIP endpoint, or browser agent, with routing rules, IVR, whisper messages, and call logs that record the original inbound caller. If you need to identify the line or campaign as calls arrive while you sort out caller ID presentation, a short whisper is often the least disruptive fix.

Practical test plan: Place three inbound test calls to your published business number—one from each of two different mobile networks and one from a landline—while forwarding first to the owner’s cell and then to a SIP softphone. For each call, note exactly what number the destination displays and save timestamps. If the SIP phone shows the original caller but the cell shows your business number, the issue is likely on the PSTN route to the mobile carrier and your provider may need to adjust headers or switch routes. Keep notes for support.

Why the caller name is wrong even when the number is right

Caller name (CNAM) is not transmitted end to end in the US for ordinary PSTN calls. The terminating network usually performs a CNAM database dip based on the number it sees, then your device chooses what to show. That’s why two people can see different names for the same caller, and why forwarded calls show forwarding number names if that’s the number presented.

Mobile devices layer in contacts and apps. If the number exists in your contacts, that wins. If you use a reputation or directory app, it might label the caller differently. Landlines rely more on the network dip and can lag if the database hasn’t been updated yet. If you show your business number on forwarded calls, the displayed name will be whatever is listed for your business line and can take time to refresh after changes.

What you can control is the number. Present the correct original number when possible, and keep your own business CNAM listing accurate if you choose to show it on forwarded calls. Don’t be surprised if the name differs by destination carrier or device even when you’ve fixed the number.

Test across networks and confirm it’s fixed

Build a small matrix and document the results. Forward your main number to the owner’s cell and, separately, to a SIP softphone. Place inbound test calls from two different mobile networks and one landline. Note what each destination phone displays. If all paths now show the original number, you’re done.

If one path still shows your business number or a platform number, escalate with specifics. Provide your provider the exact timestamps (with time zone), the calling number, your business DID, the destination, and the requirement: “Pass original CLI on the forwarded leg with a Diversion header (or P-Asserted-Identity) containing my business DID.” Ask whether their outbound routes support this consistently and if they see any STIR/SHAKEN reason a particular route would rewrite the From. If your SIP device shows it correctly but the mobile does not, ask if an alternate carrier-grade route to that mobile network can preserve Diversion.

Keep a whisper enabled while you validate caller ID so staff don’t get blindsided if the display changes during testing. If, in parallel, your forwarded calls aren’t reaching the destination reliably, work through the basics in forwarded calls not ringing so you’re not chasing two issues at once.

What to do next

• If you use star-code forwarding, ask your line carrier about forwarding with original caller ID. If they can’t, move the forward into a platform or PBX you control.
• If you use a PBX or cloud number, enable caller ID passthrough, and ask your provider to allow a foreign From with Diversion or PAI on forwarded legs.
• Run the three-call test from different networks to confirm the fix, and send timestamps to support if one route still rewrites the number.

If you need a forwarding platform that lets you route to phones, SIP, or browser agents with IVR, schedules, and whispers while keeping detailed call logs for the original caller, you can create an account at CallFlow. If you prefer to talk through your setup, reach us at Contact.