![]() |
Robert Moskowitz wrote:I hoped that was the way of it.
Faxgetty will 'learn'? what the remote fax supports, T38 or just T30, after connecting.
When using t38modem faxgetty will make no distinction between that device/connection and any other device or connection. faxgetty speaks T.31 to the modem, and uses T.30 to know what to speak. (I.e. the sentence structure is T.30, but the words are T.31.)
t38modem will perform T.38 entirely transparent to faxgetty.
I knew that.... Just not thinking through all the pieces. Well IAXmodem, it was nice knowing you! And Lee, thank you for all you are doing for us.
Or is this reason for IAXmodem to add T.38 support? :)
Since T.38 is not supported by IAX2 there really is no way to "add" T.38 support to iaxmodem without pretty much ripping out nearly all that is iaxmodem...
you'd end up with a scrap of stuff... a pseudo-device handler and a worthless loop... and after building in what would need to be there the end result would be "sipmodem" or "h323modem"... both of which already exist in t38modem.Now if we can be comfortable that the code will be maintained.
Thanks,
Lee.
____________________ HylaFAX(tm) Users Mailing List _______________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*