3CX for 2x trunks/countries

[ArtR]

Hi All,
Testing 3CX to move our company to soon I hope, but wanted to get some input/advice in regards to setting up users Outbound CID as we will use 2x trunks to service 2x countries.

I understand we will need to set some outbound rules to ensure the right trunk is used for the number being dialed (AU calls via AU trunk, NZ via NZ)

Outbound CID?
* All users CID is main NZ trunk number when calling NZ numbers
* Most users CID is main AU trunk number when calling AU numbers
* Some users CID should be their direct line (only on AU trunk where we have block of 100) - i.e. ext 2110, external number is 028780 2110

Is that possible to have such a mix? Basically we have most staff just present the main line as return calls should just go to our IVR, but some managers etc it is best to go direct and get them or their VM.

 

[nub]

Outbound rules can handle what trunk is used for whatever number is called.

Whatever trunk is used the caller id will be displayed by that trunk I guess, you can override this from the extensions > general > Outbound Caller ID, some providers let you spoof caller id and some do not, this would only be a problem for people that want a DID displayed for caller id across both trunks.

 

[leejor]

If need be, you could enforce the inclusion of country codes in your outbound rules (full national numbers) to ensure dialled numbers use the correct trunks.

 

[YiannisH_3CX]

Hello @ArtR

It will take some configuring but i believe you can achieve the desired functionality. The first thing you need to know is that if an extension outbound caller ID is present the PBX will use that.

So for most users that option should be empty so when they call out the main trunk number is displayed. When calling out from AU the AU number will be displayed and when calling out NZ the NZ number will be displayed.

* Some users CID should be their direct line (only on AU trunk where we have block of 100) - i.e. ext 2110, external number is 028780 2110

This is the tricky part as these users must have their outbound caller ID set under their extension. So when these users call out from the AU trunk the correct number will be sent to the provider. But this means that the AU number will also be sent when these users call out from the NZ number.
To avoid this from happening you need to force the NZ trunk to always send the main trunk number.

Ideally you need to know what SIP field your NZ provider is using to read the caller ID from and change only that but for testing you can change all SIP fields that contain "OutboundCallerId" and "OriginatorCallerID" to "LineNumber". This will tell the PBX to always send the main trunk number as outbound caller ID when the NZ trunk is used. So even if users have an outbound caller ID configured the PBX will ignore it for that trunk.

Hope this makes sense.

 

[ArtR]

Hello @ArtR

Ideally you need to know what SIP field your NZ provider is using to read the caller ID from and change only that but for testing you can change all SIP fields that contain "OutboundCallerId" and "OriginatorCallerID" to "LineNumber". This will tell the PBX to always send the main trunk number as outbound caller ID when the NZ trunk is used. So even if users have an outbound caller ID configured the PBX will ignore it for that trunk.

Hope this makes sense.

Makes perfect sense, thank you. Will work on testing this out.

 

[ArtR]

If need be, you could enforce the inclusion of country codes in your outbound rules (full national numbers) to ensure dialled numbers use the correct trunks.

On our existing system we use 0 to dial out locally (AU) and 064 to dial out the NZ trunk, it looks like we could continue with that as long as our outbound rules are setup right.

 

[YiannisH_3CX]

Glad we could assist. Let us know if you encounter any issues.