Wrong DID on Inbound Rule Call Forwarding

[vankampen]

Hi, I have configured two DIDs on the SIP Trunk. Let's say DID a and DID b.
When calling with a specific DID, this works properly.

I have now configured an Inbound rule on DID a, to forward this to an Outside Number. This forwards the call using DID b. I expected it to use the same DID as the call was received on. I did a capture of the traffic in the activity log, and this confirms the incoming call on DID a is forwarded with a From DID b.

Is there a way I can force it to use the incoming DID?

• 3CX Version, Professional Annual 18.0 update 9
• Server OS, Windows 11
• Is the 3CX Server Hosted and where? On-premises
• Has the Firewall Checker passed: YES

 

[SweetAction]

Do you have an outbound rule that would affect system forcing a outbound callerid of DID b?

 

[vankampen]

Do you have an outbound rule that would affect system forcing a outbound callerid of DID b?

Hi SweetAction,
no I don't. All outbound rules are not DID specific.

Is it possible to specifiy the DID in the call forwarding?

Pieter from SweetLake City.

 

[TheodorosG_3CX]

The DID numbers are only for inbound calls
It is not possible to select a DID to make the call as all calls are going from the main trunk number.
You can however create an outbound caller id from the outbound rules. Keep in mind though that this also depends on whether the sip trunk provider supports this functionality. Are you using a 3CX Supported Provider?