Version 0.1.0 from FTP

git-svn-id: http://svn.digium.com/svn/zaptel/trunk@9 5390a7c7-147a-4af0-8ec9-7488f05a26cb

1 files changed, 102 insertions, 0 deletions

diff --git a/zaptel.conf.sample b/zaptel.conf.sample
new file mode 100755
index 0000000..2de39d2
--- /dev/null
+++ b/zaptel.conf.sample
@@ -0,0 +1,102 @@
+#
+# Zaptel Configuration File
+#
+# This file is parsed by the Zaptel Configurator, torcfg
+#
+#
+# First come the span definitions, in the format
+# span=<span num>,<timing>,<line build out (LBO)>,<framing>,<coding>[,yellow]
+# 
+# The timing parameter determines the selection of primary, secondary, and
+# so on sync sources.  If this span should be considered a primary sync
+# source, then give it a value of "1".  For a secondary, use "2", and so on.
+# To not use this as a sync source, just use "0"
+#
+# The line build-out (or LBO) is an integer, from the following table:
+# 0: 0 db (CSU) / 0-133 feet (DSX-1)
+# 1: 133-266 feet (DSX-1)
+# 2: 266-399 feet (DSX-1)
+# 3: 399-533 feet (DSX-1)
+# 4: 533-655 feet (DSX-1)
+# 5: -7.5db (CSU)
+# 6: -15db (CSU)
+# 7: -22.5db (CSU)
+#
+# The framing is one of "d4" or "esf"
+#
+# The coding is one of "ami" or "b8zs"
+#
+# If the keyword "yellow" follows, yellow alarm is transmitted when no
+# channels are open.
+#
+#span=1,0,0,esf,b8zs
+#span=2,1,0,esf,b8zs
+#
+# Next come the definitions for using the channels.  The format is:
+# <device>=<channel list>
+#
+# Valid devices are:
+#
+# "e&m"     : Channel(s) are signalled using E&M signalling (specific
+#             implementation, such as Immediate, Wink, or Feature Group D
+#             are handled by the userspace library).
+# "fxsls"   : Channel(s) are signalled using FXS Loopstart protocol.
+# "fxsgs"   : Channel(s) are signalled using FXS Groundstart protocol.
+# "fxsks"   : Channel(s) are signalled using FXS Koolstart protocol.
+# "fxols"   : Channel(s) are signalled using FXO Loopstart protocol.
+# "fxogs"   : Channel(s) are signalled using FXO Groundstart protocol.
+# "fxoks"   : Channel(s) are signalled using FXO Koolstart protocol.
+# "unused"  : No signalling is performed, each channel in the list remains idle
+# "clear"   : Channel(s) are bundled into a single span.  No conversion or
+#             signalling is performed, and raw data is available on the master.
+# "indclear": Like "clear" except all channels are treated individually and
+#             are not bundled.  "bchan" is an alias for this.
+# "rawhdlc" : The zaptel driver performs HDLC encoding and decoding on the 
+#             bundle, and the resulting data is communicated via the master
+#             device.
+# "fcshdlc" : The zapdel driver performs HDLC encoding and decoding on the
+#             bundle and also performs incoming and outgoing FCS insertion
+#             and verification.  "dchan" is an alias for this.
+# "nethdlc" : The zaptel driver bundles the channels together into an
+#             hdlc network device, which in turn can be configured with
+#             sethdlc (available separately).
+#
+# The channel list is a comma-separated list of channels or ranges, for
+# example:
+#
+#   1,3,5 (channels one, three, and five)
+#   16-23, 29 (channels 16 through 23, as well as channel 29
+#
+# So, some complete examples are:
+#   e&m=1-12
+#   nethdlc=13-24
+#   fxsls=25,26,27,28
+#   fxols=29-32
+#
+#fxoks=1-24
+#bchan=25-47
+#dchan=48
+#fxols=1-12
+#fxols=13-24
+#e&m=25-29
+#nethdlc=30-33
+#clear=44
+#clear=45
+#clear=46
+#clear=47
+#fcshdlc=48
+#
+# Finally, you can preload some tone zones, to prevent them from getting
+# overwritten by other users (if you allow non-root users to open /dev/tor*
+# interfaces anyway.  Also this means they won't have to be loaded at runtime.
+# The format is "loadzone=<zone>" where the zone is a two letter country code.
+# 
+# You may also specify a default zone with "defaultzone=<zone>" where zone
+# is a two letter country code.
+#
+loadzone = us
+#loadzone=fr
+#loadzone=fr
+#loadzone=de
+#loadzone=uk
+defaultzone=us