[Bug 337] Digi AccelePort RAS support

Lee's protype files, which forgot to CVS add

diff --git a/config/digi b/config/digi
new file mode 100644 (file)
index 0000000..6f4dd18
--- /dev/null
+++ b/config/digi
@@ -0,0 +1,17 @@
+# $Id$
+#
+# prototype config for Digi AccelePort RAS
+# It uses a K56 chip, but is similar in behavior to Lucents.
+#
+# Note that because the devices are named as "ttyG0_00" (which on some
+# systems indicates a subdirectory, i.e. "ttyG0/00") you must:
+# `ln -s /dev/ttyG0_00 /dev/ttyG000`
+# for each device and refer to the symlink.  Otherwise various HylaFAX 
+# functions will fail.
+
+# CONFIG:CLASS1:Digi RAS modem:.*:.*: Manufacturer=Digi Model=AccelePort
+#
+# BEGIN-SERVER
+# END-SERVER
+
+ModemType:             Class1          # use this to supply a hint

diff --git a/config/digi-2 b/config/digi-2
new file mode 100644 (file)
index 0000000..bed1eeb
--- /dev/null
+++ b/config/digi-2
@@ -0,0 +1,27 @@
+# $Id$
+#
+# prototype config for Digi AccelePort RAS
+# It uses a K56 chip, but is similar in behavior to Lucents.
+#
+# Note that because the devices are named as "ttyG0_00" (which on some
+# systems indicates a subdirectory, i.e. "ttyG0/00") you must:
+# `ln -s /dev/ttyG0_00 /dev/ttyG000`
+# for each device and refer to the symlink.  Otherwise various HylaFAX 
+# functions will fail.
+
+# CONFIG: CLASS2:"Digi"*-"RAS modem"*-*
+#
+# BEGIN-SERVER
+# END-SERVER
+
+ModemType:             Class2          # use this to supply a hint
+ModemRate:             19200
+ModemFlowControl:      rtscts
+ModemNoFlowCmd:                AT&K0
+ModemSoftFlowCmd:      AT&K4
+ModemHardFlowCmd:      AT&K3
+
+Class2APQueryCmd:      none            # not available
+
+# unfortunately, HylaFAX can't currently receive in MMR
+ModemAnswerCmd:                AT+FCC=,,,,1;A

diff --git a/config/digi-20 b/config/digi-20
new file mode 100644 (file)
index 0000000..9954def
--- /dev/null
+++ b/config/digi-20
@@ -0,0 +1,31 @@
+# $Id$
+#
+# prototype config for Digi AccelePort RAS
+# It uses a K56 chip, but is similar in behavior to Lucents.
+#
+# Note that because the devices are named as "ttyG0_00" (which on some
+# systems indicates a subdirectory, i.e. "ttyG0/00") you must:
+# `ln -s /dev/ttyG0_00 /dev/ttyG000`
+# for each device and refer to the symlink.  Otherwise various HylaFAX 
+# functions will fail.
+
+# CONFIG: CLASS2.0:"Digi"*-"RAS modem"*-*
+#
+# BEGIN-SERVER
+# END-SERVER
+
+ModemType:             Class2.0        # use this to supply a hint
+ModemRate:             19200
+ModemFlowControl:      rtscts
+ModemNoFlowCmd:                AT&K0
+ModemSoftFlowCmd:      AT&K4
+ModemHardFlowCmd:      AT&K3
+
+Class2APCmd:           AT+FAP=1,1,1
+Class2CQCmd:           AT+FCQ=2,2
+
+# versions that respond to AT+FFC=? with non-zero data support RTFCC
+# Class2RTFCC:         yes
+
+# unfortunately, HylaFAX can't currently receive in MMR
+ModemAnswerCmd:                AT+FCC=,,,,1;A