Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

The web interface of 3CX 20 is a bit different than older versions, but the configuration of a beroNet gateway with the IPBX is very similar.

Find out the IP of your Gateway

First things first: you need to find out the IP address of your gateway that you plugged to your LAN. To do so, run bfdetect. It enables you to find all beroNet devices on your network.

You can also use bfdetect to set a fixed IP address on your gateway (which is recommended).

Add a Gateway in 3CX

On the bottom part of the 3CX web interface is an Admin, click on "SIP Trunks".

Click on "+Add gateway"

The following window appears:


On this page, you can create the SIP connection between the 3CX and the gateway. A few important informations need to be entered:

  • "Registrar/Server/Gateway Hostname or IP": You need to enter here the IP address of your beroNet Gateway
  • Main Trunk Number needs to be assigned a value containing at least four digits

In the authentification part we configure the values which the beronet gateways uses to register to the 3cx:
  • "Authentification ID" is what we call "user" in the beroNet web interface
  • "Authentification Password" is what we call "secret" in the beroNet web interface

Registering the beroNet gateway


On the beroNet gateway go to SIP→SIP and click the Add button. In the pop-up fill out the values 3cx provided for registering a SIP trunk, save and click activate.



Go to the state screen to see if registering was successful.
Create an outbound rule for the gateway, cutting off the first four digits (the main trunk number)
On the beronet gateway configure the inbound and outbound rules in the dialplan

Known issues with 3cx v20

Especially when using ISDN there seems to be an issue with the 3cx making a SIP call to the gateway and the ringing sound isn't heard.
This is mostly caused by the mixed Progress and Alerting messages passed through from ISDN. If this happens in your environment, this can be addressed by creating a call progress table. For this go to Preferences→Call Progress, and create a SIP→ISDN call progress table and save it.

Now you need to configure it to not pass all the ISDN messages to the calling SIP peer. Configure the SIP response to be 180 on an incoming ISDN ALERTING message.


This now has to be configured in the SIP→ISDN dialplan rule in the field Call Progress Table S2I

Save and activate. Note that in the 24.01 firmware there is a bug. If you open the dialplan rule again, the value is not pre-selected in the dropdown and saving the rule without manually selecting the Call Progress Table again would reset it. This issue has been fixed with firmware 24.01.01-rc02



  • No labels

If you need scheduled remote assistance, you can request our on-demand support services: https://www.beronet.com/support