I believe since the latest update of VitalPBX to Asterisk 20.19.0 the caller ID behaviour is different.
Scenario 1 - Functioning as specified.
Follow Me enabled, ring All, external destination. The FROM parameter on outbound INVITE shows the original caller number
Scenario 2 - Changed
Inbound call to a ring group or queue. External member defined in group or virtual extension with external number in dial string as member.
The FROM parameter on outbound INVITE shows NO caller ID (or an overwritten caller ID when specified in the trunk/outbound route).
Scenario 3 - Looks OK
Inbound call to extension with CFI enabled shows the original CID.
We’re having the same problem here. I tried posting twice about this, but it looks like it didn’t get approved. We’ve had multiple clients reach out to us about this, so we really need to find a way to fix it as soon as possible.
Outbound Caller ID lost during Ring Group forwarding after VitalPBX 4.5.3-4 upgrade
Hello, we have detected a regression in our outbound calling identity presentation immediately following our upgrade to version 4.5.3-4.
When an external call comes into a Ring Group and is routed to an external number, the original incoming Caller ID is no longer preserved. Instead, the final recipient sees the default tenant CallerID. This feature was working seamlessly prior to the 4.5.3-4 release.
Could you please advise if there is any configuration change or workaround we can apply on our side to resolve this situation?