Hello everyone,
We're experiencing a Caller ID issue with our 3CX PBX and would like to know if anyone in the community has encountered a similar problem or found a reliable solution.
Our environment:
Under normal circumstances, when an external caller contacts one of our numbers, the receiving phone correctly displays the original caller's phone number.
However, when we configure an extension to forward incoming calls to an external mobile number, the Caller ID behavior becomes inconsistent.
In our testing, the forwarded call displays the destination mobile number itself (usually my own number, since I am typically the recipient of the forwarded calls) rather than the original caller's number.
Current configuration:
We've reviewed the SIP trunk's Caller ID Control tab, and the configuration is straightforward, with nearly everything left at its default values.
Both Reformat Inbound Caller ID and Reformat Outbound Caller ID are empty, and we haven't made any specific Caller ID manipulation changes that would explain this behavior.
Since this is a production PBX, we're looking for a reliable way to identify and resolve the issue without disrupting existing calls, routing, or other working functionality.
Our questions:
Any guidance, recommended troubleshooting steps, or confirmed solutions from other 3CX administrators would be greatly appreciated.
Thank you in advance!
We're experiencing a Caller ID issue with our 3CX PBX and would like to know if anyone in the community has encountered a similar problem or found a reliable solution.
Our environment:
- 3CX Version: Latest stable V20 release
- Operating System: Debian
- SIP Trunk: Generic SIP Trunk with a direct connection to our SIP provider
- Call Forwarding: Extensions configured to forward incoming calls to external mobile numbers
- Caller ID Control: Mostly default settings, with no significant customization
- Reformat Inbound Caller ID: Empty
- Reformat Outbound Caller ID: Empty
Under normal circumstances, when an external caller contacts one of our numbers, the receiving phone correctly displays the original caller's phone number.
However, when we configure an extension to forward incoming calls to an external mobile number, the Caller ID behavior becomes inconsistent.
In our testing, the forwarded call displays the destination mobile number itself (usually my own number, since I am typically the recipient of the forwarded calls) rather than the original caller's number.
Current configuration:
We've reviewed the SIP trunk's Caller ID Control tab, and the configuration is straightforward, with nearly everything left at its default values.
Both Reformat Inbound Caller ID and Reformat Outbound Caller ID are empty, and we haven't made any specific Caller ID manipulation changes that would explain this behavior.
Since this is a production PBX, we're looking for a reliable way to identify and resolve the issue without disrupting existing calls, routing, or other working functionality.
Our questions:
- Has anyone experienced similar Caller ID behavior when forwarding calls to external numbers using a Generic SIP Trunk on 3CX V20?
- Could the issue be related to SIP headers such as From, P-Asserted-Identity, Remote-Party-ID, or Diversion?
- Are there any recommended settings under Caller ID Control that we should review or adjust without affecting normal inbound and outbound calls?
- Could the SIP provider be modifying the Caller ID during forwarded calls, even when the 3CX configuration remains unchanged?
- What would be the safest way to troubleshoot this issue, preferably by comparing SIP signaling between a successful forwarded call and one displaying the incorrect Caller ID?
Any guidance, recommended troubleshooting steps, or confirmed solutions from other 3CX administrators would be greatly appreciated.
Thank you in advance!
