![]() |
Dear HylaFAX+ wizards: I'm using HylaFAX+ version 5.25 and I have a MultiTech MULTIMODEM ZPX INTERNAL V.92 ( MT5634ZPX-PCI-U ). I want to detect DTMF tones after answering the line and before receiving the fax for routing based on 4 digits received. Another user had a similar issue and was asked to run the following commands under minicom for diagnostics. Here are those commands and the responses: OK AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0 <== done by minicom OK ATZ OK ATS0=0 OK AT+VCID=1 OK AT+FCLASS=8 OK .R.X DATE=0125 TIME=1910 NAME=U.S. CELLULAR NMBR=919344#### ...R.RATH.R1 OK .s.s./.4.~./.8.~./.4.~./.9.~.s The modem successfully detects the "4849" that I pressed on my cell phone's keypad under minicom. However, Hylafax does NOT detect my keypresses upon answering the phone as indicated by the below log: Jan 25 19:34:49.88: [ 3764]: SESSION BEGIN 000056540 +15809200 Jan 25 19:34:49.88: [ 3764]: HylaFAX (tm) Version 5.2.5 Jan 25 19:34:49.88: [ 3764]: DELAY 2000 ms Jan 25 19:34:51.88: [ 3764]: <-- [14:AT+FCLASS=1;A\r] Jan 25 19:34:51.88: [ 3764]: --> [9:DATE=0125] Jan 25 19:34:51.88: [ 3764]: --> [9:TIME=1959] Jan 25 19:34:51.88: [ 3764]: --> [18:NAME=U.S. CELLULAR] Jan 25 19:34:51.88: [ 3764]: --> [15:NMBR=9193449722] Jan 25 19:35:00.64: [ 3764]: --> [7:CONNECT] Jan 25 19:35:00.64: [ 3764]: ANSWER: DATA CONNECTION Jan 25 19:35:00.64: [ 3764]: GETTY: START "/sbin/agetty -h ttyS5 dx_57600", pid 4767 Jan 25 19:35:00.64: [ 3764]: STATE CHANGE: ANSWERING -> GETTYWAIT Jan 25 19:35:05.64: [ 3764]: GETTY: exit status 01 Jan 25 19:35:05.64: [ 3764]: SESSION END Here are all three of my configuration files: Config: LogFacility: daemon CountryCode: 1 AreaCode: 919 LongDistancePrefix: 1 InternationalPrefix: 011 DialStringRules: etc/dialrules ServerTracing: 0xFFF #1 SessionTracing: 0xFFF #1 NotifyCmd: bin/notify-custom PageChop: none Config.ttyS4: # $Id: lucent-MT-21,v 1.4 2007/02/21 19:23:06 faxguy Exp $ # # prototype config file for MultiTech MT5634ZBA-V.92-NAM # # # CountryCode: 1 AreaCode: 919 FAXNumber: +1.919.###.#### LongDistancePrefix: 1 InternationalPrefix: 011 DialStringRules: etc/dialrules ServerTracing: 0xFFF SessionTracing: 0xFFF RecvFileMode: 0600 LogFileMode: 0600 DeviceMode: 0600 RingsBeforeAnswer: 1 SpeakerVolume: off GettyArgs: "-h %l dx_%s" LocalIdentifier: ECCM TagLineFont: etc/lutRS18.pcf TagLineFormat: "From %%l|%c|Page %%P of %%T" MaxRecvPages: 99 NotifyCmd: bin/notify-custom # # ModemType: Class2.1 ModemRate: 57600 # for V.34 faxing ModemNoFlowCmd: AT&K0 ModemSoftFlowCmd: AT&K4 ModemHardFlowCmd: AT&K3 ModemSetupDTRCmd: AT&D3 # hang up and reset on DTR drop Class2APCmd: AT+FAP=1,1,1 Class2BUGCmd: AT+FBU=0 # early firmware is buggy Class2SendRTC: yes Class2UseHex: yes # Some firmwares do not report copy quality correction, although it # is present and cannot be disabled. Thus modem-based CQ must be used. Class2CQQueryCmd: "!(00-02),(00-02)" Class2CQCmd: AT+FCQ=1,0 # versions that respond to AT+FFC=? With non-zero data support RTFCC # Class2RTFCC: yes # Some firmware revisions (I.e. 1.25) report MMR support but corrupt the data. # Some firmware revisions (I.e. 1.25 and 1.28) report extended resolution support but # have trouble with 300x300 and 400x400 resolutions and corrupt DIS for inch resolutions. # Enabling the following lines should work around these things. # Compare this against the modem's AT+FCC=? Response. # Class2DCCQueryCmd: "!(03),(00-05),(00-02),(00-02),(00-01),(00-01),(00) (00-07)" # ModemAnswerCmd: AT+FCC=03,,,,1,,,,0;A # ModemDialCmd: AT+FCC=03,,,,1,,,,0;DT%s # If your modem supports ECM you may want to do something like this # Class2Cmd: AT+FCLASS=2.1;+FRY=4 # If your line supports Caller-ID, you may want to uncomment this... # ModemResetCmds: AT+VCID=1 # CallIDPattern: "NMBR=" # CallIDPattern: "NAME=" # Or with the MT5634ZBA-DID you'll probably need something like... #ModemReadyCmds: AT*DS1*DD0*DF1*DN4 # enable DTMF-DID, wink-start, 4 digits # CallIDPattern: "DTMF" # format of AT*DF1 # CallIDAnswerLength: 4 # four DTMF-DID digits then ATA # ModemResetCmds: AT*DP1 # to reverse the polarity ModemRingResponse: AT+FCLASS=8;H1 CallIDPattern: SHIELDED_DTMF CallIDAnswerLength: 4 ModemAnswerCmd: <delay:100>AT+FCLASS=1;A config.ttyS5: # $Id: lucent-MT-21,v 1.4 2007/02/21 19:23:06 faxguy Exp $ # # prototype config file for MultiTech MT5634ZBA-V.92-NAM # # # CountryCode: 1 AreaCode: 919 FAXNumber: +1.919.###.#### LongDistancePrefix: 1 InternationalPrefix: 011 DialStringRules: etc/dialrules ServerTracing: 0xFFF SessionTracing: 0xFFF RecvFileMode: 0600 LogFileMode: 0600 DeviceMode: 0600 RingsBeforeAnswer: 1 SpeakerVolume: off GettyArgs: "-h %l dx_%s" LocalIdentifier: ECCM TagLineFont: etc/lutRS18.pcf TagLineFormat: "From %%l|%c|Page %%P of %%T" MaxRecvPages: 99 NotifyCmd: bin/notify-custom # # ModemType: Class2.1 ModemRate: 57600 # for V.34 faxing ModemNoFlowCmd: AT&K0 ModemSoftFlowCmd: AT&K4 ModemHardFlowCmd: AT&K3 ModemSetupDTRCmd: AT&D3 # hang up and reset on DTR drop Class2APCmd: AT+FAP=1,1,1 Class2BUGCmd: AT+FBU=0 # early firmware is buggy Class2SendRTC: yes Class2UseHex: yes # Some firmwares do not report copy quality correction, although it # is present and cannot be disabled. Thus modem-based CQ must be used. Class2CQQueryCmd: "!(00-02),(00-02)" Class2CQCmd: AT+FCQ=1,0 # versions that respond to AT+FFC=? With non-zero data support RTFCC # Class2RTFCC: yes # Some firmware revisions (I.e. 1.25) report MMR support but corrupt the data. # Some firmware revisions (I.e. 1.25 and 1.28) report extended resolution support but # have trouble with 300x300 and 400x400 resolutions and corrupt DIS for inch resolutions. # Enabling the following lines should work around these things. # Compare this against the modem's AT+FCC=? Response. # Class2DCCQueryCmd: "!(03),(00-05),(00-02),(00-02),(00-01),(00-01),(00) (00-07)" # ModemAnswerCmd: AT+FCC=03,,,,1,,,,0;A # ModemDialCmd: AT+FCC=03,,,,1,,,,0;DT%s # If your modem supports ECM you may want to do something like this # Class2Cmd: AT+FCLASS=2.1;+FRY=4 # If your line supports Caller-ID, you may want to uncomment this... # ModemResetCmds: AT+VCID=1 # CallIDPattern: "NMBR=" # CallIDPattern: "NAME=" # Or with the MT5634ZBA-DID you'll probably need something like... # ModemReadyCmds: AT*DS1*DD0*DF1*DN4 # enable DTMF-DID, wink-start, 4 digits # CallIDPattern: "DTMF" # format of AT*DF1 # CallIDAnswerLength: 4 # four DTMF-DID digits then ATA # ModemResetCmds: AT*DP1 # to reverse the polarity ModemRingResponse: AT+FCLASS=8;H1 CallIDPattern: SHIELDED_DTMF CallIDAnswerLength: 4 ModemAnswerCmd: <delay:100>AT+FCLASS=1;A Davie Lynn IT Administrator East Carolina Case Management, Inc. ____________________ HylaFAX(tm) Users Mailing List _______________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*