Debian Codegraph @

config/lucent-mt-20

raw
1 # $Id$
2 #
3 # prototype config file for MultiTech MT5634ZBA-V.92-NAM
4 #
5
6 #
7 # CONFIG: CLASS2.0:"Multi-Tech Systems"-"MT5634ZBA"-*
8 # CONFIG: CLASS2.0:"Multi-Tech Systems"-"MT5634ZPX"-*
9 # CONFIG: CLASS2.0:*-"ISI5634PCI"-*
10 # CONFIG: CLASS2.0:*-"MT5634SMI-V92"-*
11 #
12 # BEGIN-SERVER
13 # END-SERVER
14 #
15
16 ModemType: Class2.0
17 ModemRate: 19200
18 ModemNoFlowCmd: AT&K0
19 ModemSoftFlowCmd: AT&K4
20 ModemHardFlowCmd: AT&K3
21
22 Class2APCmd: AT+FAP=1,1,1
23 Class2BUGCmd: AT+FBU=0 # early firmware is buggy
24 Class2SendRTC: yes
25 Class2UseHex: yes
26
27 # Some firmwares do not report copy quality correction, although it
28 # is present and cannot be disabled. Thus modem-based CQ must be used.
29 Class2CQQueryCmd: "!(00-02),(00-02)"
30 Class2CQCmd: AT+FCQ=1,0
31
32 # versions that respond to AT+FFC=? with non-zero data support RTFCC
33 # Class2RTFCC: yes
34
35 # Some firmware revisions (i.e. 1.25 in ZBAs) report MMR support but
36 # corrupt the data. Enabling the following lines should work around this.
37 # Compare this against the modem's AT+FCC=? response.
38 # Class2DCCQueryCmd: "!(00-01),(00-05),(00-02),(00-02),(00-01),(00-01),(00),(00-07)"
39 # ModemAnswerCmd: AT+FCC=,,,,1,,,,0;A
40 # ModemDialCmd: AT+FCC=,,,,1,,,,0;DT%s
41
42 # If your modem supports ECM you may want to do something like this
43 # Class2Cmd: AT+FCLASS=2.0;+FRY=4
44
45 # If your line supports Caller-ID, you may want to uncomment this...
46 # ModemResetCmds: AT+VCID=1
47 # CallIDPattern: "NMBR="
48 # CallIDPattern: "NAME="
49
50 # Or with the MT5634ZBA-DID you'll probably need something like...
51 # ModemReadyCmds: AT*DS1*DD0*DF1*DN4 # enable DTMF-DID, wink-start, 4 digits
52 # CallIDPattern: "DTMF" # format of AT*DF1
53 # CallIDAnswerLength: 4 # four DTMF-DID digits then ATA