summaryrefslogtreecommitdiff
path: root/README.fxotune
diff options
context:
space:
mode:
authormattf <mattf@5390a7c7-147a-4af0-8ec9-7488f05a26cb>2005-02-25 21:33:25 +0000
committermattf <mattf@5390a7c7-147a-4af0-8ec9-7488f05a26cb>2005-02-25 21:33:25 +0000
commitd82a4fd0f404af903f95b15d46982ba1afd6a41a (patch)
treeaf5423769a2c20d4966441801dbb6a1281697547 /README.fxotune
parent97566e3aa18cab8e7291573180ed2579a2a8f664 (diff)
Added readme file for fxotune
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@596 5390a7c7-147a-4af0-8ec9-7488f05a26cb
Diffstat (limited to 'README.fxotune')
-rwxr-xr-xREADME.fxotune21
1 files changed, 21 insertions, 0 deletions
diff --git a/README.fxotune b/README.fxotune
new file mode 100755
index 0000000..99a5430
--- /dev/null
+++ b/README.fxotune
@@ -0,0 +1,21 @@
+Q. I have echo problems on my FXO modules and I've tried the different
+echo cancellation algorithms in zconfig.h, tried tweaking the gains, and
+still nothing works. What can I do?
+
+A. Use the fxotune utility.
+
+To use:
+Just run the fxotune utility with the -i option. (`fxotune -i`) It should
+discover which zap channels are FXO modules and tune them accordingly. Be warned
+however, it takes a significant amount of time for EACH module to test, I would
+say somewhere around 2-3 minutes. But you only have to initialize it once for
+the line. It will write a configuration file to /etc/fxotune.conf. You will
+need to have your system run fxotune with the -s flag (`fxotune -s`) to set the
+module with the previously discovered values from fxotune.conf for it to take
+affect, so essentially if each time you reboot the machine you need to run
+`fxotune -s`. You might consider putting it in your startup scripts some time
+after the module loads and before asterisk runs.
+
+As always, if you have any questions, you can email me at creslin@NOSPAMdigium.com
+
+Matthew Fredrickson