Overview

By Steve F, 31 March 2026

To date, fax remains an essential means of transmitting legal and official documents in the United States. It is still widely used for medical orders, legal notices, and government communications. Therefore, the ability to reliably support customers’ existing fax services is a critical factor for the successful deployment of any POTS replacement solution.

1 Brief review of Fax over IP technologies

1.1 T.30 Fax

Like alarm panels, the T.30 fax protocol was originally developed for PSTN networks and imposes strict synchronization and latency requirements. When migrated to VoIP networks, traditional fax machines connected via standard ATAs often encounter issues such as session establishment failures or incomplete transmissions. This is particularly problematic for long documents (e.g., dozens of pages), which frequently fail to be sent correctly.

1.2 Fax T.38

Pour relever ces défis, l’UIT a défini le protocole T.38 pour la transmission de fax sur les réseaux de nouvelle génération (NGN), qui reposent sur des protocoles tels que H.323, H.248 et SIP.

T.38 is an excellent protocol and can handle most fax transmission scenarios over IP networks. However, its adoption is limited by two main drawbacks:

• Both ends must support T.38, and in some cases, FEC (Forward Error Correction) is also required for optimal performance.

• Due to inherent IP network issues such as latency, jitter, and packet loss, T.38 cannot guarantee reliability in all conditions—especially during sudden congestion or multi‑second network outages.

1.3 T.37 Fax (eFax)

To ensure fax reliability even in unstable IP network conditions, the ITU introduced the T.37 protocol, which uses a store‑and‑forward approach.

The principle of T.37 is simple:

• The ATA emulates a fax machine.

• When sending, the ATA receives the fax from the fax machine connected via its FXS port and stores it as a TIFF file.

• When receiving, the ATA reconverts the TIFF file to T.30 format and sends it to the fax machine.

As for how the TIFF file is delivered to the destination, the T.37 standard recommends using messaging protocols such as SMTP/POP3, although this is not mandatory. That is why T.37 is often referred to as the Fax‑to‑Email standard.

Most eFax solutions on the market are variants of T.37. However, since e‑mail transmission may not meet confidentiality and security requirements, many implementations use dedicated fax servers with secure protocols such as SSL for file transfer.

2 How Flyingvoice helps MSPs provide POTS disaster recovery and communication resilience

Flyingvoice's POTS replacement solution provides robust support for the three methods: T.30, T.38, and T.37.

• For T.30 and T.38, Flyingvoice solutions can integrate seamlessly with existing UC platforms without any code changes.

• For T.37, Flyingvoice offers comprehensive documentation of the FlyingvoiceCloud API as well as demo code, allowing MSPs to develop their own fax store‑and‑forward servers in just 1 to 2 weeks.

2.1 Pour les MSP utilisant déjà des passerelles T.38

All Flyingvoice POTS Replacement CPE devices are fully T.38 compatible.

If an MSP has already deployed a T.38 gateway, it can simply enable T.38 on Flyingvoice POTS CPE devices — no additional integration is required.

2.2 For MSPs using existing UC platforms

For MSPs that only have voice‑centric UC platforms, is it possible to provide reliable fax services without investing in new infrastructure?

The answer is yes—using the Flyingvoice POTS Media SBC.

The Flyingvoice POTS media SBC acts as a transparent device for the UC platform:

• La plateforme UC n'est pas consciente de son existence et ne nécessite aucun changement de configuration.

• The SBC handles packet retransmission and error correction between the Flyingvoice POTS CPE (e.g., PR12) and converts traffic into standard G.711 audio streams for the UC platform.

This allows both T.38 and T.30 + SBC to provide real‑time fax services, offering fax services equivalent to the PSTN. A successful transmission confirms that the receiving fax machine has received the document.

T.38 and T.30 performance + SBC depends on network quality. According to Flyingvoice lab tests:

• End-to-end latency (including jitter) must be < 300 ms

• Packet loss must be < 3 %

2.3 For MSPs deploying or planning eFax servers

For MSPs that already own or plan to deploy their own eFax servers, the Flyingvoice POTS CPE integrates T.37 support, combined with FlyingvoiceCloud APIs, allowing rapid development and deployment. For detailed technical documentation, please contact us.

Overall, T.37 is a non‑real‑time (store‑and‑forward) solution. The advantage is that it requires very little IP network performance, and fax sending and receiving can be performed even under intermittent network conditions.

The disadvantage is that the fact that the sending fax machine displays a successful transmission status only means that the fax server has correctly received the fax file; it does not mean that the receiving fax machine has correctly received the fax file. Confirmation of a successful fax transmission often involves a delay, requiring a wait of several minutes to more than ten minutes.

3 Summary: which solution is best ?

For UC service providers, the T.38 approach (if supported by the UC platform) or the T.30 + SBC solution (without UC platform requirements) is generally the most practical. Integration with Flyingvoice solutions can be achieved in a few days, providing reliable POTS replacement services without modifying existing systems.

The T.38 or T.30 + SBC approach is suitable for installation sites with relatively good network conditions. According to Flyingvoice lab evaluations, the network generally requires an end‑to‑end global latency (fixed latency + jitter) below 300 ms and a packet loss rate below 3 %.

For installation sites with poor network conditions, such as frequent jitter above 500 ms, packet loss rates above 5 % or frequent network outages, the store‑and‑forward T.37 approach is a better choice.