Overview

بقلم ستيف ف، 31 مارس 2026

To date, fax remains a primary method for transmitting legal and official documents in the United States. It is still widely used for prescriptions, legal notices, and government communications. Therefore, the ability to reliably support existing fax services for customers is a critical factor in the success of deploying any POTS line replacement solution.

1 مراجعة موجزة لتقنيات الفاكس عبر IP

1.1 T.30 فاكس

Similar to alarm panels, the T.30 fax protocol was originally developed for PSTN networks and has strict synchronization and latency requirements. When migrated to VoIP networks, traditional fax machines connected via standard ATAs often face issues such as session establishment failure or incomplete transmission. This becomes a particular problem for long documents (e.g., dozens of pages), which often fail to send successfully.

1.2 T.38 فاكس

To address these challenges, ITU defined the T.38 protocol for fax transmission over next‑generation networks (NGN), which rely on protocols such as H.323, H.248 and SIP.

يُعد T.38 بروتوكولًا ممتازًا ويمكنه التعامل مع معظم سيناريوهات نقل الفاكس عبر شبكات IP. ومع ذلك، يقتصر اعتماده على عيبين رئيسيين:

• يجب أن يدعم الطرفان T.38، وفي بعض الحالات قد يكون FEC (تصحيح الأخطاء المتقدم) مطلوبًا أيضًا لتحقيق الأداء الأمثل.

• بسبب مشكلات شبكة IP المتأصلة مثل الكمون، والارتجاع، وفقدان الحزم، لا يمكن لـ T.38 ضمان الموثوقية في جميع الظروف—خاصةً أثناء الازدحام المفاجئ أو انقطاعات الشبكة التي تستمر لعدة ثوانٍ.

1.3 T.37 Fax (eFax)

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

مبدأ T.37 بسيط:

• The ATA emulates a fax machine.

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

• Upon receipt, the ATA converts the TIFF file back to T.30 format and sends it to the fax machine

Regarding how to deliver a TIFF file to the destination, T.37 recommends using email protocols such as SMTP/POP3, although it is not mandatory. For this reason, T.37 is often referred to as the Fax‑to‑Email standard.

Most eFax solutions on the market are variants of T.37. However, because email transport may not meet privacy and security requirements, many applications use dedicated fax servers with secure protocols such as SSL to transfer files.

2 How Flyingvoice MSPs help deliver fax services

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

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

• For T.37, Flyingvoice provides comprehensive API documentation for FlyingvoiceCloud and sample code, enabling MSPs to develop their own fax server storage and transmission system within 1–2 weeks.

2.1 لمزودي الخدمات المدارة الذين يستخدمون بوابات T.38 بالفعل

All Flyingvoice CPE devices replacing POTS lines are fully compatible with T.38.

إذا كان لدى MSP بوابة T.38 مُنشأة مسبقًا، يمكنه ببساطة تمكين T.38 على أجهزة Flyingvoice POTS CPE — دون الحاجة إلى أي عمل تكامل إضافي.

2.2 لمزودي الخدمات المدارة الذين يستخدمون منصات UC الحالية

For managed service providers (MSPs) that only have UC platforms oriented to voice, is it possible to provide reliable fax services without investing in new infrastructure?

Answer yes—using Flyingvoice POTS Media SBC.

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

• منصة UC غير مدركة لوجوده ولا تتطلب أي تغييرات في التكوين.

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

This allows both T.38 and T.30 + SBC to provide real‑time fax services, and provide fax services equivalent to PSTN. Successful transfer confirms that the receiving fax device has received the document.

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

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

• يجب أن يكون فقدان الحزم < 3%

2.3 Managed service providers deploying or planning eFax servers

For managed service providers (MSPs) who have or plan to deploy their own eFax servers, Flyingvoice POTS CPE offers built‑in T.37 support, with FlyingvoiceCloud APIs, enabling rapid development and deployment. For detailed technical documentation, please contact us.

In general, T.37 is a store‑and‑forward solution. The advantage is that it requires very low IP network performance requirements, and fax can be sent and received even under intermittent network conditions.

العيب هو أن ظهور حالة نجاح الإرسال على جهاز الفاكس المرسل يعني فقط أن خادم الفاكس قد استلم ملف الفاكس بشكل صحيح؛ ولا يعني أن جهاز الفاكس المستقبل قد استلم الملف بشكل صحيح. عادةً ما يكون هناك تأخير في تأكيد نجاح إرسال الفاكس، ويتطلب الانتظار عدة دقائق إلى أكثر من عشر دقائق.

3 ملخص: أي حل هو الأفضل؟

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 usually the most suitable. Integration with Flyingvoice solutions can be completed in days, providing reliable POTS line 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 Labs’ assessment, the network typically requires a total end‑to‑end round‑trip time (fixed latency + jitter) of less than 300 ms and a packet loss rate of less than 3 %.

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