[hylafax-users] Hylafax + IaxModem: No response to PPS repeated 3 times

[Lorenzo Milesi]

Hi.
I have a setup with Hylafax 6.0.5 and Iaxmodem 1.2.0 which does faxing over VoIP. This setup has been working great for several months, but lately it started suffering communication problems: faxes longer than one page gets corrupted, communication is truncated, pages received only partially.

The common RX/TX result is:
Sep 18 09:02:32.16: [22651]: SEND FAILED: JOB 26266 DEST 0341222222 ERR [334] No response to PPS repeated 3 times.; too many attempts to send


Now I tried adding the options suggested here:
http://www.hylafax.org/archive/2008-09/msg00053.php
will report back if I get any improvement (tought the first send replied No receiver protocol (T.30 T1 timeout)).



I captured some comm logs:
https://dl.dropboxusercontent.com/u/706934/c000106495.gz
https://dl.dropboxusercontent.com/u/706934/c000107898.gz
https://dl.dropboxusercontent.com/u/706934/c000108390.gz

Excerpts:

Sep 11 15:54:13.46: [29522]: <-- [9:AT+FTS=7\r]
Sep 11 15:54:13.54: [29522]: --> [2:OK]
Sep 11 15:54:13.54: [29522]: <-- [9:AT+FTH=3\r]
Sep 11 15:54:13.54: [29522]: --> [7:CONNECT]
Sep 11 15:54:13.54: [29522]: <-- HDLC<7:FF C8 FD F2 00 80 88>
Sep 11 15:54:13.54: [29522]: <-- data [7]
Sep 11 15:54:13.54: [29522]: <-- data [2]
Sep 11 15:54:14.72: [29522]: --> [2:OK]
Sep 11 15:54:14.72: [29522]: SEND send PPS (partial page signal)
Sep 11 15:54:14.72: [29522]: SEND send MPS (more pages, same document)
Sep 11 15:54:14.72: [29522]: <-- [9:AT+FRH=3\r]
Sep 11 15:54:17.82: [29522]: --> [0:]
Sep 11 15:54:17.82: [29522]: MODEM <Empty line>
Sep 11 15:54:17.82: [29522]: MODEM TIMEOUT: waiting for v.21 carrier
Sep 11 15:54:17.82: [29522]: <-- data [1]
Sep 11 15:54:17.84: [29522]: --> [2:OK]
Sep 11 15:54:17.84: [29522]: <-- [9:AT+FTH=3\r]
Sep 11 15:54:17.86: [29522]: --> [7:CONNECT]
Sep 11 15:54:17.86: [29522]: <-- HDLC<7:FF C8 FD F2 00 80 88>
Sep 11 15:54:17.86: [29522]: <-- data [7]
Sep 11 15:54:17.86: [29522]: <-- data [2]
Sep 11 15:54:19.04: [29522]: --> [2:OK]
Sep 11 15:54:19.04: [29522]: SEND send PPS (partial page signal)
Sep 11 15:54:19.04: [29522]: SEND send MPS (more pages, same document)
Sep 11 15:54:19.04: [29522]: <-- [9:AT+FRH=3\r]
Sep 11 15:54:19.54: [29522]: --> [7:CONNECT]
Sep 11 15:54:19.82: [29522]: --> [4:FE 3B 10 03]
Sep 11 15:54:19.82: [29522]: --> [5:ERROR]
Sep 11 15:54:19.82: [29522]: MODEM Command error
Sep 11 15:54:19.82: [29522]: FCS error


Sep 16 16:33:05.47: [ 9463]: <-- [9:AT+FTS=7\r]
Sep 16 16:33:05.55: [ 9463]: --> [2:OK]
Sep 16 16:33:05.55: [ 9463]: <-- [9:AT+FTH=3\r]
Sep 16 16:33:05.55: [ 9463]: --> [7:CONNECT]
Sep 16 16:33:05.55: [ 9463]: <-- HDLC<7:FF C8 FD F2 00 00 49>
Sep 16 16:33:05.55: [ 9463]: <-- data [7]
Sep 16 16:33:05.55: [ 9463]: <-- data [2]
Sep 16 16:33:06.73: [ 9463]: --> [2:OK]
Sep 16 16:33:06.73: [ 9463]: SEND send PPS (partial page signal)
Sep 16 16:33:06.73: [ 9463]: SEND send MPS (more pages, same document)
Sep 16 16:33:06.73: [ 9463]: <-- [9:AT+FRH=3\r]
Sep 16 16:33:07.11: [ 9463]: --> [7:CONNECT]
Sep 16 16:33:09.09: [ 9463]: --> HDLC<38:FF C8 3D 00 00 07 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1F FD DF FF FF FF FF FF FF FF FF FF FF FF FE 78 BF>
Sep 16 16:33:09.09: [ 9463]: --> [5:ERROR]
Sep 16 16:33:09.09: [ 9463]: MODEM Command error
Sep 16 16:33:09.09: [ 9463]: FCS error
Sep 16 16:33:09.09: [ 9463]: <-- [9:AT+FTH=3\r]
Sep 16 16:33:09.11: [ 9463]: --> [7:CONNECT]
Sep 16 16:33:09.11: [ 9463]: <-- HDLC<7:FF C8 FD F2 00 00 49>
Sep 16 16:33:09.11: [ 9463]: <-- data [7]
Sep 16 16:33:09.11: [ 9463]: <-- data [2]
Sep 16 16:33:10.29: [ 9463]: --> [2:OK]
Sep 16 16:33:10.29: [ 9463]: SEND send PPS (partial page signal)
Sep 16 16:33:10.29: [ 9463]: SEND send MPS (more pages, same document)
Sep 16 16:33:10.29: [ 9463]: <-- [9:AT+FRH=3\r]
Sep 16 16:33:10.67: [ 9463]: --> [7:CONNECT]
Sep 16 16:33:11.09: [ 9463]: --> [4:3F 00 10 03]
Sep 16 16:33:11.09: [ 9463]: --> [5:ERROR]
Sep 16 16:33:11.09: [ 9463]: MODEM Command error
Sep 16 16:33:11.09: [ 9463]: FCS error
Sep 16 16:33:11.09: [ 9463]: <-- [9:AT+FTH=3\r]
Sep 16 16:33:11.11: [ 9463]: --> [7:CONNECT]
Sep 16 16:33:11.11: [ 9463]: <-- HDLC<7:FF C8 FD F2 00 00 49>
Sep 16 16:33:11.11: [ 9463]: <-- data [7]
Sep 16 16:33:11.11: [ 9463]: <-- data [2]
Sep 16 16:33:12.29: [ 9463]: --> [2:OK]
Sep 16 16:33:12.29: [ 9463]: SEND send PPS (partial page signal)
Sep 16 16:33:12.29: [ 9463]: SEND send MPS (more pages, same document)
Sep 16 16:33:12.29: [ 9463]: <-- [9:AT+FRH=3\r]
Sep 16 16:33:15.39: [ 9463]: --> [0:]
Sep 16 16:33:15.39: [ 9463]: MODEM <Empty line>
Sep 16 16:33:15.39: [ 9463]: MODEM TIMEOUT: waiting for v.21 carrier



Any help is welcome!
thanks

--
Lorenzo Milesi - lorenzo...@yetopen.it

YetOpen S.r.l. - http://www.yetopen.it/
Via Carlo Torri Tarelli 19 - 23900 Lecco - ITALY -
Tel 0341 220 205 - Fax 178 6070 222

GPG/PGP Key-Id: 0xE704E230 - http://keyserver.linux.it

-------- D.Lgs. 196/2003 --------

Si avverte che tutte le informazioni contenute in questo messaggio sono
riservate ed a uso esclusivo del destinatario. Nel caso in cui questo
messaggio Le fosse pervenuto per errore, La invitiamo ad eliminarlo
senza copiarlo, a non inoltrarlo a terzi e ad avvertirci non appena
possibile.
Grazie.


____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-us...@hylafax.org < /dev/null
*To learn about commercial HylaFAX(tm) support, mail sa...@ifax.com.*

[Lorenzo Milesi]

> Now I tried adding the options suggested here:
> http://www.hylafax.org/archive/2008-09/msg00053.php
> will report back if I get any improvement (tought the first send replied No
> receiver protocol (T.30 T1 timeout)).

I've just sent a fax from outside to Hylafax. Result:
set 30 10:31:30.30: [ 8422]: RECV FAX (000112007): session with CALLER_3 terminated abnormally: T.30 T2 timeout, expected signal not received
Full comm log here.
https://dl.dropboxusercontent.com/u/706934/c000112007.gz

Out of 5 pages I received 2 pages which are OK, the third page is completely blank, and of course the last two pages did never reach the destination.

I placed the config in /etc/hylafax/config, so it's applied to all modems. Should I specify it for all single configs?

[Tim Nelson]

----- Original Message -----
> > Now I tried adding the options suggested here:
> > http://www.hylafax.org/archive/2008-09/msg00053.php
> > will report back if I get any improvement (tought the first send
> > replied No
> > receiver protocol (T.30 T1 timeout)).
>
> I've just sent a fax from outside to Hylafax. Result:
> set 30 10:31:30.30: [ 8422]: RECV FAX (000112007): session with
> CALLER_3 terminated abnormally: T.30 T2 timeout, expected signal not
> received
> Full comm log here.
> https://dl.dropboxusercontent.com/u/706934/c000112007.gz
>
> Out of 5 pages I received 2 pages which are OK, the third page is
> completely blank, and of course the last two pages did never reach
> the destination.
>
> I placed the config in /etc/hylafax/config, so it's applied to all
> modems. Should I specify it for all single configs?
>

Are you faxing over VoIP (G.711u for example) or via T.38? If via non-T.38, it is no wonder you're getting sporadic issues. See here:

http://hylafax.sourceforge.net/docs/fax-over-voip.pdf

--Tim

[Lorenzo Milesi]

> Are you faxing over VoIP (G.711u for example) or via T.38? If via non-T.38,
> it is no wonder you're getting sporadic issues. See here:

Yeah I'm not using T38, but the issue is more systematic than sporadic, and it seems to happen only on "long" transmissions (> 2/3 pages), short faxes goes through (very slowly, but they do).
And what puzzles me is that it has been working great for a couple of years at least.

From what I can get in the logs there are a lot of transmission errors, but the audio seems clean. I posted some audio files to the iaxmodem ML (which I uploaded here [1]).

Any other suggestion is welcome.
thanks


[1] http://www.maxxer.it/hyladebug/

--
Lorenzo Milesi - lorenzo...@yetopen.it

YetOpen S.r.l. - http://www.yetopen.it/
Via Carlo Torri Tarelli 19 - 23900 Lecco - ITALY -
Tel 0341 220 205 - Fax 178 6070 222

GPG/PGP Key-Id: 0xE704E230 - http://keyserver.linux.it

-------- D.Lgs. 196/2003 --------

Si avverte che tutte le informazioni contenute in questo messaggio sono
riservate ed a uso esclusivo del destinatario. Nel caso in cui questo
messaggio Le fosse pervenuto per errore, La invitiamo ad eliminarlo
senza copiarlo, a non inoltrarlo a terzi e ad avvertirci non appena
possibile.
Grazie.

[Tim Nelson]

----- Original Message -----
> > Are you faxing over VoIP (G.711u for example) or via T.38? If via
> > non-T.38,
> > it is no wonder you're getting sporadic issues. See here:
>
> Yeah I'm not using T38, but the issue is more systematic than
> sporadic, and it seems to happen only on "long" transmissions (> 2/3
> pages), short faxes goes through (very slowly, but they do).
> And what puzzles me is that it has been working great for a couple of
> years at least.
>
> From what I can get in the logs there are a lot of transmission
> errors, but the audio seems clean. I posted some audio files to the
> iaxmodem ML (which I uploaded here [1]).
>
> Any other suggestion is welcome.

..so you are asking for suggestions on help with this issue, are given a resource to explain why your setup is not reliable (even though it once was magically), but you're choosing to ignore it and want more suggestions?

Fax over non-T.38 transport is not going to be successful in a predictable, reliable fashion due to the many problems noted in the link I sent previously (mainly jitter, compression, packet loss, and lack of strict timing). Until you resolve those problems, you'll continue to see poor performance, of which Hylafax and/or IAXmodem are not to blame.

--Tim

[Lorenzo Milesi]

> Fax over non-T.38 transport is not going to be successful in a predictable,
> reliable fashion due to the many problems noted in the link I sent
> previously (mainly jitter, compression, packet loss, and lack of strict
> timing). Until you resolve those problems, you'll continue to see poor
> performance, of which Hylafax and/or IAXmodem are not to blame.

I was just wondering why it has been working so good for so long and then suddendly stopped.
I'm talking already to the sip provider to see if they support T.38.

Thanks again

--
Lorenzo Milesi - lorenzo...@yetopen.it

YetOpen S.r.l. - http://www.yetopen.it/
Via Carlo Torri Tarelli 19 - 23900 Lecco - ITALY -
Tel 0341 220 205 - Fax 178 6070 222

GPG/PGP Key-Id: 0xE704E230 - http://keyserver.linux.it

-------- D.Lgs. 196/2003 --------

Si avverte che tutte le informazioni contenute in questo messaggio sono
riservate ed a uso esclusivo del destinatario. Nel caso in cui questo
messaggio Le fosse pervenuto per errore, La invitiamo ad eliminarlo
senza copiarlo, a non inoltrarlo a terzi e ad avvertirci non appena
possibile.
Grazie.

[Lorenzo Milesi]

> Fax over non-T.38 transport is not going to be successful in a predictable,
> reliable fashion due to the many problems noted in the link I sent
> previously (mainly jitter, compression, packet loss, and lack of strict
> timing). Until you resolve those problems, you'll continue to see poor
> performance, of which Hylafax and/or IAXmodem are not to blame.

Moving to T.38 seems to have fixed the issue, thank you very much!


I'm having a new issue, tough. When the call is being dropped on the other side the modem remains stuck forever, no way to unbock it unless restarting hylafax.
For example if I make a test phone call from my mobile, and drop the call just after few seconds, the modem will remain in "receiving facsimile".

This is my config:
CountryCode: 39
AreaCode: 2
LongDistancePrefix: 1
InternationalPrefix: 011
DialStringRules: etc/dialrules
ServerTracing: 1
SessionTracing: 11
RecvFileMode: 0600
LogFileMode: 0600
DeviceMode: 0600
SpeakerVolume: off
GettyArgs: "-h %l dx_%s"
LocalIdentifier: "T01"
TagLineFont: etc/lutRS18.pcf
TagLineFormat: "From %%l|%c|Page %%P of %%T"
MaxRecvPages: 200
ModemType: Class1 # use class 1 interface
ModemFlowControl: rtscts # default
ModemRevQueryCmd: AT+FREV?
ModemResetCmds: "AT#CID=10" # enable ANI/DNIS reporting
RingsBeforeAnswer: 2 # collect info between two RINGs
CallIDPattern: "NMBR = " # pattern string for calling number
CallIDPattern: "NMBR="
CallIDPattern: "NAME="
CallIDPattern: "ANID="
CallIDPattern: "NDID = " # pattern string for called number
ModemDialCmd: ATDF%s # user can override F by dial V
FaxRcvdCmd: bin/faxrcvd.php
DynamicConfig: bin/dynconf.php
UseJobTSI: true

The T38 debug output prints this forever:
2014/10/15 10:57:20.478 Housekeepe...c80ffbe700 ModemEngineBody::OnTimerCallback stSendAckWait Timeout 1

I captured a full debug of t38modem during the call, if anyone has experience with this software:
https://dl.dropboxusercontent.com/u/706934/t38modem.log.gz

--
Lorenzo Milesi - lorenzo...@yetopen.it

YetOpen S.r.l. - http://www.yetopen.it/
Via Carlo Torri Tarelli 19 - 23900 Lecco - ITALY -
Tel 0341 220 205 - Fax 178 6070 222

GPG/PGP Key-Id: 0xE704E230 - http://keyserver.linux.it

-------- D.Lgs. 196/2003 --------

Si avverte che tutte le informazioni contenute in questo messaggio sono
riservate ed a uso esclusivo del destinatario. Nel caso in cui questo
messaggio Le fosse pervenuto per errore, La invitiamo ad eliminarlo
senza copiarlo, a non inoltrarlo a terzi e ad avvertirci non appena
possibile.
Grazie.

[Tim Nelson]

----- Original Message -----
>
> The T38 debug output prints this forever:
> 2014/10/15 10:57:20.478 Housekeepe...c80ffbe700
> ModemEngineBody::OnTimerCallback stSendAckWait Timeout 1
>

You may want to check out the 'wedged'[1] hook for details on dealing with unresponsive modems. Otherwise, the t38modem/OPAL mailing lists are probably your next best bet.

--Tim

[1] http://hylafax.sourceforge.net/man/wedged.php