| 1 |
# $Id$ |
| 2 |
# |
| 3 |
# prototype config for Digi AccelePort RAS |
| 4 |
# It uses a K56 chip, but is similar in behavior to Lucents. |
| 5 |
# |
| 6 |
# Note that because the devices are named as "ttyG0_00" (which on some |
| 7 |
# systems indicates a subdirectory, i.e. "ttyG0/00") you must: |
| 8 |
# `ln -s /dev/ttyG0_00 /dev/ttyG000` |
| 9 |
# for each device and refer to the symlink. Otherwise various HylaFAX |
| 10 |
# functions will fail. |
| 11 |
|
| 12 |
# CONFIG:CLASS1:Digi RAS modem*:.*:.*: Manufacturer=Digi Model=AccelePort |
| 13 |
# |
| 14 |
# BEGIN-SERVER |
| 15 |
# END-SERVER |
| 16 |
|
| 17 |
ModemType: Class1 # use this to supply a hint |
| 18 |
ModemFlowControl: rtscts # seems to work better than xonxoff |
| 19 |
|
| 20 |
# If your line supports Caller-ID, you may want to uncomment this... |
| 21 |
# ModemResetCmds: "AT#CID=1" |
| 22 |
# CallIDPattern: "NMBR=" |
| 23 |
# CallIDPattern: "NAME=" |
| 24 |
|
| 25 |
# The modem does not report +FCERROR, so this helps us simulate it |
| 26 |
Class1RMPersistence: 0 |