Outbound Caller ID via Remote Bridge

[smwebmaster]

Hi there. We are having some issued with CallerID over a remote bridge. Here is our setup.

We have a 3CX hosted install at Amazon AWS ("Master"), which registers all of our extenstions.

We have an on-premise 3CX Appliance that connects direcly to a metro-E switch as required by our local TELCO provider ("Slave").

There is a bridge between the master and the slave. Effectively, when an extension on the Master dials out, the call is sent to the Slave. The Slave passes the call to the Telco and the call completes successfully.

There is only one issue. We cannot get the Outbound Caller ID for the extensions on the "Master" to be passed as the Outbound Caller ID via the Bridge. This means that the correct DID is not passed to the Telco. Is there a way to fix this?

Our previous setup was that the "Master" had a trunk configuration on a local Asterisk server and that worked great. We thought going 3CX-to-3CX would be easier, but although I've seen this question on the forum I've not seen a really satisfying result? Does anyone know of a good way to have the "Slave" effectivey be a gateway for the Master, and faithfully pass along the Outbound Caller ID as configured for the extension on the Master?

 

[smwebmaster]

Just a gentle nudge in case someone can point me in the right direction?

 

[SweetAction]

Is this the same issue as https://www.3cx.com/community/threads/in-one-trunk-out-another.120406/ or another one?

 

[smwebmaster]

I think they are similar. Seems like they want to have outbound via an asterisk box for some other purpose. But we are trying to get 3cx bridging to work correctly for outbound calls, where the extensions are registered to one 3CX but the outbound trunks are registered on the other.

 

[SweetAction]

On the slave, does CID pass out correctly (if you make an outbound rule with the CID set to what you are trying to send from the master, does it work)?

On that same vein, does it send the correct number if you have an outbound rule on the slave that targets calls from the master and CID set on that outbound rule?

Did this ever work?

Does your telco support clip no screening? Do you own the number with that telco?

 

[smwebmaster]

Hi Sweet Action.

It's a new config. So it never worked. Here are the answers to your questions:
1) Yes we own the DID from that Telco
2) Yes, if we manually ocnfigure the exact same DID on the slave as the trunk outbound CID then the telco passes it fine

I am not sure how to do this: On that same vein, does it send the correct number if you have an outbound rule on the slave that targets calls from the master and CID set on that outbound rule?

But that seems just to be further confirmation of "will my TELCO accept that CID". And the answer is yes.

In my PCAP I can see the master calls the slave with the correct did (246NXXNXXX(EXT@<HOST>.3cx.us). But for some reason when the Slave calls the Trunk it is droping the 246NXXNXXX and instead just passing EXT.

 

[smwebmaster]

And I guess yes.... This used to work find when the "Save" was an Asterisk box. When we changed to a 3cx-to-3cx bridge it broke.

 

[SweetAction]

What DID, if any, gets passed to the telco when you make a call from the master? Is it a DID that is present on the slave and just not the correct one, no CID, something else.

On the Slave, in the outbound rules, can you provide a screenshot of your setup blurring/removing sensitive numbers?

 

[cobaltit]

If the on-prem 3CX box is just to route calls to your local provider it might be easier just to setup a VPN and route calls directly from your cloud instance.

 

[smwebmaster]

I was able to get it working, but not how I would expect:

1. On the Bridge Master, set the outbound parameters of From : Display Name to "OtboundCallerID:Taken from Extension"
2. On the Slave's TELCO Trunk, set the Outbound Paramter for "From:User Part" to be "Caller Display Name"

On the Bridge Slave I've defined the outbound rules to catchall to local numbers, and have the outbound CID set to BLANK.

This worked for me... not sure if optimal.

 

[North40IT]

ok i'm having the same issue as OP and i've followed the steps outlined in the last post but the outbound CID still is defaulting to the primary DID associated with the SIP Trunk rather than the extension defined settings on the Slave PBX.I guess I'm not sure what is meant by "On the Bridge Slave I've defined the outbound rules to catchall to local numbers, and have the outbound CID set to BLANK." I have standard 10 + 11 digit outbound rules configured on the Slave PBX. Outbound CID is blank.