In this tutorial I will show you how to install 3CX the beroNet Hypervisor using the 3CX for Debian ISO file. Towards the end of the tutorial, I will present how to set a static IP address to your Debian system. The tutorial will end with a pro tip on how to install 3CX for Debian in under five minutes.

If you have any questions about the Appliance or installing 3CX, leave us a comment, or write an email to sales@beronet.com.

The post How to install 3CX for Debian in the beroNet Appliance appeared first on beroNet GmbH.

How to Install 3CX for Linux in the beroNet Hypervisor:

Install Debian:

1. After logging into the beroNet Hypervisor, navigate to “Manage ISO’s” listed under the “Management+” tab
   
2. Select “Web Download” and paste this URL into URL field: http://cdimage.debian.org/debian-cd/8.6.0/amd64/iso-cd/debian-8.6.0-amd64-netinst.iso
   
3. Navigate to “Manage VM’s” under the “Management+” tab and select “new”
4. Enter your preferred specifications for your machine, and in the “Boot from ISO” field select the recently downloaded Debian iso media. Create the machine.
   
5. Start your new VM and complete the Debian installation process

Configure Debian for 3CX:

1. Login to your root user and set a static IP:

   1. nano /etc/interfaces/network

   2. Change

      iface eth0 inet dhcp

      to

      iface eht0 inet static

   3. Add the following below:

      address [the chosen ip address]
      netmask [the netmask for your network]
      gateway [ip address of the router/gateway]
      

      
      
   4. Select ctrl+w to exit, Y to save and then enter to confirm

Install 3CX for Linux:

1. Run the following commands, either using SSH as demonstrated in the video – or type them in directly using the Web-VNC viewer
   

   wget -O- http://downloads.3cx.com/downloads/3cxpbx/public.key | apt-key add -echo "deb http://downloads.3cx.com/downloads/3cxpbx/ /" | tee /etc/apt/sources.list.d/3cxpbx.listapt-get updateapt-get install 3cxpbx
   

2. Select “1” to install using a Web GUI
3. Navigate to http://[machine IP address]:5015 and follow the on-screen prompts

The post How to install 3CX for Linux in the beroNet Hypervisor appeared first on beroNet GmbH.

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 left part of the 3CX web interface, click on “SIP Trunks”.

Click on “+Add gateway”

The following window appears:

As brand, leave beroNet, select the device that you have:

• You can use BRI for the following references: BFSB1S0, BFSB2S0, BFSB2HY, and BF400Box with BRI or hybrid modules;
• You can use FXO for the following references: BFSB4XO, BF4004FXObox and for GSM Gateways
• You can use PRI for the following references: BF400box, BF1600box or BF6400box with 1 or 2 PRI

Enter you main number in the text block “Main Trunk No”.

Configure the SIP connection

On the page that appears after, you can create the SIP connection between the 3CX and the gateway. A few important information need to be entered:

• “Registrar/Server/Gateway Hostname or IP”: You need to enter here the IP adresse of your beroNet Gateway
• “Number of SIM Calls”: the number of simultaneous calls you can do via the gateway: 2 for 1 BRI port, 1 for 1 FXO port and 30 for 1 PRI port.

• “Authentification ID” is what we call “user” in the beroNet web interface
• “Authentification Password” is what we call “secret” in the beroNet web interface

Do not use the 3 way authentifications.

Configure the beroNet gateway

Once the configuration on the 3CX part is done, clique on “generate device config” on the top:

The interface of the beroNet gateway opens. Enter your credentials (admin / admin).

If you use version 16.x, the necessary information are already filled in. Otherwise, you need to enter the IP address of the 3CX, the User and Password set in the authentification part of the 3CX and set hardware information of the VoIP Gateway.

Save and activate the settings to finish the configuration.

The post How to configure a beroNet Gateway with 3CX V15 appeared first on beroNet GmbH.

The post How to build a VoIP system using the beroNet Telephony Appliance 2.0 and mobydick appeared first on beroNet GmbH.

The post How to install a complete VoIP System using a beroNet Appliance 2.0 and 3CX appeared first on beroNet GmbH.

How to register your beroNet Appliance 2.0 in the beroNet Cloud:

1. In the interface of the hypervisor, navigate to “Cloud settings” under “Settings” in the web interface of the appliance
2. Enable the Cloud management
3. Enter the credentials of your cloud account you received by email
   
4. Then log into your cloud account under berocloud.beronet.com. The appliance should be connected to it. If it does not appears green (but grey), go back to the cloud settings of the hypervisor and re-enable it. Once it has turned green, click on the device. Information about your appliance and the VMs should be available.
   
5. In order to access the web Interface of the hypervisor, click on “Request GUI”. Let the connection be enabled – it can take up to 3 minutes.
   
6. Once the tunnel has been enabled, you have the possibility to access the hypervisor by clicking on “beroNet Appliance GUI”.
   
   However, to access each VM, a VNC client is needed. I personally use the program “tightVNC” available here: http://www.tightvnc.com/download.php
   Once you have launched the program, you can access each VM by entering the IP of the Cloud and the port opened by it in order to access the VM. Example: 80.244.243.46::20006 which leads to my VM with the VNC 5901. Each VM installed on the hypervisor of the beroNet Appliance can then be accessed. For more information about the Appliance, visit our product page.

To learn more about VoIP technology and hardware, sign up to receive new blog posts in your email.

If you prefer only to receive the best of the best, as well as a list of upcoming beroNet webinars and activities, sign up for our monthly newsletter.

The post How to register your beroNet Appliance 2.0 in the Cloud appeared first on beroNet GmbH.

Connecting a beroNet VoIP Gateway to a 3CX Cloud installation is not difficult. In fact – with a VPN it’s essentially the same process you would use with a local installation. Eddie Vincent from beroNet distributor the Electronic Frontier guides us through a step by step tutorial on how to configure a beroNet VoIP Gateway with a 3CX Cloud Installation.

The post Connect a beroNet VoIP Gateway with 3CX in the Cloud appeared first on beroNet GmbH.

The beroNet Appliance 2.0 is a telecommunication platform with an Intel Celeron Quad Core processor running a pre-installed beroNet Hypervisor. beroNet customers have the possibility to use the hypervisor to virtualize different operating systems enabling the single system to function as a complete communications hub.

The Appliance can also function as a hybrid device capable of pairing SIP with analog, digital and/or GSM technologies using a beroNet PCIe card.

About the hypervisor

The beroNet hypervisor is based on the XEN Project which is an open source hypervisor that allows multiple operating systems to run concurrently on the same hardware. We decided to implement this open source tool on our device to enhance the possibilities of the beroNet Telephony Appliance.

A. Accessing the hypervisor

Before switching on the appliance, connect it to the network. For this, use the left network card on the appliance. This is necessary so that the DHCP server will provide the system with a local IP address that can be detected by Windows UPnP or thanks to the bfdetect tool. An icon called “beroNet Telephony Appliance” will then appear on another computer connected to the same network under “network devices”.

Then you can login using default credentials of the hypervisor: “admin / beronet”. It is strongly recommended that you change the login credentials for your hypervisor after login.

B. Installing an application from the beroNet market

The beroNet market enables integrators to quickly and easily install a new application on the hypervisor. In order to access it, navigate to “market” in the drop down menu under “Virtual Machines+”.

It is then possible to download a complete application from a secure source or only an ISO that will then need to be configured.

The beroNet market is due to evolve thanks to the different technology partners of beroNet, that will make their solutions available on it.

C.   Manually install a new virtual machine in the hypervisor

To get started you need to first download an OS (a) and then create a VM(b).

a) Download the ISO from a webserver or from a Fileserver

In order to download an ISO from a webserver, simply enter the URL  as below. If needed, add the credentials of the web server using the format: “User:Password”.

It is also possible to upload an ISO from a computer or from a file server. The three options are available under the tab “virtual Machines+” and “manage Isos”:

b)     Create a new virtual machine

Under the tab “Virtual Machines+”, it is possible to manage the virtual machines of the hypervisor. In order to create a new one, navigate to the tab “Manage VMs” in the drop down menu.

To create a new VM:

• Give it a name (no spaces);
• Give it one, two or three CPUs;
• Choose how much RAM it should get depending on the size of the appliance (M has 4 GB, L has 8 and XL 16);
• Choose the size of SSD it will be allocated (M has 60 GB, L has 120 and XL 240);
• Choose the ISO file from which the OS has to boot;
• Choose the “Boot-Device”. It should be “d(isofile)” for the installation of the ISO and then “c(disk)” for its use;
• Choose the Network card it will use;
• Give it a “VNC-Display” from 6901 to 6905;
• For a windows installation, add the Windows tools by clicking the box “Windows Tools”.

c) Launch and configure your ISO

Once your OS has been created in the hypervisor, you can easily launch it from the “Dashboard” and start configuring it:

The post How to configure the new beroNet Appliance 2.0 appeared first on beroNet GmbH.

beroNet will be exhibiting at the CeBIT in March 2016. Visitors at the exhibit will have an opportunity to get a close look at the recently released beroNet Telephony Appliance 2.0, and receive a chance to compete in the beroNet Gateway Installation Competition (keep an eye on this space for additional details).

Meet with us there:

Reserve your time to meet with our team and learn more about beroNet Products and services. You can also use this form to reserve a slot to compete in the beroNet Gateway Installation Competition.

The post Meet us at the CeBIT 2016 appeared first on beroNet GmbH.

• It is based on regular expressions (‘Howto RegEx’.)
• It works from top to bottom: if you have a rule that directs all calls to a specific line above a rule that directs a specific number to your fax device, the general rule will apply and the specific rule will not function. Therefore be sure that your specific rules are above your general rules in the dialplan.

In the above shown example, the calls coming from our SIP account will be routed to the first ISDN port only when the number “03025938919” is called. In any other case, the calls will be routed to the ISDN port number two. If we had put the precise rule in a second position, calls would never be routed to ISDN port one.

As this tool is a major part of the way a beroNet gateway works, it is important to fully understand how it works. Let’s take a closer look at the different fields in the dialplan.

1. Direction (From and to ID)
2. Destination and New destination
3. Source and New source
4. Position

1) Direction (From ID and To ID)

Here we choose the technology (SIP, Analog, ISDN or GSM) the call has to come from in order for the rule to apply. Of course, we also choose to which technology the call will be routed to.

When we choose ISDN, Analog or GSM as “from” or “to”, we have the possibility to choose either a group of ports or one port within a certain group.

On the other hand, when SIP is set as “From”, it is possible to choose the “match type”. Different possibilities are then offered: we can match via the IP address, via the from or to user, via a manual address or in a default way.

Usually, dialplan rules work as pair of two rules: when the gateway routes the call from a SIP account to ISDN lines, it is often necessary to route the calls in the other way i.e. from ISDN to SIP. To do this two different rules are necessary: one from SIP to ISDN, and the other from ISDN to SIP.

2) Destination and New destination

The “Destination” field enables a user to make a rule apply when a certain number is being dialed. This field is also known as “CalledID” or “DAD”: If the field is left empty, then the gateway will automatically insert a wildcard “(.*)”. This means that the rule will apply to any number that is called. In our first example, we explained that the first rule would apply when the number “03025938919” is called. Therefore we added this number in the destination field.

The field “new destination” enables the gateway to modify the DAD.The default “\1” sends to the “To” technology the variables that are set between brackets in the “Destination” field.

In the example above, the gateway is transparent meaning that it sends the dialed number the way it received it.

In this example, the rule will apply when the number “1234” is dialed and the gateway will rewrite this number and send “6789” to the “to” technology.

As we said in the beginning, the beroNet dialplan uses regular expressions. It enables our partners to create flexible rules without having to make a long list of possible numbers that can be dialed. It is also a good way to only send a certain number of digits. When a gateway is used to connect a traditional PBX to SIP for example, it is sometimes necessary to send only 4 digits to the PBX. 

Here, the rule applies when a 10 digit number starting with 014661 is being dialed. Then the gateway sends only the 4 digits that are between brackets and leaves the 6 first ones. For more example, see below.

3) Source and New Source

The “Source” field enables beroNet gateway users to make a dialplan rule apply only when the call comes from a certain number. This field is also known as “CallerID” or “OAD”. The same regular expressions are used. The default parameters are the same as for the “Destination” and “New Destination” fields. Here is a default rule:

The “New Source” field enables beroNet users to modify the CallerID with which they call. To call anonymously, we just have to write “Anonymous” in this field. Providers usually do not allow end-users to call with a complete different CallerID but calling anonymously is almost always an option.

If nothing is changed in both fields, then the gateway does a transparent job: it sends the CallerID it receives in source to ISDN / Analog or SIP depending on the direction of the rule.

4) Position

The positions of dialplan rules are very important. As we already explained at the beginning of this blog post: the dialplan “works from top to bottom: if a call matches the parameters of a rule, then the rule will apply. Therefore general rules should be placed under more precised ones.”

Let’s take a look at a few example to understand this better:

In this example, according to the first rule, all calls coming from the “SIP_Account” will be routed to the ISDN ports no matter what the CallerID (OAD) or the the CalledID (DAD) is. This means that each and every call coming from this SIP account will be routed to ISDN.

The second rule says: “calls coming from “SIP_Account” with  “0156638515” as a DAD, will be routed to the analog port number 1″. However, this second rule is more precise than the first one. It will not apply as long as it is placed under it. In order for it to apply, we need to put it in the first row as below:

In this example, we can send some calls to the analog port when the number 0156638515 is being dialed and the rest is sent to ISDN.

5) Understanding the regular expressions

Regular expressions enable beroNet users to create clever dialplan rules. Depending on the information set in the “Destination / New Destination” or “Source / New Source” fields, the dialplan will make a transparent job or change the CID or DAD of a call.

Let’s take a look at some examples:

Example 1:

Destination:       “0176(.*)”    matches if calledID is starting with 0176
New Destination:   “0049176\1”   will cut 0176 from calledID and add 0049176 to the calledID, followed by reference to parameter 1 
Source:            “(..)”        matches callerIDs with exact 2 digits.
New Source:        “25938912”    CallerID will be overwritten by 25938912

Example 2:

Destination:       ”259389([0-8][0-9])”  matches all numbers starting with 259389 followed by 2 digits in the range from [00-89]
New Destination:   “\1”                  will cut 259389 from calledID and add the 2 digits referenced by parameter 1
Source             “(.*)”                matches any callerID
New Source:        “\1 “                 \1 is the value in the first parenthesize of 'Source'

Example 3:

Destination:       ”0([2-9])(.*))”    matches all numbers starting with 0. The second digit has to be in range[2-9] followed by the any digits.
New Destination:   “\1\2”             will cut 0 from calledID and add the parameter 1 followed by parameter 2 
Source             “(.*)”             will match any callerID
New Source:        “\1 “              \1 is the value in the first parenthesize of 'Source' field

The post Understanding the beroNet Dialplan appeared first on beroNet GmbH.