VOS3000 how-to

Fax over VOS3000: T.38 and G.711

Fax is unforgiving: one lost packet can end a page. Choose the right mode for each route and most problems go away.

Updated · By the VOS3000 Web team

Quick answer: VOS3000 carries fax as T.38 when both sides support it: tick Allow t38 on the mapping gateway and the routing gateway. If a carrier has no T.38, fax can pass as G.711 audio, but only with G.711 end to end, no silence suppression and a clean network.

Best
T.38 on both gateways
Fallback
G.711 pass-through
Avoid
G.729 and annexb=yes for fax
Setting
Allow t38

Two ways to carry fax

  • T.38: the fax is sent as data, built to survive packet loss. The call starts as voice, then the fax machines' gateways switch to T.38 with a re-INVITE. Both the customer and the carrier must support it.
  • G.711 pass-through: the fax tones travel as uncompressed G.711 audio. It works when T.38 is not available, but only on a clean network.

Turn on T.38

Tick Allow t38 in both places:

  • The customer's mapping gateway, Additional settings, Protocol.
  • The carrier's routing gateway, Additional settings, Protocol, SIP: Allow t38 lets VOS3000 send T.38 to that carrier.

If only one side supports T.38, leave it off for that route and use G.711, or the switch to T.38 fails and so does the fax. Route fax traffic to carriers that support T.38; a separate prefix for fax customers makes that easy.

G.711 pass-through settings

  • Use G.711 (PCMA or PCMU) end to end, with no G.729 or G.723 anywhere on the path, and no transcoding.
  • Turn off silence suppression: on the routing gateway, set G729 annexb to no or None, and ask the customer and carrier to disable VAD.
  • Keep the path short and clean: packet loss above about 1% or high jitter breaks fax.

See codecs and DTMF for how to set codecs per gateway.

Media proxy

Fax machines and ATAs are often behind NAT. If the fax call connects but no pages go through, try Media proxy On for that customer, and make sure your firewall allows the RTP port range; see media proxy.

Check a failed fax

Capture the call (see debug trace and SIP capture) and look for the re-INVITE with m=image in the SDP: that is the switch to T.38. If the carrier rejects it, use G.711 for that route. If there is no re-INVITE, the fax ran as G.711 and the network quality is the place to look.

Questions about this topic

Does VOS3000 support T.38 fax?

Yes. Tick Allow t38 on the mapping gateway and on the routing gateway, and VOS3000 passes the T.38 negotiation between them.

Can I send fax over G.729?

No. G.729 compresses the signal too much for fax. Use T.38, or G.711 end to end.

Why do faxes fail halfway?

Usually packet loss or jitter, silence suppression, or one side switching to T.38 while the other does not support it.

Try every step in the live demo

Each screen in this guide is in the VOS3000 Web demo, with made-up data. Sign in with demo / demo.