- Joined
- Oct 22, 2021
- Messages
- 62
- Reaction score
- 16
Hi All,
We have a 3CX system hosted on Microsoft Azure, all necessary ports open to the Azure VM including port 5090.
We have installed a Ubiquiti EdgeRouter Pro 8 into the network which is connected to our FTTP directly from the supplier using a Fibre Cable and Module plugged into the ER Pro. The connection is established using PPPoE.
We have an SBC installed on a Hyper-V server using the Linux Distro provided by 3CX.
The SBC will not connect to the PBX, it attempts a connection which we see in the 3CX logs but then disconnects. We have a register OK and a register fail at the same time on the SBC Trunk.
I know that port forwarding / firewall rules do not need to be in place for SBC traffic, we do not block any outbound traffic via the firewall on the ER Pro only the inbound traffic is restricted but again no port forwarding or firewall configuration needed for SBC to work.
The ER Pro is configured with a secondary 4G WAN connection provided by a router with a SIM card in it and Fail Over is configured. The ER Pro through some misconfiguration on the PPPoE failed over to the 4G connection and the SBC connected and stayed connected.
I wonder if anyone has any ideas what might be happening with the primary PPPoE connection that is preventing the SBC from connecting. It would not seem like it is the ER Pro that is the issue as it connected when on the failover WAN connection.
I've been looking at this all day and I'm pulling my hair our.
Thanks in advance.
We have a 3CX system hosted on Microsoft Azure, all necessary ports open to the Azure VM including port 5090.
We have installed a Ubiquiti EdgeRouter Pro 8 into the network which is connected to our FTTP directly from the supplier using a Fibre Cable and Module plugged into the ER Pro. The connection is established using PPPoE.
We have an SBC installed on a Hyper-V server using the Linux Distro provided by 3CX.
The SBC will not connect to the PBX, it attempts a connection which we see in the 3CX logs but then disconnects. We have a register OK and a register fail at the same time on the SBC Trunk.
I know that port forwarding / firewall rules do not need to be in place for SBC traffic, we do not block any outbound traffic via the firewall on the ER Pro only the inbound traffic is restricted but again no port forwarding or firewall configuration needed for SBC to work.
The ER Pro is configured with a secondary 4G WAN connection provided by a router with a SIM card in it and Fail Over is configured. The ER Pro through some misconfiguration on the PPPoE failed over to the 4G connection and the SBC connected and stayed connected.
I wonder if anyone has any ideas what might be happening with the primary PPPoE connection that is preventing the SBC from connecting. It would not seem like it is the ER Pro that is the issue as it connected when on the failover WAN connection.
I've been looking at this all day and I'm pulling my hair our.
Thanks in advance.