Hi. I just configured a box with Hylafax and t38modem and works great. I just have a problem when the other end drops the call, the whole daemon will remain stuck and won't answer further calls. For example when I make a test call from my mobile and I drop it few seconds after, the hylafax status remains on "Receiving facsimile".
Running t38 in debug will end up in this line repeated forever:
2014/10/15 11:01:20.525 Housekeepe...c80ffbe700 ModemEngineBody::OnTimerCallback stSendAckWait Timeout 1
$ t38modem --version
T38Modem Version 2.0.0
(OPAL-3.10.10/3.10.10 (svn:29150), PTLIB-2.10.10/2.10.10 (svn:29149)) by Vyacheslav Frolov on Unix Linux (3.2.0-29-generic-x86_64)
2014/10/15 11:03:14.348 T38Modem Version 2.0.0 by Vyacheslav Frolov on Unix Linux (3.2.0-29-generic-x86_64) with PTLib (v2.10.10 (svn:29149)) at 2014/10/15 11:03:14.348
Last edit: Maxxer 2014-10-15
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Maxxer,
Did you find the answer to this problem? I'm seeing the same thing with:
T38Modem Version 2.0.0
(OPAL-3.10.10/3.10.10 (svn:29150), PTLIB-2.10.10/2.10.10 (svn:29149)) by Vyacheslav Frolov on Unix Linux (3.13.0-52-generic-x86_64)
2015/05/19 17:08:47.535 T38Modem Version 2.0.0 by Vyacheslav Frolov on Unix Linux (3.13.0-52-generic-x86_64) with PTLib (v2.10.10 (svn:29149)) at 2015/5/19 17:08:47.535
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes and no... t38modem is VERY unstable, you have to find a good mix between opal/ptlib/t38modem. The best is to use Peter's version https://github.com/hehol/t38modem
Also, which should be the solution to all the stuff, use a single t38modem process per modem
Good luck!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Using a singe modem per process did not help. I'm using this with Hylafax and Hylafax does not detect a modem that is off hook and 'Receiving facsimile' as being wedged.
So, I just wrote a script that checks for modems that are in the state "Receiving facsimile" for over 3 minutes. If they are in that state, I reset the modem. So I have a work around, but not a fix.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I did the same, sadly other than not having a solution you get dropped calls and thus incomplete faxes: when the modem remains wedged it means it has segfaulted. that is why I said it's unstable. Peter told me that he got it working by compiling the right libraries, but I never had the same result :(
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi. I just configured a box with Hylafax and t38modem and works great. I just have a problem when the other end drops the call, the whole daemon will remain stuck and won't answer further calls. For example when I make a test call from my mobile and I drop it few seconds after, the hylafax status remains on "Receiving facsimile".
Running t38 in debug will end up in this line repeated forever:
2014/10/15 11:01:20.525 Housekeepe...c80ffbe700 ModemEngineBody::OnTimerCallback stSendAckWait Timeout 1
Here's the full log of the dropped call:
https://dl.dropboxusercontent.com/u/706934/t38modem.log.gz
What problem could it be? thanks
$ t38modem --version
T38Modem Version 2.0.0
(OPAL-3.10.10/3.10.10 (svn:29150), PTLIB-2.10.10/2.10.10 (svn:29149)) by Vyacheslav Frolov on Unix Linux (3.2.0-29-generic-x86_64)
2014/10/15 11:03:14.348 T38Modem Version 2.0.0 by Vyacheslav Frolov on Unix Linux (3.2.0-29-generic-x86_64) with PTLib (v2.10.10 (svn:29149)) at 2014/10/15 11:03:14.348
Last edit: Maxxer 2014-10-15
Maxxer,
Did you find the answer to this problem? I'm seeing the same thing with:
T38Modem Version 2.0.0
(OPAL-3.10.10/3.10.10 (svn:29150), PTLIB-2.10.10/2.10.10 (svn:29149)) by Vyacheslav Frolov on Unix Linux (3.13.0-52-generic-x86_64)
2015/05/19 17:08:47.535 T38Modem Version 2.0.0 by Vyacheslav Frolov on Unix Linux (3.13.0-52-generic-x86_64) with PTLib (v2.10.10 (svn:29149)) at 2015/5/19 17:08:47.535
Yes and no... t38modem is VERY unstable, you have to find a good mix between opal/ptlib/t38modem. The best is to use Peter's version https://github.com/hehol/t38modem
Also, which should be the solution to all the stuff, use a single t38modem process per modem
Good luck!
Using a singe modem per process did not help. I'm using this with Hylafax and Hylafax does not detect a modem that is off hook and 'Receiving facsimile' as being wedged.
So, I just wrote a script that checks for modems that are in the state "Receiving facsimile" for over 3 minutes. If they are in that state, I reset the modem. So I have a work around, but not a fix.
I did the same, sadly other than not having a solution you get dropped calls and thus incomplete faxes: when the modem remains wedged it means it has segfaulted. that is why I said it's unstable. Peter told me that he got it working by compiling the right libraries, but I never had the same result :(
Well it is not segfaulting and I'm not actually restarting t38modem. I'm just restarting faxgetty and that resets the modem....
I see the same thing in the trace logs that you were seeing:
Housekeepe...c80ffbe700 ModemEngineBody::OnTimerCallback stSendAckWait Timeout 1
You will get more support on the opal mailing list, I suggest you to ask the same question there.