From 0190168de86691a781eec114fbc3e68cf53861a1 Mon Sep 17 00:00:00 2001 From: tzafrir Date: Sat, 16 Feb 2008 14:13:27 +0000 Subject: * Start documenting module parameters in the README. * Update the hardware supported by xpp. git-svn-id: http://svn.digium.com/svn/zaptel/branches/1.2@3837 5390a7c7-147a-4af0-8ec9-7488f05a26cb --- README | 78 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 77 insertions(+), 1 deletion(-) (limited to 'README') diff --git a/README b/README index f110293..cd771fc 100644 --- a/README +++ b/README @@ -36,7 +36,7 @@ Analog Cards - wctdm: * Digium TDM400P: up to 4 analog ports - xpp: Xorcom Astribank: a USB connected unit of up to 32 ports - (also BRI) + (includeing the digital BRI and E1/T1 modules) - wcfxo: X100P, similar and clones. A simple single-port FXO card - wcusb: Digium S100U: A simple single-port USB FXS unit @@ -265,6 +265,82 @@ and xpp_usb (in that order) add the following line to that file: Currently that file must set "TELEPHONY=yes" for the zaptel init.d to work. +Module Parameters +~~~~~~~~~~~~~~~~~ +The kernel modules can be configured through module parameters. Module +parameters can optionally be set at load time. They are normally set (if +needed) by a line in a file under /etc/modprobe.d/ or in the file +/etc/modprobe.conf (Or /etc/modules.conf in kernel 2.4). + +Example line: + + options zaptel debug=1 + +The module parameters can normally be modified at runtime through sysfs: + + pungenday:~# cat /sys/module/zaptel/parameters/debug + 0 + pungenday:~# echo 1 >/sys/module/zaptel/parameters/debug + pungenday:~# cat /sys/module/zaptel/parameters/debug + 1 + +Viewing and setting parameters that way is possible as of kernel 2.6 . +In kernels older than 2.6.10, the sysfs "files" for the parameters +reside directly under /sys/module/'module_name' . + +Useful module parameters: + +debug (most modules):: + Sets debug mode / debug level. With most modules 'debug' can be either + disabled (0, the default value) or enabled (any other value). + + + + + wctdm and wcte1xp print several extra debugging messages if the value + of debug is more than 1. + + + + + Some modules have "debugging flags" bits - the value of debug is a + bitmask and several messages are printed if some bits are set: + - ztdummy: + * 1: DEBUG_GENERAL - general error messages. + * 2: DEBUG_TICKS - Show that the module is alive :-) + - wctdm24xxp: + * 1: DEBUG_CARD + * 2: DEBUG_ECHOCAN + - wct4xxp: + * 1: DEBUG_MAIN + * 2: DEBUG_DTMF + * 4: DEBUG_REGS + * 8: DEBUG_TSI + * 16: DEBUG_ECHOCAN + * 32: DEBUG_RBS + * 64: DEBUG_FRAMER + + + + + The xpp modules use 'print_dbg' instead of 'debug' . Refer to + README.Astribank. + +deftaps (zaptel):: + The default size for the echo canceller. The number is in "taps", that + is "samples", 1/8 ms. The default is 64 - for a tail size of 8 ms. + + + + + Asterisk's chan_zap tends to pass its own value anyway, with a + different default size. So normally setting this doesn't change + anything. + +To get a list of parameters supported by a module, use + + modinfo module_name + +Or, for a module you have just built: + + modinfo ./module_name.ko + +For the xpp modules this will also include the description and default +value of the module. You can find a list of useful xpp module parameters +in README.Astribank . + Zaptel PERL modules ------------------- -- cgit v1.2.3