by SteveF, April 5, 2026
The modem technology was born in the 1950s and was among the first communication technologies to connect computers. In 1958, AT&T launched the Bell 103 modem, which achieved a transmission rate of 300 bps, paving the way for data transmission over the PSTN network and enabling, for the first time, remote computer communications.
In the 1960s–1980s, modem technology rapidly spread in commercial and industrial applications. At that time, computers were all equipped with RS232 serial ports — just as modern computers are all equipped with Wi‑Fi. The DTE/DCE interface and the standard AT command set were also standardized during this period. Even today, we still refer to network devices using 4G/5G technology as cellular modems, and these devices continue to rely on the AT command set.

Today’s youth find it hard to imagine that 30 years ago, people mainly accessed the Internet via a device called a “modem” (see the image above). With the Internet boom in the 1990s, modem speeds quickly increased—from early rates of 9.6 kbps and 14.4 kbps to 33.6 kbps (V.34 standard), eventually evolving to the theoretical limit of 56 kbps on analog lines (V.90/V.92 standards).
56 kbps represents the theoretical limit of PCM lines, but this bandwidth is clearly insufficient to meet the demands of Internet development. Thus, at the turn of the year 2000, modems were quickly replaced by xDSL and then by PON technology. Today, the dominant wired Internet technology is Giga PON, which is currently evolving toward 10 G PON.

Cependant, l'application de la technologie modem va bien au-delà de la simple connectivité Internet. Même avant l'ère d'Internet, les modems étaient déjà largement utilisés dans divers scénarios nécessitant une communication à distance — par exemple, les systèmes POS de caisses enregistreuses, les applications SCADA, les panneaux d'alarme ou la programmation à distance des téléphones d'urgence. Ces applications restent également très répandues aujourd'hui
1. Challenges posed to modem applications by the PSTN switch of
The PSTN is a clock‑synchronised network. Although the PSTN can experience transmission errors due to environmental interference (such as lightning), it only has very low, fixed latency and no jitter. In contrast, IP networks are characterised by asynchrony; jitter on the order of tens or even hundreds of milliseconds is fairly common, and communication interruptions of several seconds can even occur.
Modem protocols heavily depend on PSTN network synchronization functions. For example, consider the SIA FSK F2 format, which is a modem protocol similar to Bell 103.

As shown in the figure above, the SIA FSK F2 format requires recognition of the start bit then proceeds to receive 8 data bits at a rate of 42.7 baud. This protocol can tolerate a certain amount of jitter, but clearly, the maximum jitter duration must not exceed 23.42 ms (1000 ms / 42.7); otherwise, data recognition will become "misaligned," leading to communication errors.
The SIA FSK F2 format is a very low‑speed modem communication protocol. Although it also uses FSK, its baud rate is only 42.7, far below the 300 bps defined by Bell103. Even so, the SIA FSK F2 format can tolerate only 23.42 ms jitter—a requirement clearly too strict for IP networks. That is precisely why most UC platforms designed for voice communications cannot directly support modem communications.
2. ITU Standards for Developing Modem Over IP Solutions
《ITU V.152 Procedures for Supporting Voice-Band Data over IP Networks》 aims to provide a generic transmission method for voice-band data (VBD) based on G.711. It defines a basic approach for automatic recognition of voice codecs such as G.729 and for switching between Voice and VBD modes. At the same time, V.152 also specifies an Assure VBD mode that supports RED and FEC.
The unsecured VBD mode defined in V.152 generally cannot operate due to the modem's sensitivity to jitter. In contrast, the secured VBD mode works exceptionally well in environments where jitter is not severe. Unfortunately, most UC platforms do not directly support RED or FEC.
When jitter is significant, V.152 also experiences a substantial increase in failure rates. In these cases, it becomes necessary to use another ITU-defined standard—the V.150.

The main content of the V.150 specification is defined in "V.150.1 Modem‑over‑IP networks: Procedures for the end‑to‑end connection of V‑series DCEs", which describes a relay communication model.

V.150.1 also defines the SPRT (Simple Packet Relay Transport) protocol, which implements reliable UDP‑based transmission. V.150.1 addresses the modem relay transmission problem by decoding the modem protocol on the gateway device (e.g., Flyingvoice’s PR12 or PR18) and converting it into IP packets, which are then transmitted via the SPRT protocol to the called party (usually another gateway also supporting V.150.1) and reconverted into modem signals. Since the modem protocol is decoded locally into IP packets, the effects of IP network jitter are naturally avoided, enabling reliable modem transmission.
3. How does Flyingvoice's POTS Replacement help MSPs build a reliable modem communication platform?
The MSPs can use Flyingvoice’s POTS media SBC to enable V.152 mode. Assure VBD, or deploy Flyingvoice POTS terminals at both ends and use the V.150 protocol to implement Modem Relay transport.
3.1. Implement V.152 Ensure VBD mode using the Flyingvoice SBC Media

Comme le montre la figure ci‑dessus, le SBC média POTS Flyingvoice est un serveur cloud déployé sur AWS. Il est responsable de la conversion des données en mode V.152 Assure—où la méthode RED/FEC est activée—en données G.711 standard et de leur transmission à la plateforme UC déjà déployée par le MSP. Sans nécessiter aucune modification du réseau existant, le MSP peut exploiter le dispositif POTS Flyingvoice pour fournir des services de transmission modem fiables.
The V.152 + SBC mode is suitable for scenarios with relatively good network conditions. According to Flyingvoice laboratory evaluation, the total end-to-end latency (fixed delay + jitter) of such a network should generally be less than 300 ms, and the packet loss rate should be below 3 %.
3.2. Deploy Flyingvoice POTS devices at both ends to obtain a direct V.150 connection.
For installation sites with poor network conditions — for example those with frequent jitter over 500 ms, packet loss rates over 5 % or frequent network outages — the V.150 protocol is a better choice.
However, this requires both CPEs to support V.150. While Flyingvoice does not mandate that both ends use Flyingvoice devices, to simplify management and maintenance we recommend using Flyingvoice POTS Replacement devices (such as PR12 or PR18) at both ends.

4. Summary
In the United States today, modems are still widely used in legacy devices such as alarm panels, emergency phones (elevators and blue boxes), inbound programming, SCADA systems, point‑of‑sale terminals, etc. With the imminent closure of the PSTN, the communication problems of these devices must be urgently resolved.
MSPs can leverage Flyingvoice CPE devices (such as PR12 and PR18) and POTS media SBCs to quickly integrate into their existing UC platforms and provide customers with reliable modem transmission services.
