The beroNet Telephony Appliance is the ideal platform for customers and technology integrators, looking for a reliable hardware solution, with integrated ISDN, Analog and GSM connectivity.
The beroNet Telephony Appliance’s elegant design delivers superior energy efficient properties and is designed specifically for the rigorous 24/7 uptime demand of modern telephony systems. With a power consumption of less than 24W during normal operation, over 200 EUR can be saved in electricity costs per year.
With its fanless design and harmonized components the beroNet Telephony Appliance is the suitable solution for all kinds of telephony projects. The beroNet Telephony Appliance is designed for telephony applications in the SOHO and SME markets and is perfectly suited for businesses with up to 60 concurrent calls.
The most amazing feature is its built in beroNet Hypervisor, which allows user to run multiply apps simultaneously. A PBX, Faxserver and Firewall can run on the same hardware platform and be maintained via a WebGUI. The appliance is the embedded low power Datacenter for your office.
The beroNet Hypervisor is built on the Alpine embedded Linux with the XEN Kernel. This allows to use minimum ressources of physical Machine for the hypervisor itself and give most of the ressources to the Virtual Machines. The hypervisor only requires 2GB of disk space and 1 GB of Memory.
After powering up and after a few seconds the appliance should receive an IP Address from your local DHCP Server. There are several ways to obtain the IP Address of the Hypervisor:
The windows built in network discovery tool should find the beroNet appliance. It shows an icon and the IP of the appliance. By double clicking you will be forwarded to the Hypervisor webinterface.
Another option is bfdetect. With bfdetect you can discover the appliance via the windows or linux command line. bfdetect shows the serial Number, the Hypervisor Version, the MAC address and the IP Address of the Appliance. The following bfdetect output shows an appliance and a gateway. The Appliance Serial-Numbers start with 20 followed by the amount of RAM and finally by the serial itself.
Please wait, while we're scanning on all interfaces for beroNet devices... 1) serial: 20-16-0000000004 type: Appliance appfs: 0.2 mac: 00:13:3b:10:08:48 ip: 172.20.10.10 2) serial: 2-16-0000012238 type: Gateway appfs: 3.0.03-Phone-Detect-rc001. mac: d8:df:0d:00:22:e8 ip: 172.20.10.9 Please, select a device (enter 'q' to leave): |
With bfdetect you can also switch from DHCP to a static IP which can be set manualy, by choosing the index of the device and then following the configuration steps.
As soon as you have accessed the Hypervisor Webinterace you can login with the default credentials:
Make sure to change the password in the menu under "System->change password".
The Hypervisor GUI allows it to:
To install an operating system as a VM you need to follow the steps:
The dashboard shows all VMs and all ISO files.
Each VM can be started by clicking the "start" link if they are in the state "STOPPED". If they are in the state "RUNNING" the VM can be accessed via VNC, halted via the "shutdown" link or powered off via the "Poweroff" link.
By default each Virtual Machine starts a VNC Server on the Ports between 5900 - 5905. Any VNC tool can connect to this port, e.g. tightvnc for linux and windows: TightVNC
The Dashboard provides a built-In WebtRTC based WebVNC Client from Kanaka: noVNC Client. As the VNC Server of the VM is not a WebRTC Server, a WebRTC Proxy is used to connect the VM VNC Server and the noVNC Client. We're using again Kanakas Socket Proxy: websockify for that.
The Websockify Proxy opens a WebRTC Port on the Ports 6900 - 6905 corrresponding to the VNC Server ports. This needs to be understand and considered when creating NAT rules to the Hypervisors WebGui. It is easier to use an external VNC client like tightvnc in this case (the VNC port must still be natted).
The following picture shows how a browser can use the WebVNC on port 6900 and the Webserver on port 80 and how a VNC client can directly connect to the VMs VNC Server on port 5900:
Under "Virtual Machines->Manage VMs" you create new VMs, delete or rename existing ones.
By clicking on New the VM Create wizard opens and allows to create a new vm.
After clicking on Create you can modify the VM Details in the VM Manager.
In the List of Virtual Machines you can always find a "manage" button which brings you the the VM Manager of this machine.
The VM Manager divided in different sections:
STATUS
Shows the current status of the VM and allows to do actions with it. The actions are:
Additionally you can use the built-in WebVNC tool to connect to the console of the VM.
SYSTEM
In the System Settings you can define:
NETWORK
Under the network settings you can define:
Also the MAC Addresses of the VM are visible here. The WAN Mac Address is only relevant in the lan-wan mode.
DISKS
The Disks Manager allows to create, delete and reorder virtual disks. Also It defines if an ISO Intallation Medium is inserted in the VM. NOTE: a deleted disk can not be recovered!
OTHER
Under other, you can mainly find the VNC and miscellaneous settings:
The Hypervisor can backup & restore both full VMs and ISO files. In the Backpup & Restore-Manager the attached USB drivers are displayed.
If no disk was found, attach a USB drive and click on "scan for new devices". If the drive is not yet a "backup-space" for the Hypervisor, the drive needs to be formatted as backup space.
To make a backup or restore already made backups click on the USB drive link.
In the restore tab, previously backuped ISO files and Apps (VMs) can be restored back to the hypervisor disk. This may take several minutes and even hours depending on the file size and if the file is compressed. The backups can also be deleted here.
In the "Backup-Tab" local VMs and ISO files can be backuped. VMs can be compressed in order to save drive space.
Make sure that the drive is large enough to hold a complete VM. Creating a backup can take several minutes and even hours, depending on the filesize and wether compression is used or not.
The iso manager shows the lokal stored ISO files which can be used to boot a VM to install the OS provided in the ISO file (e.g. an Ubuntu ISO for installing Ubuntu in a VM). Isos can be deleted via the "delete" link.
There are 3 ways to get an ISO on the appliance:
Domain e.g. beroNet
Share Name e.g. //beronas/ISOs (the share is only one Folder on the Server, like //SERVER/SHARE and SHARE does not have subfolders)
user e.g. beroUser
password e.g. beroPassword
The beroNet Appliance Market allows it to download pre-installed Virtual Machines. These machines can be started directly in the Hypervisor. The Market also allows to donwload ISO Installation Media for setting up new Virtual Machines.
Each VM or ISO has additional Meta Information like the version and the size. By clicking the download icon the VM or ISO will be downloaded to the lokal appliance.
NOTE: this can take several minutes or even hours, depending on the size and internet speed.
The beroNet hypervisor GUI allows to create thin clones of existing VMS. A clone is not a full copy of a VM. The disks of the clone reference back to the parent so that only the differences for each clone are stored within the clone, while the main data resides within the parents disk. The mechanism used here is copy-on-write. The parents disk is not modified while the clones run, this means the parents VM state is saved as a snapshot. When the clones are deleted the parent can run again from the moment on when the first clone was created. At later times other clones can be created from the parent or even from clones.
The result is a tree, like in this example:
NOTE: only the orange leaves of the tree can actually run. But indeed they can run at the same time!
"Parent" and "clone 2" can be seen as snapshots as they preserve the VM state at the time when they ran at last.
Create a clone:
To create a clone you need to go to the VM Manager of a VM on the STATUS Tab and click on "clone" and then provide a name of the clone (You can only create clones of powered of VMs).
After that the cloned VM becomes a parent and is in the STATUS CLONED:
Also a list of all clones of this VM is displayed:
You can always create new clones from this parent VM. These clones will have the state of the parent last time it was powered off.
To update the hypervisor, simply click on the Version which you want to install.
The Network Manager allows to choose the Interface Mode of the appliance:
The LAN Mode can be defined as DHCP or static. If it is static the LAN Settings need to be defined. These settings do only apply to the LAN interface of the Appliance. The WAN Port however can only be controlled from within a VM which has the LAN-WAN mode enabled.
The cloud manager allows to register the appliance into the beroNet cloud or into a private beroNet cloud. After successfull registration a cloud key appears. The appliance starts communication with the beroNet cloud after enabling the cloud and after clicking "cloud enable".
NOTE: a reboot of the hypervisor might be needed to register the appliance in a different cloud'
By clicking "CLICK HERE FOR REBOOTING THE APPLIANCE", the appliance does a reboot.
NOTE: all VMs will be halted ungracefully
By clicking "CLICK HERE FOR SYSTEM SHUTDOWN", the appliance will turn itself off.
NOTE: it is not possible to turn on the appliance from remote
Under System->change password, the password of the admin GUI User can be changed.
The Gateways Manager starts a bfdetect in the background and shows a list of all local appliances and Gateways with their Serials, Firmware Versions, IP Addresses and MAC Addresses.