Different CallerID for different trunks not working??

[Zahed]

Hello guys. I need your help.

I'm having an installation where 3CX (Version 20.0 Update 2 (Build 715 Release) is connected to 2 different Trunks. one for landline (Trunk1) and the other going to another system (not 3cx) in the HQ (Trunk2).

I have user 310 with outbound caller id 123456310 (all numbers are examples)

both trunks are up (Generic SIP Trunk) and working.

For landline (Trunk1) , the caller id 123456310 is used when user 310 calls outside using it. which is good.

The problem happen with the Trunk2. it is also sending 123456310 when the user 310 is calling. where I want it to send only caller id "310" since it is internal call between branches.

I tried reformatting outbound caller id in the trunk2 options with the following setup
source pattern: 123456(*.) replace: \1

but the system is totally bypassing it as if does not exist and keep sending full caller id (123456310).

I tried export trunk then modify the following line as shown below:
<field name="ParameterOut" custom="" parameter="FromUserPart">$CallerNum</field>

then import again.

but now the system is sending the "Trunk main number" in trunk2 general settings instead of sending user caller id (310).

I tried export trunk then modify the following line as shown below:
<field name="ParameterOut" custom="" parameter="FromUserPart">$OriginatorCallerId</field>

system is still sending user 310 outbound caller id "123456310"

The only way it is working is when i put outbound caller id for user 310 to "310". but that will butcher the calls in Tunrk1 because it is sending "310" now as caller id.

What can I do to solve this issue??
is there another way to do this?

 

[leejor]

Because trunks 2 is set as Generic, it will use the outbound caller ID that you've set against the extension, as you've discovered. You would have to set trunk 2 as a Bridge Trunk, for it to use the actual extension caller ID.
Keep in mind that this is no longer supported to a non-3CX PBX and may bring some undesired interactions. You can however , easily test it, without having to remove your original trunk 2.