Buyer’s shortcut 🔥

Skip the research, sales pitch & spam.

Take the Dialvice 5-Minute Quiz to find your precise Cloud Phone System.

75% of buyers prefer a “rep-free” experience, Gartner.

• Minutes vs. Pages: T.38 SIP trunks bill by real-time duration ($0.02–$0.035/min), while cloud APIs charge per page ($0.05–$0.12/page). At volume, per-minute trunks cost far less.
• Baud Rate Impact: Heavy graphics or slow modem connections lengthen call times and raise per-minute carrier costs.
• ECM Overhead: Enabling ECM prevents dropped pages but adds 10%–15% to call duration, slightly increasing usage fees.
• Hardware Overheads: Connecting physical fax machines requires HTTPS-capable ATAs to stop local SIP ALG corruption.
• Audit & Optimization: Plain white cover sheets, local DIDs, and restricted retry policies cut average transmission times and prevent wasted call minutes.

The short answer ⚡

T.38 Fax SIP trunks cost $7 to $25 monthly per trunk, plus $0.02 to $0.035 per minute for domestic transmission.

Because a standard text page takes 30 to 50 seconds to clear, per-minute T.38 trunks cost up to 60% less at volume than per-page cloud fax subscriptions.

Data Flow Architecture: 

Physical Fax / MFP  ➡️  T.38 Encrypted ATA  ➡️  T.38 SIP Trunk (SIP TLS / SRTP)  ➡️  T.38 Carrier PSTN Gateway  ➡️  Recipient Fax Engine

Healthcare scenario: A clinic’s failed fax

A 15-location regional healthcare network generated 45,000 inbound referral and record pages monthly using physical multi-function printers (MFPs) and an on-premises fax server.

Facing a 300% price hike on copper POTS lines, IT migrated to standard voice SIP trunks.

The result was a failure: 35% of faxes dropped due to G.711 packet loss, creating critical patient processing backlogs.

To fix it, they deployed T.38 SIP trunks. Also, they installed T.38 ATAs at clinics and hooked their fax server to SIP webhooks.

At $0.025 per minute (averaging 42 seconds per page), their monthly usage bill settled around $787.

That delivered nearly $2,000 in monthly savings compared to a $2,700/month cloud API quote.

💡 Derek’s Pro Tip: Want to ditch your SIP trunks, ATAs, and on-prem phone system entirely? Explore a digital POTS Replacement solution (fax, elevator, alarm, etc.) and a modern cloud phone system.

T.38 SIP trunking vs. Cloud Fax API pricing

Choosing how you purchase fax capacity changes how your operational costs scale with volume. You have two primary pricing models:

Transmission physics: How page speed impacts invoices

Because T.38 SIP trunks bill by the minute rather than the page, document transmission times dictate your total monthly bill:

Modem negotiation speed (baud rate)

T.38 endpoints try to negotiate at V.34 speeds (33,600 bps). Legacy PSTN lines or destination machines often down-negotiate to V.17 speeds (14,400 or 9,600 bps), doubling transmission time and doubling your per-minute cost.

Document density & resolution

Standard resolution (200×100 DPI) plain text transmits quickly. High-resolution text, signatures, or greyscale images create heavy payloads that extend call times.

Error correction mode (ECM) retries

ECM re-requests corrupted frames during packet loss. While ECM guarantees 100% page clarity, poor network connections trigger multiple retries, turning a 1-minute transmission into a 2.5-minute billable call.

💡 Derek’s Pro Tip: Cap maximum transmission speeds on ATAs and fax servers at 14,400 bps (V.17). V.34 sounds faster, but its sensitivity to jitter causes transaction retries that cost more in failed call minutes than a stable V.17 connection.

Hidden line items in T.38 carrier bills

When evaluating quotes for T.38 SIP trunking, look beyond the raw per-minute rate.

Carrier quotes frequently leave out these four backend charges:

• Billing increments: Choose 6-second or 1-second rounding with a 6-second minimum. Carriers using 60-second minimums bill a 61-second transmission as 2 full minutes.
• Inbound toll-free surcharges: Inbound faxes to Toll-Free DIDs (800/888/877) cost $0.045 to $0.06 per minute, compared to $0.025 for local DIDs.
• T.38 fallback rates: If a destination carrier lacks T.38 support, some providers fall back to G.711 passthrough while charging higher specialty rates.
• HIPAA & BAA charges: Cloud fax vendors often add 20% to 50% markups for a BAA. Dedicated T.38 SIP trunking providers typically include BAA coverage at no added cost because media in transit is encrypted via TLS/SRTP.

💡 Derek’s Pro Tip: Avoid basic SIP ATAs for physical fax machines. Standard router firewalls with active SIP ALG settings frequently corrupt T.38 INVITE packets. Instead, deploy dedicated T.38 hardware or ATAs supporting Fax over HTTPS (FoHTTPS).

Auditing and lowering your T.38 transmission spend

If your business handles significant fax volume, use this checklist to streamline your FoIP (Fax over IP) architecture:

1. Audit document density: Replace dark cover sheets, shaded backgrounds, and heavy logos with plain white backgrounds to cut average page transmission times by 15 to 20 seconds.
2. Use local DIDs for inbound: Move inbound channels off 800 Toll-Free numbers and onto local DIDs to instantly lower per-minute costs.
3. Use dedicated T.38 carriers: Avoid running fax traffic over general voice SIP trunks. Partner with specialized T.38 carriers (like T38Fax or Power-T.38) built for low latency and direct telco peering.
4. Limit automatic retries: Set fax servers to cap failed transmission retries at two attempts spaced 5 minutes apart to avoid burning minutes on dead lines.

Streamline your FoIP migration

Switching from legacy copper POTS to T.38 Fax SIP trunks delivers essential cost control and reliability.

Understanding modem speeds and avoiding per-page rounding traps are critical first steps.

Choosing dedicated T.38 infrastructure ensures reliable document delivery while keeping monthly telecom expenses predictable.

Need quotes for T.38 SIP Trunks or POTS Replacement (elevator, alarms)? Contact us

Shopping for your exact cloud phone system? Start here. 👇

Frequently Asked Questions

Why do standard VoIP voice trunks fail when sending a fax?

Standard VoIP trunks use codecs optimized for human speech (G.729/G.711). Faxing relies on precise analog modem tones. Minor packet drops, jitter, or compression algorithms corrupt these tones, breaking synchronization and dropping the call.

Is T.38 Fax over IP HIPAA compliant for healthcare organizations?

Yes. T.38 is HIPAA compliant when encrypted using SIP over TLS for signaling and SRTP for media streams. Ensure your T.38 carrier signs a formal Business Associate Agreement (BAA) covering data in transit.

What is Error Correction Mode (ECM), and why is it required for T.38?

ECM breaks page data into small packets. If packet loss corrupts data during transmission, ECM detects the error and requests that specific frame again. Without ECM, internet jitter causes blacked-out lines, cut-off pages, or failed transmissions.

Can I keep my existing fax numbers when switching to a T.38 SIP trunk?

Yes. Federal LNP (Local Number Portability) rules allow you to port local and toll-free fax numbers from legacy copper carriers directly to your new T.38 provider without downtime.

Notice: For informational purposes only. Emergency systems must be installed by certified professionals to ensure local code compliance.