I have tried the number alone. It rings, gets modem "handshake" but never connects. It first says "connection in progress" After 60 sec I get "transmission failure"
I tried the "99" in front, the number won't even go through.
Anybody have experience with this ? It should operate similarly to a fax.
it's *99 pause
If you are dialing manually, dial *99 and wait for the dial tone to return before dialing the rest of the numbers.
If the number is stored in the unit, you need to store a pause after the *99. How you do that shoulld be in the manual for the unit. With a standard telephone modem it's done with the comma.
Telo with 2 Handsets, a Linx, and a Safety Phone
Telo2 with 2 Handsets and a Linx
VoIP hardware: 2 Telo w/3 handsets & Linx / ooma core
Total Lines: 8 / Numbers: 11 / Handsets: 20
Lifetime Premier Member
Friends don't remember what Landline Integration was or why we did it.
Yes but it does not rule out FOIP. This would require the provider to offer t.38 as a codec to transmit fax over as well as an ATA that can do fax bypass. I'm not too keen on faxing via g.711 (Ooma calls this fax mode) even though it does work sometimes. It only works at all because g.711 is not nearly as lossy of a voice codec as iLBC, g.729, g.726 etc. It is still far less than ideal for faxing data.wbensing wrote:well I tried it unfortunately it still will not work. I have since learned that the ecg transmissions have to be ANALOG (imagine how backward the FAA system is). I think that pretty much rules out a VOIP transmission.
I work at Boeing and we converted to VOIP exclusively three years ago and used it very widely prior to this. Cisco IP phones are used throughout. For FAX we have a t.38 capable ATA connected to the modem port of our multifunction printer/copier equipment. We are able to fax consistently at 14400 using this which is true FOIP rather than VOIP. One of my providers I use in my VOIP hobby offers t.38 but it's a BYOD service. One of my prior providers also offers t.38 FOIP but they provide you equipment that you can't tinker with but most people would want something you unbox, activate and use. The more adventurous prefer the BYOD method where you have complete control over the settings because it's YOUR equipment.
Actually, Ooma's end. To use FOIP, the network and device used to connect to the network must support the specified codec. Neither Ooma's network nor Ooma's devices have that codec.wbensing wrote:where can I find out more about FOIP. Is it something I have to set up at my end or does the FAA (receiver) have to have it at their end ?
Formerly employed at another VoIP company.
My opinions are my own.