Michael wrote: >> There is a dialplan variable called FAX_DISABLE_V17. If you don't set >> that, V.17 should work. >> > > I have not set it. > > >> Are you using T.38? A lot of people set their T.38 gateways to inhibit >> anything above 9600bps. >> > > Next question - why most of time when calling from a normal phone I get no > fax > tones at the other end? > > Does T38 rely on the calling machine to start the process? > > This is a dedicated incoming fax number - If possible I would like to force > it > in to fax mode every time, to give tones, because some calling machines are > started manually by people calling with the handset first, and it is more > comforting for them to hear a fax tone. > This depends on the path. If it is
FAX machine A -> gateway A-> gateway B -> FAX machine B something like the following will happen. FAX machine A calls, and the call reaches FAX machine B with an audio path. FAX machine B sends the answer tone, which gateway B hears. Gateway B mutes the audio path while it attempts T.38 negotiation. Gateway B and gateway A chat, and switch into T.38 mode. Gateway B might then send the "answer tone present" signal to gateway A, or it may not. They are pretty sloppy about this. Now things should be running in T.38 mode, but probably the only answer tone that arrived at FAX machine A was the first 20 or 30 ms. FAX machine A should hear bursts of V.21 every few seconds, so there should be no ambiguity about having reached FAX machine B. Steve _______________________________________________ Callweaver-users mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-users
