Re: FW: flexfax: Trace which modem a session is on?

[John Williams <williams@morinda.com>]

On Fri, 15 Jan 1999, William H. Gilmore wrote:
> > -----Original Message-----
> > From:	John Williams [SMTP:williams@morinda.com]
> > Sent:	Thursday, January 14, 1999 10:11 AM
> > To:	Hylafax
> > Subject:	flexfax: Trace which modem a session is on?
> > 
> > I hope this is a easy question for someone.
> > 
> > Can anyone tell me what to set the "SessionTracing:" parameter to
> > in order to have the modem's tty recorded in the log file?
> > 
> > ~~ John Williams
>
> Set the SessionTracing=11 in the config file for you modem.

Sorry, that does not work.

My SessionTracing is already set to 11, but there is nothing in the log
file to identify which modem was used.  

Here is one of our logfiles:

Jan 13 10:37:58.83: [20978]: SESSION BEGIN 00095930 #########
Jan 13 10:37:58.83: [20978]: SEND FAX: JOB 20377 DEST ######## COMMID 00095930
Jan 13 10:37:58.83: [20978]: DELAY 2600 ms
Jan 13 10:38:01.44: [20978]: <-- [15:ATE0V1Q0S0=0H0\r]
Jan 13 10:38:01.71: [20978]: --> [14:ATE0V1Q0S0=0H0]
Jan 13 10:38:01.71: [20978]: --> [2:OK]
Jan 13 10:38:01.71: [20978]: <-- [21:ATS8=2S7=60&E4&D3&C1\r]
Jan 13 10:38:01.91: [20978]: --> [2:OK]
Jan 13 10:38:01.91: [20978]: <-- [12:AT+FCLASS=2\r]
Jan 13 10:38:02.11: [20978]: --> [2:OK]
Jan 13 10:38:02.11: [20978]: <-- [10:AT+FTBC=0\r]
Jan 13 10:38:02.31: [20978]: --> [2:OK]
Jan 13 10:38:02.31: [20978]: <-- [10:AT+FBOR=0\r]
Jan 13 10:38:02.51: [20978]: --> [2:OK]
Jan 13 10:38:02.51: [20978]: <-- [13:AT+FPHCTO=30\r]
Jan 13 10:38:02.71: [20978]: --> [2:OK]
Jan 13 10:38:02.71: [20978]: <-- [24:AT+FDCC=1,5,2,2,2,0,0,0\r]
Jan 13 10:38:02.91: [20978]: --> [2:OK]
Jan 13 10:38:02.91: [20978]: <-- [5:ATM0\r]
Jan 13 10:38:03.11: [20978]: --> [2:OK]
Jan 13 10:38:03.11: [20978]: <-- [12:AT+FCLASS=2\r]
Jan 13 10:38:03.41: [20978]: --> [2:OK]
Jan 13 10:38:03.41: [20978]: <-- [10:AT+FTBC=0\r]
Jan 13 10:38:03.69: [20978]: --> [2:OK]
Jan 13 10:38:03.69: [20978]: <-- [10:AT+FBOR=0\r]
Jan 13 10:38:03.97: [20978]: --> [2:OK]
Jan 13 10:38:03.97: [20978]: <-- [13:AT+FPHCTO=30\r]
Jan 13 10:38:04.29: [20978]: --> [2:OK]
Jan 13 10:38:04.29: [20978]: <-- [24:AT+FDCC=1,5,2,2,2,0,0,0\r]
Jan 13 10:38:04.61: [20978]: --> [2:OK]
Jan 13 10:38:04.61: [20978]: <-- [31:AT+FLID="Morinda, Inc. (vger)"\r]
Jan 13 10:38:04.93: [20978]: --> [2:OK]
Jan 13 10:38:04.93: [20978]: DIAL ########
Jan 13 10:38:04.93: [20978]: <-- [19:ATDT##########@\r]
Jan 13 10:38:42.37: [20978]: --> [4:BUSY]
Jan 13 10:38:42.37: [20978]: SEND FAILED: Busy signal detected
Jan 13 10:38:42.37: [20978]: <-- [5:ATH0\r]
Jan 13 10:38:47.37: [20978]: MODEM <Timeout>
Jan 13 10:38:47.37: [20978]: SESSION END

And here is one of our config files:

#
# Configuration for a Multi-Tech MT1432, MT224BA, and MT1932ZDX modems.
#
# MT1432        firmware rev 0307 I or newer
# MT132BG       rev 0109A
# MT1932ZDX     rev 0109H
#
# Note that MT1432 modems come in several varieties:
#
# MT1432BA      uses Rockwell data pump
# MT1432BA/A    uses AT&T data pump
# MT1432BG      MT1432BA tweaked for German FCC
# MT1432MK      (for UK?)
#
# The modem has been tried with both XON/XOFF and RTS/CTS flow
# control; this configuration is for hardware flow control.
#
#
CountryCode:            1
AreaCode:               801
FAXNumber:              1-#########
LongDistancePrefix:     1
InternationalPrefix:    011
DialStringRules:        "etc/dialrules"
ServerTracing:          1
SessionTracing:         11
RecvFileMode:           0600
LogFileMode:            0600
DeviceMode:             0600
RingsBeforeAnswer:      1
SpeakerVolume:          off
GettyArgs:              "-h %l dx_%s"
LocalIdentifier:        "Morinda, Inc. (vger)"
TagLineFont:            etc/lutRS18.pcf
TagLineFormat:          "From %%l|%c|Page %%p of %%t"
MaxRecvPages:           9999
#
#
# Modem-related stuff: should reflect modem command interface
# and hardware connection/cabling (e.g. flow control).
#
ModemType:              Class2          # use class 2 interface
ModemRate:              38400           # lock rate for DCE-DTE communication
ModemFlowControl:       rtscts          # default
#
ModemHardFlowCmd:       AT&E4           # hardware flow control
ModemSoftFlowCmd:       AT&E5           # software flow control
ModemSetupDTRCmd:       AT&D3           # setup so DTR drop resets modem
ModemSetupDCDCmd:       AT&C1           # setup so DCD reflects carrier (or not)
ModemSetupAACmd:        AT+FAA=1        # enable adaptive-answer in class 2
#
# NB: some models get confused by the @
#
ModemDialCmd:           ATDT%s@         # T for tone dialing, @ for silence
#
Class2RecvDataTrigger:  "\022"          # character sent to modem to start recv
ModemReadyState:        "D"