A high-capacity FXS gateway is usually specified by one number: how many ports it has. That number matters, and the AGW series supports up to 192 FXS ports in a 2U chassis. But port count alone does not determine whether the gateway will keep working in a nursing home at 3 a.m. during a power outage, or in a hotel where the phone lines also carry alarm panels and fax traffic.

The AGW1 (1U) and AGW4 (2U) are built with four things that most gateways in this category treat as optional or leave out entirely.

Battery backup sized for the actual requirement

A POTS line in a commercial building is expected to survive a power outage. Building codes and regulators treat this as a requirement. Most FXS gateways either have no battery option or offer one that keeps the device alive long enough to shut down gracefully.

The AGW takes an optional battery pack provides up to 24 hours of standby and one hour of emergency calling on eight concurrent lines. The battery unit is hot-swappable, so it can be replaced without taking the gateway down. The goal is to keep phones working through the duration of a typical outage, which usually means several hours, not the few minutes a UPS provides.

In a nursing home where residents may need to place a call during an outage, this is the difference between a phone system that meets the building code and one that actually works when it needs to.

Cloud monitoring and management

Most gateways in this class are managed through a local web interface or an SNMP platform that treats them like any other network device. The AGW integrates with Flyinglink, which gives the operator visibility into the device without logging into it.

The platform receives alerts when the SIP registration drops, when the primary network fails over to the backup, or when the battery is running low. These events can be delivered through web notifications, email, or API, so they reach whoever needs to act on them rather than sitting in a log.

The sensor ports are where the monitoring goes further than what most gateways offer. The AGW has five sensor inputs that accept fire alarms, door open sensors, flood detectors, humidity sensors, and surge protection devices. When a sensor is triggered, the event goes to Flyinglink and can be correlated with the voice infrastructure in the same dashboard. A door open sensor on a telecom closet can tell you someone has been inside before the phone system starts behaving oddly. A fire alarm input can be tied into the same notification chain that already handles life safety.

Configuration and updates are handled through TR-069, including TR-104 for voice parameters. Firmware upgrades are delivered over the air from Flyinglink. There is no need to schedule access to each device or send someone to apply a patch.

Dual uplink with 4G modem backup and shared power

The AGW has two uplink ports: one SFP and one RJ45, both gigabits. A site can run a primary fiber connection with a secondary broadband connection and automatic failover between them.

For sites that need cellular as the backup path, the AGW provides 12V and 5V DC output ports (2A max each). A 4G or 5G modem can be connected and powered directly from the gateway. When the building loses power, the modem continues running on the AGW's battery. The backup network path stays up for the same duration as the voice system.

Without this, a gateway with battery backup but a modem on wall power will lose its network connection before it loses its voice processing. The AGW keeps both alive from the same battery.

Modular design for expansion and field repair

The AGW is a chassis with interchangeable modules: subscriber units (each with 32 or 48 FXS ports), battery units, power units, and a fan module on the 2U model. All modules are hot-swappable.

A site can start with 32 ports and add another subscriber unit when demand grows, up to the chassis limit. The AGW1 and AGW4 accommodate different numbers of modules, so the same product family covers a small hotel and a large campus without forcing a platform change.

When a component fails, the failed module can be pulled and replaced on site while the rest of the gateway keeps running. In a deployment with multiple sites, this is the difference between a field swap that takes minutes and a gateway that is down for a week waiting for an RMA.

Where it fits

The AGW is designed for facilities where the copper lines carry more than voice. In a nursing home, the same FXS ports serve resident phones, nurse call systems, and alarm panels. In a hotel, they handle guest phones, fax for booking confirmations, and modem traffic from legacy building systems. In a school, they connect emergency phones and paging systems.

Battery, monitoring, network backup, and modularity are the things that determine whether a gateway keeps a building's communications running through the situations that actually cause them to fail. Port count tells you how many lines the box can handle. But AGW tell you whether those lines will still be working when they are needed most.