Solutions for All-IP migration and failover

Four situations account for most beroNet installations. Each one has a device behind it — but the situation comes first.

The provider switches off ISDN, the PBX stays

The PBX works, it is paid for, and replacing it is a project nobody has budget for this year. A BRI or PRI gateway puts the SIP trunk in front of it: the PBX keeps speaking ISDN, the provider gets SIP. With a 2 PRI device the old and the new system can run side by side while extensions move over one department at a time.

Analog devices have to survive the move

Fax machines, franking machines, door intercoms, lift emergency phones, alarm diallers, EC card terminals. They do not speak SIP and they never will. An FXS gateway bridges them transparently in hardware instead of re-encoding them, which is what makes fax and modems work at all.

The line must not be the single point of failure

Two ways, often combined. A VoLTE eSBC adds a mobile path that takes over when the SIP provider or the internet connection is gone. A failover switch physically re-routes analog, BRI or PRI lines to a backup when the primary system stops answering. The Survival Branch Appliance app keeps a site making internal calls even when the hosted PBX is unreachable.

Two sites, or two PBX systems that have to talk

The SIP-to-SIP function bridges two IP PBX systems, normalises what they disagree about and terminates both signalling paths. This is the SBC role, and it is the one function that needs an SBC licence.

---

Which device fits depends on port count, concurrent calls and where the demarcation sits. Get in touch with the scenario and we will name the configuration — or go straight to the shop.