Re: [hylafax-users] Problem with sending faxes

["John Warren" <jwarren@xxxxxxx>]

Sorry, on the way home last night I remembered
I didn't add it as well. 

Here is the com log with the phone number
edited since it's our private testing number. As you can see it's responding
busy even though the call was answered, the fax hand shaking completed
and I hear the fax carrier starting up. At this point the mainpine card
drops the call and hylafax reports "Busy signal detected". 

This happens on at least three channels
on the card so I don't think it's a hardware problem. Also we receiving
faxes without any problems.

I'm going to call Mainpine but I wanted
to pass it by the group incase I did something wrong in my config file.

Session log:
Dec 16 18:34:02.42: [18108]: SESSION
BEGIN 000831057 1310642xxxx
Dec 16 18:34:02.42: [18108]: HylaFAX
(tm) Version 4.4.2
Dec 16 18:34:02.42: [18108]: SEND FAX:
JOB 330090 DEST 1310642xxxx COMMID 000831057 DEVICE '/dev/ttyS11' FROM
'John Warren <jwarren@xxxxxxx>' USER root
Dec 16 18:34:02.42: [18108]: <--
[14:AT+FCLASS=1.0\r]
Dec 16 18:34:02.42: [18108]: -->
[2:OK]
Dec 16 18:34:02.42: [18108]: DIAL 1310642xxxx
Dec 16 18:34:02.42: [18108]: <--
[20:ATDT*82,1310642xxxx\r]
Dec 16 18:34:23.52: [18108]: -->
[4:BUSY]
Dec 16 18:34:23.52: [18108]: SEND FAILED:
JOB 330090 DEST 1310642xxxx ERR [1] Busy signal detected
Dec 16 18:34:24.52: [18108]: <--
[5:ATH0\r]
Dec 16 18:34:24.57: [18108]: -->
[2:OK]
Dec 16 18:34:24.57: [18108]: SESSION
END

            Pharmacy Services
            John Warren
            Network Operations Administrator
            100 Corporate Pointe, Suite 395
            Culver City, CA 90230

            direct: 1.310.237.7721
            p: 1.310-642.1700 x7721 | f:
1.310.642.1701 | c: 1.714.504.9101
            e: jwarren@xxxxxxx
            w: www.hms.com

Please
consider the environment before printing this email.

From:	John Hudak <jjhudak@xxxxxxxxx>
To:	John Warren <jwarren@xxxxxxx>
Cc:	hylafax-users@xxxxxxxxxxx
Date:	12/16/2010 07:00 PM
Subject:	Re: [hylafax-users] Problem with sending faxes
Sent by:	hylafax-users-bounce@xxxxxxxxxxx

---

To see what is actually happening from the time the sending
is initiate to the time it fails, please post the log file (/var/spool/hylafax/log). 
The files will have the form c000000xxx where xxx is a numeric value.

John


On Thu, Dec 16, 2010 at 8:53 PM, John Warren <jwarren@xxxxxxx>
wrote:
I'm having a problem sending in that
when the fax machine answers my mainpine card starts the connection sequence
when it hears the fax machines answer tone then drops the call and reports
that it was a busy connection. I'm assuming since this happens on several
of the channels it's likely a total board failure or something in the config
file is not set correctly. 

Anyone have any ideas? I running HylaFAX version 4.4.2 built Wed Oct  3
20:36:27 EDT 2007 for i686-pc-linux-gnu. 

Here is my config.ttyS file. 

# $Id: lucent-mt-10,v 1.9 2007/05/11 15:17:11 aidan Exp $

# 
# prototype config for MultiTech 5634-series modems using
# the Lucent/Agere chipset supporting V.34-Fax. 
# 

# 
CountryCode:                1
AreaCode:                310
FAXNumber:                +1.310.642.1701-12
LongDistancePrefix:        1 
InternationalPrefix:        011
DialStringRules:        etc/dialrules
ServerTracing:                1
SessionTracing:                11
RecvFileMode:                0600
LogFileMode:                0600
DeviceMode:                0600
RingsBeforeAnswer:        2 
SpeakerVolume:                on
GettyArgs:                "-h
%l dx_%s" 
LocalIdentifier:        "HMS, Inc. - Pharmacy
Services" 
TagLineFont:                etc/lutRS18.pcf
TagLineFormat:                "From
%%l|%c|Page %%P of %%T" 
MaxRecvPages:                100
ModemDialCmd: ATDT%s 
# 

ModemType:                Class1.0
       # use this to supply a hint
ModemRate:                57600
               # must be at least
as fast as the DCE-DCE communication 
ModemFlowControl:        rtscts      
         # many firmwares have broken software
flow control 
Class1EnableV34Cmd:        AT+F34=14,1,2    
   # 33600-2400 primary, 2400-1200 control
Class1TMConnectDelay:        400      
         # counteract quick CONNECT response
Class1HasRHConnectBug:        yes      
         # cope with +FRH=3 CONNECT errors
# 
# Setups for the MainPine. 
# 
ModemRingResponse:     AT+FCLASS=8;H1 
ModemRingsBeforeResponse: 2             #
Allow for CallerID to pass 
CallIDPattern:         "NMBR="    
     # Get the number if sent 
CallIDPattern:         "NAME="    
     # Get the name if sent 
CallIDPattern:         SHIELDED_DTMF    #
Get the DTMF DID digits if sent 
CallIDAnswerLength:    4            
   # We're only using the last 4 digits 
ModemAnswerCmd:        <delay:100>AT+FCLASS=1;A




           Pharmacy Services
           John Warren
           Network Operations Administrator
           100 Corporate Pointe, Suite 395
           Culver City, CA 90230

           direct: 1.310.237.7721
           p: 1.310-642.1700 x7721 | f: 1.310.642.1701
| c: 1.714.504.9101
           e: jwarren@xxxxxxx
           w: www.hms.com

          Please consider
the environment before printing this email.
----------------------------------------------------------------------------------------

Please note that the information contained in this message is intended
only for the use 
of the person or office to whom it is addressed, and may contain privileged
and
confidential information protected from disclosure under the law, including
the 
Health Insurance Portability and Accountability Act (HIPAA).  All
recipients are hereby 
notified that any inadvertent or unauthorized receipt does not waive such
privilege, and
that unauthorized dissemination, distribution or copying of this communication
is 
strictly prohibited and may subject you to criminal or civil penalties.
 If you have 
received this communication in error, please notify the sender by replying
to the message
and delete the material from any computer.  HMS Holdings Corp., together
with
its subsidiaries and affiliates hereby claim all applicable privileges
related to this 
information.  Any views expressed in this message are those of the
individual sender,
except where the sender specifies, and with authority, states them to be
the views of the company.

----------------------------------------------------------------------------------------



----------------------------------------------------------------------------------------

Please note that the information contained in this message is intended only for the use 
of the person or office to whom it is addressed, and may contain privileged and
confidential information protected from disclosure under the law, including the 
Health Insurance Portability and Accountability Act (HIPAA).  All recipients are hereby 
notified that any inadvertent or unauthorized receipt does not waive such privilege, and
that unauthorized dissemination, distribution or copying of this communication is 
strictly prohibited and may subject you to criminal or civil penalties.  If you have 
received this communication in error, please notify the sender by replying to the message
and delete the material from any computer.  HMS Holdings Corp., together with
its subsidiaries and affiliates hereby claim all applicable privileges related to this 
information.  Any views expressed in this message are those of the individual sender,
except where the sender specifies, and with authority, states them to be 
the views of the company.

----------------------------------------------------------------------------------------