bridge failed no changes made

[PaulEmous]

Hi all,

So I had a bridge working for a few months. Nothing special. Made a bridge and was online. Then all of a sudden it failed to register. As far as I can tell (I am the only person with access) the bridge stopped working.

I rebooted both 3cx instances and the bridge fails to go online.
I checked if port 5090 is open (both sides, and it is).

I also made a new bridge to an "other" 3cx instance (to the effected one) and also that fails. Making a bridge from the remote 3cx instance to the "other" 3cx instance works, making me believe it's something that affects the "main" 3cx instance, not the "remote", "xxx.my3cx.nl" main instance. Hope that makes sense....

This comes from the activity log:

Call or Registration to "xxx" Bridge has failed. sip:[email protected]3cx.nl:5090 replied: 503 Remote end of tunnel is not connected; warning: Remote end of the bridge is not connected; from IP:127.0.0.1:5080

I also did a quick test to see if the port was working so in the FW I forwarded port 5090 to 80 and saw if TCP traffic was going (by opening a manage page on a different device). This worked.

Port 5090 allows UDP and TCP traffic trough the FW.

Again nothing in the configuration is changed.
Side note: why is the activity log showing it tried it from port 5080?

Any advice is greatly appreciated.

 

[leejor]

Again nothing in the configuration is changed.
Side note: why is the activity log showing it tried it from port 5080?

That's a concern. Do you have Activity logs that go back before all this began? Do you see 5080 used in there? It must be told to use that port, somewhere.

 

[PaulEmous]

its 127.0.0.1:5080. Local is always funny. Not sure what that is about. Anyway, setup a VPN and did the bridge internal. It works. I have reason to believe the ISP is blocking it. (Middle East)

 

[leejor]

I have reason to believe the ISP is blocking it. (Middle East)

If one end is located there, then that may very well be the problem. It may have taken them a while to detect your VoIP traffic.

 

[JohnS_3CX]

Hi Paul,

The bridge traffic arrives encrypted from outside to port 5090 of the PBX IP. Where the bridge terminates locally, the PBX connects internally to it on localhost port 5080 so this is normal.

If it works via VPN but not via WAN then yes, it is possible the ISP is blocking traffic. a capture on the Master PBX will confirm this (you will see traffic coming from the slave IP vs no traffic if the ISP is blocking you).