hylafax + 调制解调器 (USR Sportster Flash X2) + 调制解调器超时:从调制解调器读取线路

hylafax + 调制解调器 (USR Sportster Flash X2) + 调制解调器超时:从调制解调器读取线路

我的 Sportster Flash X2 调制解调器出现了以下问题。我们已使用 hylafax 对其进行了设置,并且可以使用一两周。但今天在接收传真时,它挂起了,没有响应。这是调制解调器上次运行时的日志

<-- [5:ATM0\r]
Oct 14 10:58:36 minos FaxGetty[62820]: --> [2:OK]
Oct 14 11:00:03 minos FaxGetty[62820]: --> [4:RING]
Oct 14 11:00:03 minos FaxGetty[62820]: DynamicConfig: bin/dynconf.php "/dev/ttyS0"
Oct 14 11:00:07 minos FaxGetty[62820]: ANSWER: FAX CONNECTION  DEVICE '/dev/ttyS0'
Oct 14 11:02:01 minos /USR/SBIN/CRON[638]: (logcheck) CMD (   if [ -x /usr/sbin/logcheck ]; then nice -n10 /usr/sbin/logcheck; fi)
Oct 14 11:06:06 minos FaxGetty[62820]: RECV FAX (000000019): from +XX XXX XXXXXX, page 1 in 0:05:59, A4, 3.85 line/mm, 2-D MMR, 14400 bit/s
Oct 14 11:06:06 minos FaxGetty[62820]: RECV FAX (000000019): recvq/fax000000010.tif from +43 316 720883, route to <unspecified>, 1 pages in 0:05:59
Oct 14 11:06:13 minos FaxGetty[62820]: RECV FAX (000000019): session with +XX XXX XXXXXX terminated abnormally: Timeout waiting for Phase C carrier drop
Oct 14 11:06:13 minos FaxGetty[62820]: RECV FAX: bin/faxrcvd.php "recvq/fax000000010.tif" "ttyS0" "000000019" "Timeout waiting for Phase C carrier drop"
Oct 14 11:06:13 minos FaxGetty[62820]: <-- [5:ATH0\r]
Oct 14 11:06:18 minos FaxGetty[62820]: MODEM TIMEOUT: reading line from modem <-- From here modem is not working

首先,我们尝试重启调制解调器,因为它通常会产生神奇的效果,但现在却没有帮助。所以我们还重启了 hylafax 甚至整个服务器。hylafax 再次启动后,它就挂在这里了

Oct 14 11:10:44 minos FaxGetty[62820]: CLOSE /dev/ttyS0
Oct 14 11:10:44 minos FaxQueuer[62798]: MODEM /dev/ttyS0 appears to be wedged
Oct 14 11:10:44 minos FaxQueuer[62798]: MODEM WEDGED: bin/wedged "ttyS0" "/dev/ttyS0"
Oct 14 12:24:59 minos HylaFAX[3772]: HylaFAX INET Protocol Server: restarted.
Oct 14 12:24:59 minos FaxGetty[3790]: OPEN /dev/ttyS0  HylaFAX (tm) Version 6.0.6
Oct 14 12:25:00 minos FaxGetty[3790]: MODEM set DTR OFF
Oct 14 12:25:01 minos FaxGetty[3790]: MODEM set DTR ON
Oct 14 12:25:04 minos FaxGetty[3790]: MODEM set baud rate: 19200 baud, input flow XON/XOFF, output flow XON/XOFF
Oct 14 12:25:04 minos FaxGetty[3790]: MODEM flush i/o
Oct 14 12:25:04 minos FaxGetty[3790]: <-- [4:ATZ\r]
Oct 14 12:25:34 minos FaxGetty[3790]: MODEM TIMEOUT: reading line from modem

这是调制解调器的配置:

ModemType:              Class1          # use class 1 interface
ModemRate:              19200           # rate for DCE-DTE communication
ModemFlowControl:       xonxoff         # software flow control
#
ModemSetupDTRCmd:       ATS13=1&D2      # setup so DTR drop resets modem
ModemSetupDCDCmd:       AT&C1           # setup so DCD reflects carrier (or not)
ModemNoFlowCmd:         AT&H0&I0&R1     # setup modem for no flow control
ModemHardFlowCmd:       AT&H1&I0&R2     # setup modem for hardware flow control
ModemSoftFlowCmd:       AT&H2&I2&R1     # setup modem for software flow control
ModemResultCodesCmd:    ATQ0X4          # enable result codes
#
ModemMfrQueryCmd:       !USR
ModemModelQueryCmd:     ATI3
ModemRevQueryCmd:       ATI7            # XXX returns a multi-line result
#
# When AT+FCLASS=1 is issued the modem automatically switches
# to software flow control; these parameters let the fax software
# reset flow control as needed after entering Class 1.
#
Class1NFLOCmd:          AT&H0&I0&R1     # setup modem for no flow control
Class1HFLOCmd:          AT&H1&I0&R2     # setup modem for hardware flow control
Class1SFLOCmd:          ""              # modem does this automatically

#
# This should resolve "DIS/DTC received 3 times" errors:
#
Class1ResponseWaitCmd:  AT+FRS=1        # wait after sending TCF for response
#
# The remainder of this configuration is included so that the
# modem "idles" in Class 0 while not sending or receiving facsimile.
#
ModemSetupAACmd:        AT+FCLASS=0     # leave modem idling in class 0
ModemAnswerCmd:         AT+FCLASS=1A    # answer in Class 1
#
# When using AT+FRS=n we see USR modems reset themselves in the middle of sessions
# this is not good.  So, we seem to work-around that problem by not using the
# command.  Unfortunately, this isn't an ideal thing.
#
Class1SwitchingCmd:     "<delay\0727>"

#
## AvantFAX
#
FaxRcvdCmd:     bin/faxrcvd.php
DynamicConfig:  bin/dynconf.php
UseJobTSI:      true

我们还尝试用 ZyXEL U1496(在出现此问题之前也可以正常工作)替换 Sportster,但这个也没有响应。使用 cu 或 minicom 连接到调制解调器后,它似乎已连接,但在执行 AT+FCLASS?命令后没有响应。可能是 hylafax 出了问题,还是我遗漏了什么。我浏览了很多论坛,重新启动调制解调器后一切都应该正常工作,但在我们的例子中并非如此。

更新

好的,现在我们 100% 确定调制解调器没有问题。我们尝试将调制解调器插入 win XP 机器和不同的 linux 机器。两台调制解调器都正常工作,我可以使用基本 AT 命令查询它。问题似乎出在第一台服务器上的串行上,但日志中没有任何内容可以表明存在问题。服务器是新的 HP 360e Gen8 ProLiant,所以我希望端口没有死。我可以使用 cu -l /dev/ttyS0 连接到调制解调器,但没有 AT 命令不起作用。我也尝试过 /etc/init.d/setserial restart,但没有帮助。系统是 Debian Wheezy 7.6 内核 3.2.0-4-amd64

非常感谢您的帮助。

答案1

好的,我们终于弄清楚了问题所在。我们正在使用的 HP Proliant DL360e Gen8 将 ilo4 连接到串行端口,通过此连接,它允许远程连接到控制台。在 ilo4 bios 中禁用 ilo4 虚拟串行端口后(设置 -> 串行 CLI 状态 -> 禁用),一切都开始正常工作。

感谢您的时间

相关内容