HylaFAX The world's most advanced open source fax server

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [hylafax-users] V.21 signal reception timeout +FCERROR



Some kind of VoIP, not a really complete VoIP network, but a provider converting telephone (analog) communications to digital signals inside a cisco router.

The strange thing is that we have problems almost exclusively by fax of a given zone (prefix 050….). From many other fax we receive with a percentage of error very low.

 

Some clarifications to be more possible self-employed in the log analysis:

 

1)    Nov 29 09:37:54.85: [ 3155]: --> [10:NO CARRIER]

-          You say 10 seconds. In the log, the numbers before colon are seconds ?

-          Arrow --> means modem (DCE) to hylafax (DTE) communications ? and <-- means hylafax (DTE) to modem (DCE) communication ?

 

2)    Can a VoIP T.38 line allow reception well at some time and wrong at other time ? congestion or something like that ?

 

3)    Can a VoIP T.38 line allow reception well all times from specific remote fax and produce wrong reception for some other remote fax machine ? this is our situation. Perhaps best remote fax machine can resolve this issue ?

 

4)    Can we set hylafax to invalidate all fax communication if REJECT by Page Quality arises ? so remote fax return an error to operator and operator know to resend fax ?

 

5)    What’s this “MODEM <Empty line>”

Nov 29 14:30:06.14: [ 3153]: ANSWER: FAX CONNECTION  DEVICE '/dev/apsfax429'

Nov 29 14:30:06.14: [ 3153]: RECV FAX: begin

Nov 29 14:30:06.14: [ 3153]: <-- data [32]

Nov 29 14:30:06.14: [ 3153]: <-- data [2]

Nov 29 14:30:06.17: [ 3153]: --> [7:CONNECT]

Nov 29 14:30:06.17: [ 3153]: <-- data [23]

Nov 29 14:30:06.17: [ 3153]: <-- data [2]

Nov 29 14:30:06.19: [ 3153]: --> [7:CONNECT]

Nov 29 14:30:06.19: [ 3153]: <-- data [13]

Nov 29 14:30:06.19: [ 3153]: <-- data [2]

Nov 29 14:30:08.40: [ 3153]: --> [2:OK]

Nov 29 14:30:08.40: [ 3153]: <-- [9:AT+FRH=3\r]

Nov 29 14:30:15.40: [ 3153]: --> [0:]

Nov 29 14:30:15.40: [ 3153]: MODEM <Empty line>

Nov 29 14:30:15.40: [ 3153]: <-- data [1]

Nov 29 14:30:15.41: [ 3153]: --> [2:

 

6)    What’s this strange character instead of “2:<modem response command like OK or CONNECT or other>” ? I hope will be readable, if not it’s seams a Unicode 2 byte character.

Nov 29 14:30:31.91: [ 3153]: <-- data [2]

Nov 29 14:30:32.24: [ 3153]: --> [2:OK]

Nov 29 14:30:32.24: [ 3153]: <-- [10:AT+FRM=96\r]

Nov 29 14:30:42.14: [ 3153]: <-- data [1]

Nov 29 14:30:42.15: [ 3153]: --> [2:


]

Nov 29 14:30:42.15: [ 3153]: --> [2:OK]

Nov 29 14:30:42.15: [ 3153]: <-- [9:AT+FRH=3\r]

 

7)    What’s this error ? local modem - hylafax communication error ?

Nov 29 09:47:14.65: [ 2967]: <-- [9:AT+FRH=3\r]

Nov 29 09:47:15.96: [ 2967]: --> [7:CONNECT]

Nov 29 09:47:17.52: [ 2967]: --> [5:ERROR]

Nov 29 09:47:17.52: [ 2967]: MODEM Command error

Nov 29 09:47:17.52: [ 2967]: FCS error

Nov 29 09:47:17.52: [ 2967]: <-- [10:AT+FRS=21\r]

 




Project hosted by iFAX Solutions