beroNet

VoIP gateways and session border controllers

beroNet builds the hardware that keeps existing telephony working while the network around it moves to SIP — ISDN, analog and LTE on one side, SIP on the other. Developed and manufactured in Germany.

See the rangeStart from the situation

beroNet enterprise session border controller seen at an angle from the front: a slim metal housing with two module slots of four RJ45 ports each

What the device does

On one side the lines that already exist — ISDN, analog or mobile. On the other side SIP: a provider trunk, an IP PBX, or both. Every device runs the same beroNet OS and can be managed remotely from the beroCloud.

Overview: ISDN BRI and PRI lines, analogue a/b lines and LTE mobile all terminate on a beroNet gateway or eSBC running beroNet OS. On the SIP side the device connects a provider SIP trunk and an IP PBX or UC platform. The beroCloud manages the device remotely.beroCloudremotemanagementberoNet gatewayor eSBCberoNet OS · up to two moduleslinesSIPSIP trunkIP PBX or UCISDN · BRI / PRIAnalogue · a/bLTE · mobile
Existing lines on one side, SIP on the other. The device converts between them; the beroCloud manages it remotely.

The range

All families, with the comparison table

beroNet Cloud: remote management without an open port

The device opens the connection, not the cloud. A beroNet gateway sends an HTTPS request outward about once a minute, reports its state and picks up whatever task is waiting for it — nothing from the outside has to reach into the customer network, no inbound port has to be opened in the firewall, and NAT is not a problem. From the browser you watch a whole fleet, roll out configuration and firmware updates across it, scheduled if you want, get a notification when a device drops out, and back up and restore a device configuration. How the beroNet Cloud works, or sign up at berocloud.beronet.com — the first 30 days are free.

Fleet management with the beroCloud. At the top, two administrators work in a web browser: they manage, configure and update the fleet, and a notification reaches them when a device drops out. In the middle sits the beroCloud with the fleet dashboard. Below it, three customer sites — Site A, Site B and Site C — each hold a beroNet gateway behind the customer firewall. Each gateway opens an outbound HTTPS connection to the cloud about once a minute, reports its state and collects whatever task is waiting for it: a configuration change or a firmware update, scheduled if needed. No inbound port, no port forwarding and no NAT rule are required, because every connection is opened from inside the customer network.Adminweb browserAdminweb browsermanage, configure,update the fleetnotification when adevice drops outberoCloudfleet dashboardthe device dials out —HTTPS about once a minutetasks wait in the cloud:configuration, firmwareNo inbound port, no port forwarding, no NAT rule — every connection is opened from inside.Customer firewallSite AberoNet gatewayCustomer firewallSite BberoNet gatewayCustomer firewallSite CberoNet gateway
One or more administrators manage a fleet across several sites from a browser. Every connection is opened by the device, outward through the customer firewall.

Start from the situation

  • The provider switches off ISDN

    The PBX works and stays. A BRI or PRI gateway puts the SIP trunk in front of it.

    How that works

  • Analog devices have to survive

    Fax, door intercoms, lift emergency phones. An FXS gateway bridges them in hardware.

    How that works

  • The line must not be the single point of failure

    LTE as a second path, or a failover switch that re-routes the lines physically.

    How that works

  • Two sites, two PBX systems

    SIP to SIP bridges both and normalises what they disagree about — the SBC role.

    How that works

One module system across the range

A modular gateway takes up to two modules — BRI, PRI, FXS, FXO or LTE — in a single chassis. The installation decides the configuration, not the catalogue. Ports can be switched between NT and TE mode in the web interface; no jumpers, no rebuild.

  • Since 2002Developed and manufactured in Germany.
  • One OSEvery device runs beroNet OS and answers the same REST API.
  • No licenceISDN, analog and LTE to SIP is included. Only SIP to SIP needs one.
  • 2 + 3 yearsTwo years warranty, extendable to five.

Works with standards compliant PBX systems — among others 3CX, STARFACE, pascom, IPTAM and snom.

Where to buy

Order the current configurations directly in the beroNet shop, or through a distributor in your country. Not sure which configuration fits? Describe the installation and we will name it.

Support and documentation

Technical documentation lives in the beroNet Wiki, support requests go through the Service Desk. Both are open to every customer during the warranty period.