[Asterisk-cvs] zaptel zaptel.conf.sample,1.17,1.18
kpfleming
kpfleming
Tue Oct 4 18:51:58 CDT 2005
- Previous message: [Asterisk-cvs] asterisk/apps app_directory.c,1.44,1.45
- Next message: [Asterisk-cvs] asterisk/configs alarmreceiver.conf.sample, 1.1,
1.2 codecs.conf.sample, 1.4, 1.5 extensions.conf.sample, 1.46,
1.47 iax.conf.sample, 1.55, 1.56 iaxprov.conf.sample, 1.1,
1.2 indications.conf.sample, 1.29, 1.30 logger.conf.sample,
1.14, 1.15 manager.conf.sample, 1.6, 1.7 meetme.conf.sample,
1.4, 1.5 mgcp.conf.sample, 1.11, 1.12 modules.conf.sample, 1.6,
1.7 musiconhold.conf.sample, 1.9, 1.10 queues.conf.sample,
1.31, 1.32 sip.conf.sample, 1.72, 1.73 voicemail.conf.sample,
1.53, 1.54 vpb.conf.sample, 1.11, 1.12 zapata.conf.sample,
1.53, 1.54
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
Update of /usr/cvsroot/zaptel
In directory mongoose.digium.com:/tmp/cvs-serv1526
Modified Files:
zaptel.conf.sample
Log Message:
make timing source configuration easier to understand (issue #5356)
Index: zaptel.conf.sample
===================================================================
RCS file: /usr/cvsroot/zaptel/zaptel.conf.sample,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -d -r1.17 -r1.18
--- zaptel.conf.sample 11 Dec 2004 04:30:25 -0000 1.17
+++ zaptel.conf.sample 4 Oct 2005 22:47:45 -0000 1.18
@@ -5,12 +5,29 @@
#
#
# 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"
+# span=<span num>,<timing source>,<line build out (LBO)>,<framing>,<coding>[,yellow]
+#
+# All T1/E1 spans generate a clock signal on their transmit side. The
+# <timing source> parameter determines whether the clock signal from the far
+# end of the T1/E1 is used as the master source of clock timing. If it is, our
+# own clock will synchronise to it. T1/E1's connected directly or indirectly to
+# a PSTN provider (telco) should generally be the first choice to sync to. The
+# PSTN will never be a slave to you. You must be a slave to it.
+#
+# Choose 1 to make the equipment at the far end of the E1/T1 link the preferred
+# source of the master clock. Choose 2 to make it the second choice for the master
+# clock, if the first choice port fails (the far end dies, a cable breaks, or
+# whatever). Choose 3 to make a port the third choice, and so on. If you have, say,
+# 2 ports connected to the PSTN, mark those as 1 and 2. The number used for each
+# port should be different.
+#
+# If you choose 0, the port will never be used as a source of timing. This is
+# appropriate when you know the far end should always be a slave to you. If the
+# port is connected to a channel bank, for example, you should always be its
+# master. Any number of ports can be marked as 0.
+#
+# Incorrect timing sync may cause clicks/noise in the audio, poor quality or failed
+# faxes, unreliable modem operation, and is a general all round bad thing.
#
# The line build-out (or LBO) is an integer, from the following table:
# 0: 0 db (CSU) / 0-133 feet (DSX-1)
- Previous message: [Asterisk-cvs] asterisk/apps app_directory.c,1.44,1.45
- Next message: [Asterisk-cvs] asterisk/configs alarmreceiver.conf.sample, 1.1,
1.2 codecs.conf.sample, 1.4, 1.5 extensions.conf.sample, 1.46,
1.47 iax.conf.sample, 1.55, 1.56 iaxprov.conf.sample, 1.1,
1.2 indications.conf.sample, 1.29, 1.30 logger.conf.sample,
1.14, 1.15 manager.conf.sample, 1.6, 1.7 meetme.conf.sample,
1.4, 1.5 mgcp.conf.sample, 1.11, 1.12 modules.conf.sample, 1.6,
1.7 musiconhold.conf.sample, 1.9, 1.10 queues.conf.sample,
1.31, 1.32 sip.conf.sample, 1.72, 1.73 voicemail.conf.sample,
1.53, 1.54 vpb.conf.sample, 1.11, 1.12 zapata.conf.sample,
1.53, 1.54
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the svn-commits
mailing list