- Joined
- Jul 30, 2026
- Messages
- 3
- Reaction score
- 0
Hello 3CX Support Team,
We use 3CX V20 with Twilio and VoIP.ms trunks. When an unanswered queue call forwards to our Vapi AI assistant, Vapi displays the main Twilio trunk number instead of the original customer’s number.
Example call:
The 3CX report shows caller 1660 and forwarded destination 4788 correctly. However, Vapi shows 2835 under Customer Phone Number.
Settings reviewed:
Please also advise which SIP headers or diagnostic traces we should inspect to determine where the caller number changes. We need this to work dynamically for every customer.
Thank you.
We use 3CX V20 with Twilio and VoIP.ms trunks. When an unanswered queue call forwards to our Vapi AI assistant, Vapi displays the main Twilio trunk number instead of the original customer’s number.
Example call:
- Original caller: +1....81660
- Dialed Twilio DID: +1....784316
- Main Twilio trunk number: +1....032835
- Queue: 80029 — TEST QUE
- Queue timeout: 15 seconds
- No-answer destination: +1....014788, our Vapi assistant
The 3CX report shows caller 1660 and forwarded destination 4788 correctly. However, Vapi shows 2835 under Customer Phone Number.
Settings reviewed:
- Outbound-rule caller ID: blank.
- VoIP.ms default outbound caller ID: blank.
- Include diversion header support: enabled.
- Exported VoIP.ms template: FromUserPart = $AuthID and RemotePartyIDCallingPartyUserPart = $OutboundCallerId.
Please also advise which SIP headers or diagnostic traces we should inspect to determine where the caller number changes. We need this to work dynamically for every customer.
Thank you.