Peter Fraser [p...@thinkage.ca] wrote: > I believe I am trying to interface into a T38 gateway which is supported by > my SIP supplier. > I expect but don't know, that if I don't uses T38 my Sip supplier will send > the call on a SIP > call to any other client which will not recognize it as FAX. > > > -----Original Message----- > From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of > Mikkel C. Simonsen > Sent: Monday, April 22, 2013 1:47 PM > To: OpenBSD misc > Subject: Re: faxing > > Peter Fraser wrote: > > I would like to know if anyone has done something similar or any good > > suggestions on what I should do to get faxing to work > > Connect the existing fax to a Linksys PAP2 (or whatever the current model is > called), use the g711 codec, setup the PAP2 correctly, and faxing will work > great. No need for a separate phone line anymore. >
Newer ATAs like the Linksys SPA2102 (now discontinued), Cisco SPA122 (replacement), Obihai OBi302, all support T.38. The SPA122 is simply not reliable with anything less than the newest 1.3.1(003) firmware. The Obihai is a great box but I'd recommend it mainly for a service provider or someone who is already familiar with VoIP. If you are an SP, they have a great "Zero touch" provisioning option where they can hit your provisioning server (HTTP or HTTPS) out-of-the-box and you buy direct from them. Stuart Henderson [s...@spacehopper.org] wrote: > > This depends on latency and jitter to your SIP provider. > FAX is very sensitive to this. That's what T.38 is supposed to help with. Translates all the fax modem tones to HDLC frames which then get transported over the IP network. If you have a full duplex Internet link with low load, you can do G.711 based faxing and have a decent success rate. Otherwise, T.38 can handle the more typical situation.
