From 872af797f8f0588df93271ee4af5bd387e44cd48 Mon Sep 17 00:00:00 2001
From: markster <markster@5390a7c7-147a-4af0-8ec9-7488f05a26cb>
Date: Wed, 13 Feb 2002 20:24:17 +0000
Subject: Version 0.1.6 from FTP

git-svn-id: http://svn.digium.com/svn/zaptel/trunk@59 5390a7c7-147a-4af0-8ec9-7488f05a26cb
---
 zaptel.conf.sample | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

(limited to 'zaptel.conf.sample')

diff --git a/zaptel.conf.sample b/zaptel.conf.sample
index 2de39d2..e1b720f 100755
--- a/zaptel.conf.sample
+++ b/zaptel.conf.sample
@@ -1,7 +1,7 @@
 #
 # Zaptel Configuration File
 #
-# This file is parsed by the Zaptel Configurator, torcfg
+# This file is parsed by the Zaptel Configurator, ztcfg
 #
 #
 # First come the span definitions, in the format
@@ -32,6 +32,18 @@
 #span=1,0,0,esf,b8zs
 #span=2,1,0,esf,b8zs
 #
+# Next come the dynamic span definitions, in the form:
+# dynamic=<driver>,<address>,<numchans>,<timing>
+#
+# Where <driver> is the name of the driver (e.g. eth), <address> is the
+# driver specific address (like a MAC for eth), <numchans> is the number
+# of channels, and <timing> is a timing priority, like for a normal span.
+# use "0" to not use this as a timing source, or prioritize them as
+# primary, secondard, etc.  Note that you MUST have a REAL zaptel device
+# if you are not using external timing.
+#
+# dynamic=eth,eth0/00:02:b3:35:43:9c,24,0
+#
 # Next come the definitions for using the channels.  The format is:
 # <device>=<channel list>
 #
-- 
cgit v1.2.3