Slave Bridge unable to make calls (via bridge)

[MarcGold]

I manage two systems that I am attempting to create a bridge for. I have followed the instructions and I have the bridge up and running.

Two Systems - Master: Self Hosted AWS Lightsail with a Pro licence. The slave is a 3cx Hosted system with Pro Licence. (All via Tunnel 5090 and firewalls are open on this port)
I have the bridge up and from the master I can see the slave server, I have the presence and can see all the users there. I can make a call from the Master to the Slave and this works.
However, on the Slave the trunk is up, but I cannot make a call to the Master server - just says the number does not exist, the presence shows nothing.

I have no idea what I am doing wrong - I have a strange idea that the connection is not bidirectional and I need to set up Master -> Slave on both servers depending on the direction of the traffic flow. But it seems illogical and bidirectional should be working no?

Can someone point me in the right direction?

Thanks

 

[SnakeRiverWebDevelopment]

For each side, master and slave you need to set an outbound rule with a prefix to dial out.

example you have 3 digit extensions Outbound rule, Calls to Numbers with a length of 4
Calls to numbers starting with prefix 5 (or whatever)
Route1 Your Bridge
Strip Digits 1

 

[MarcGold]

Hi
I do have outbound rules on both sides. I decided to not to use prefix's as both use 3 digit extensions in different ranges.
Master Start 5 and Slave starts 2.

That said I have tried adjusting the Slave side to your suggestion, added a prefix, adjust the outbound rules to work with it and ensured that the none of the allowed country codes conflicted with the rules.

Still the same outcome: Calls from Master -> Slave : Calls Work and Presence All OK
But Calls from Slave -> Master : Called number does not exist and no presence is displayed.

Regards

 

[SnakeRiverWebDevelopment]

I do have outbound rules on both sides. I decided to not to use prefix's as both use 3 digit extensions in different ranges.
Master Start 5 and Slave starts 2.

That is the problem, the system looks at its self first, then outbound rules, put a prefix in and it should work.

 

[MarcGold]

I did, and it didnt. So removed everything, and rebuilt it as was. Now working in both directions without the prefixes.

 

[Evolute IT]

That is the problem, the system looks at its self first, then outbound rules, put a prefix in and it should work.

It's not a problem. 3CX supports bridges without prefixes. Once it doesn't find the dialed number in its own extensions, it follows the outbound rules automatically.

 

[MarcGold]

Thanks for all the pointers. I actually found the issue which was a DOH! moment when I spotted it.
It was down to the order of the Outbound rules, It was your comment that the system "looks at itself first and then the outbound rules" made me think of this like Firewall Rules.

So what was happening was the system was hitting an outbound rule - matching and then trying to dial - and correctly failing. It was just the wrong rule it was matching on, change the order and et voila!

Documented here just in case it helps someone else in the future.

Thanks for the assist