Standby For More Details
One POTS Replacement Strategy Does Not Fit Every Customer
Posted by: Vola Networks
Sep 29, 2026
Views:3609

One of the most common questions in a POTS replacement project is:

“Which hardware (ATA) should I use?”

It sounds like a straightforward product-selection question.

But the better starting point is:

“What does the application actually require?”

A single elevator emergency phone, a commercial building with eight analog devices, a fire alarm panel, and a remote industrial installation may all be classified as POTS replacement applications.

But they do not necessarily need the same hardware, connectivity, power architecture, or management strategy.

The best POTS replacement approach starts with the application—not the product catalog.



Step 1: Identify What Is Connected

The first question should always be:

What legacy device are we replacing the POTS connection for?

Common applications include:

  • Elevator emergency phones
  • Fire alarm panels
  • Access control
  • Fax machines
  • Legacy modems
  • Utility monitoring equipment

This matters because different applications have different communication requirements.

An elevator phone primarily requires reliable voice communication.

An alarm panel may require specific signaling protocols.

A fax machine needs data transmission characteristics that are different from ordinary voice.

A modem may have its own compatibility requirements.

The first mistake in POTS replacement is treating all analog endpoints as if they were the same.



Step 2: Determine How Many Lines Are Required

The number of analog endpoints is another basic but important consideration.

A single emergency phone does not require the same architecture as a commercial building with multiple elevators and alarm systems.

For compact applications, the PR12 provides two FXS ports in a compact cellular platform. Its dual SIM capability, VoLTE support, and integrated battery backup make it suitable for applications such as elevator emergency phones and smaller distributed deployments.

For higher-density deployments, the PR18 provides eight FXS ports and 5G RedCap connectivity, along with dual WAN capability and battery backup.

The PR08-Pro also provides eight FXS ports and is designed for multi-line VoIP deployments with dual Gigabit WAN connectivity and network failover.

The objective is to match the port density and architecture to the actual deployment.



Step 3: Look at the Available Network

The next question is:

What connectivity is available at the site?

Some buildings have reliable wired Internet.

Some have poor or unavailable broadband.

Some remote locations may have cellular coverage but no practical wired connection.

This is why cellular and IP-based POTS replacement should be evaluated according to the actual environment.

The LM150, for example, provides a compact VoLTE solution for single-line applications and has completed AT&T, Verizon, and T-Mobile certifications.

For applications where cellular is the primary communication path, carrier availability and signal conditions at the installation site should be evaluated before deployment.



Step 4: Evaluate Power Requirements

Power requirements can vary significantly depending on the application.

For ordinary office equipment, a short power interruption may be acceptable.

For an elevator emergency phone or another critical communication application, availability during a building power outage may be much more important.

This means the gateway's battery backup, connected equipment, and overall power architecture need to be considered together.

Backup power should not be treated as an afterthought.

It is part of the communication design.



Step 5: Understand the Communication Protocol

Another important question is:

What is actually being transmitted?

If the application is voice, the architecture may be relatively straightforward.

But if the system is transmitting alarm signaling, fax, or modem data, additional consideration may be necessary.

The Vola POTS Media SBC is designed to support legacy analog communication applications including alarm signaling, fax, and modem transmission across modern IP-based infrastructure.

This highlights an important principle:

The analog interface is only one part of the application.

The media and signaling requirements need to be considered as well.



Step 6: Consider the Installation Environment

Where will the device be installed?

Inside a controlled equipment room?

Inside an elevator environment?

At a remote utility site?

In an industrial or outdoor location?

Environmental requirements can influence the hardware decision.

For example, the PR18's IP65-rated enclosure provides an option for applications where additional environmental protection is required.

A product that works perfectly in an office environment may not necessarily be the right choice for a remote industrial installation.




Step 7: Think About What Happens After Installation

Finally, ask:

Who will manage the device after the installer leaves?

This question is becoming increasingly important as organizations deploy hundreds or thousands of POTS replacement gateways.

With VolaCloud, organizations can centrally manage supported devices, monitor operational information, and remotely access device web interfaces for troubleshooting.

This allows technical teams to investigate many issues without immediately sending someone to the site.

For MSPs, this can turn a collection of individual devices into a manageable fleet.

PR12, PR18, PR08-Pro, and LM150 each address different deployment requirements. POTS Media SBC can provide an additional layer for specialized analog communication applications, while VolaCloud provides centralized management for the deployed infrastructure.

There is no single gateway that needs to fit every customer.

And that is actually a good thing.

The goal of POTS replacement is not to standardize every application into the same box.

The goal is to build a standardized deployment strategy that can accommodate different applications.

Because the right question isn't:

“Which POTS gateway is the best?”

It is:

“Which architecture is right for this application, this environment, and this customer?”