Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
HELP! My hylafax won't send
Dear all,
I sent this message last week and received quite a number of responses.
Thank you all for your help! Unfortunately, after trying everyone has
suggested, I still can't solve the problem. My problem is I used to have
hylafax 4.0pl1 running on Solaris 2.6 with US Robotics 56K fax modem
connected to a terminal server. Everything worked fine until we moved the
whole thing to one of our client's office where they have the phone system
under PABX, even though there is a number dedicated to faxing. I tried
sending faxes by connecting the modem to a normal phone line and things
worked great.
So, in order to troubleshoot the problem, I disabled hylafax and make the
call right at the modem by "tip" into it and issue ATDT9,9054445555. I
tried it on long distance but later found out that they have a two digit
access code tied to the line. When making local calls, the 2 digit code is
not needed. So, I tried issuing the above command in an attempt to make a
local call. My colleague at the remote site said that he can hear it
getting the dial tone after dialing 9, and then the number and some humming
noises. It looks like that it's talking to the remote machine but some
how, it keeps returning that "Busy signal is detected". The log is as
follows:
Nov 23 16:14:43.20: [ 6512]: SESSION BEGIN 00000221 14169
Nov 23 16:14:43.20: [ 6512]: SEND FAX: JOB 20 DEST 9 COMMID 00000221
Nov 23 16:14:43.20: [ 6512]: DELAY 2600 ms
Nov 23 16:14:48.02: [ 6512]: <-- [17:ATE0V1Q0X4S0=0H0\r]
Nov 23 16:14:48.19: [ 6512]: --> [16:ATE0V1Q0X4S0=0H0]
Nov 23 16:14:48.19: [ 6512]: --> [2:OK]
Nov 23 16:14:48.19: [ 6512]: <-- [32:ATS8=2S7=60&H1&I0&R2S13=1&D2&C1\r]
Nov 23 16:14:48.37: [ 6512]: --> [2:OK]
Nov 23 16:14:48.37: [ 6512]: <-- [14:AT+FCLASS=2.0\r]
Nov 23 16:14:48.55: [ 6512]: --> [2:OK]
Nov 23 16:14:48.55: [ 6512]: <-- [9:AT+FLO=2\r]
Nov 23 16:14:48.73: [ 6512]: --> [2:OK]
Nov 23 16:14:48.73: [ 6512]: <-- [9:AT+FPP=0\r]
Nov 23 16:14:48.91: [ 6512]: --> [2:OK]
Nov 23 16:14:48.91: [ 6512]: <-- [9:AT+FBO=0\r]
Nov 23 16:14:49.09: [ 6512]: --> [2:OK]
Nov 23 16:14:49.09: [ 6512]: <-- [10:AT+FCT=30\r]
Nov 23 16:14:49.27: [ 6512]: --> [2:OK]
Nov 23 16:14:49.27: [ 6512]: <-- [15:AT+FNR=1,1,1,0\r]
Nov 23 16:14:49.47: [ 6512]: --> [2:OK]
Nov 23 16:14:49.47: [ 6512]: <-- [9:AT+FIE=0\r]
Nov 23 16:14:49.67: [ 6512]: --> [2:OK]
Nov 23 16:14:49.67: [ 6512]: <-- [23:AT+FCC=1,5,2,2,0,0,0,0\r]
Nov 23 16:14:49.89: [ 6512]: --> [2:OK]
Nov 23 16:14:49.89: [ 6512]: <-- [5:ATM0\r]
Nov 23 16:14:50.07: [ 6512]: --> [2:OK]
Nov 23 16:14:50.09: [ 6512]: <-- [14:AT+FCLASS=2.0\r]
Nov 23 16:14:50.35: [ 6512]: --> [2:OK]
Nov 23 16:14:50.35: [ 6512]: <-- [9:AT+FLO=2\r]
Nov 23 16:14:50.63: [ 6512]: --> [2:OK]
Nov 23 16:14:50.63: [ 6512]: <-- [9:AT+FPP=0\r]
Nov 23 16:14:50.91: [ 6512]: --> [2:OK]
Nov 23 16:14:50.91: [ 6512]: <-- [9:AT+FBO=0\r]
Nov 23 16:14:51.17: [ 6512]: --> [2:OK]
Nov 23 16:14:51.17: [ 6512]: <-- [10:AT+FCT=30\r]
Nov 23 16:14:51.47: [ 6512]: --> [2:OK]
Nov 23 16:14:51.47: [ 6512]: <-- [15:AT+FNR=1,1,1,0\r]
Nov 23 16:14:51.75: [ 6512]: --> [2:OK]
Nov 23 16:14:51.75: [ 6512]: <-- [9:AT+FIE=0\r]
Nov 23 16:14:52.03: [ 6512]: --> [2:OK]
Nov 23 16:14:52.03: [ 6512]: <-- [23:AT+FCC=1,5,2,2,0,0,0,0\r]
Nov 23 16:14:52.33: [ 6512]: --> [2:OK]
Nov 23 16:14:52.33: [ 6512]: <-- [30:AT+FLI="ABC "\r]
Nov 23 16:14:52.63: [ 6512]: --> [2:OK]
Nov 23 16:14:52.63: [ 6512]: DIAL 9
Nov 23 16:14:52.63: [ 6512]: <-- [6:ATDT9\r]
Nov 23 16:15:12.05: [ 6512]: --> [4:BUSY]
Nov 23 16:15:12.05: [ 6512]: SEND FAILED: Busy signal detected
Nov 23 16:15:12.05: [ 6512]: <-- [5:ATH0\r]
Nov 23 16:15:12.31: [ 6512]: --> [2:OK]
Nov 23 16:15:12.36: [ 6512]: SESSION END
I checked with the phone company and they confirmed that the lines are
analog.
I think the problem now is nailed down to the modem. Anyone has any
suggestion? I'm totally stressed out to get this going. I'd greatly
appreciate if someone can offer me suggestion.
Thanks a lot for your kind attention!
Sandie