diff options
Diffstat (limited to 'xpp/README.Astribank')
| -rw-r--r-- | xpp/README.Astribank | 214 |
1 files changed, 187 insertions, 27 deletions
diff --git a/xpp/README.Astribank b/xpp/README.Astribank index 18c5bbe..270ab39 100644 --- a/xpp/README.Astribank +++ b/xpp/README.Astribank @@ -323,6 +323,11 @@ Astribank 8 ^^^^^^^^^^^ fxoks=1-14 +Astribank 6FXS/2FXO +^^^^^^^^^^^^^^^^^^^^^^^ + fxoks=1-12 + fxsks=13-14 + Astribank 16: 8FXS/8FXO ^^^^^^^^^^^^^^^^^^^^^^^ fxoks=1-14 @@ -355,9 +360,9 @@ Astribank 8 signalling=fxo_ks ; The real analog ports: context=from-internal - ; echocancel=yes + echocancel=yes ; echocancelwhenbriged=yes - ; echotraining=9 + ; echotraining=no channel => 1-8 ; output ports: @@ -368,16 +373,42 @@ Astribank 8 context=astbank-input channel => 11-14 immediate=no - + +Astribank 6FXS/2FXO +^^^^^^^^^^^^^^^^^^^^^^^ + [channels] + signalling=fxo_ks + ; The real analog ports: + context=from-internal + echocancel=yes + ; echocancelwhenbriged=yes + ; echotraining=no + channel => 1-6 + + ; output ports: + context=astbank-output + channel => 7-8 + ; input ports: + immediate=yes + context=astbank-input + channel => 9-12 + immediate=no + + ; FXO ports + signalling=fxs_ks + context=from-pstn + callerid=asreceived + channel => 13-14 + Astribank 16: 8FXS/8FXO ^^^^^^^^^^^^^^^^^^^^^^^ [channels] signalling=fxo_ks ; The real analog ports: context=from-internal - ; echocancel=yes + echocancel=yes ; echocancelwhenbriged=yes - ; echotraining=9 + ; echotraining=no channel => 1-8 ; output ports: @@ -607,36 +638,165 @@ Useful Module Parameters Compile-time defaults of all modules can be shown as part of the description line for the parameter in the output of modinfo. -zap_autoreg: (xpp) -Register spans automatically (1) or not (0). Default: 1. -Unsetting this could be useful if you have several Astribanks and you -want to set their registration order manually using zt_registration in -the /proc interface. +zap_autoreg (xpp):: + Register spans automatically (1) or not (0). Default: 1. + Unsetting this could be useful if you have several Astribanks and you + want to set their registration order manually using zt_registration in + the /proc interface. -initdir: (xpp) -This is the directory containing the initialization scripts. -The default is /usr/share/zaptel . -Setting this value could be useful if that location is inconvenient for you. +initdir (xpp):: + This is the directory containing the initialization scripts. + The default is /usr/share/zaptel . + Setting this value could be useful if that location is inconvenient for you. -print_dbg: (all modules) +print_dbg (all modules):: It will make the driver print tons of debugging messages. Can be sometime even handy, but overly-verbose in the case of xpp_usb. Can be safely set/unset at run-time using /sys/modules . -vmwineon: (xpd_fxs) -Enable (1) or disable (0) sending voicemail message waiting indication -to phones with a neon lamp. Disabled by default as it requires extra -work of the driver even without such a phone and may potentially have -some strange sideeffects with some phones. +The value is a bitmask of several values. The value of 0 thus means "no +debug". The different bits are (as defined in xpp/zap_debug.h) - + + * 1: GENERAL - General debug comments. + * 2: PCM - PCM-related messages. Tend to flood logs. + * 4: LEDS - Anything related to blinking leds. When they appear, there + are many of them. + * 8: SYNC - Synchronization messages. Annoy as they happen regularily. + * 16: SIGNAL - Zaptel signalling and such. + * 32: PROC - procfs interface. + * 64: REGS - Reading and writing to regiaters. Tends to flood logs. + +Thus: + + echo 33 >/sys/modules/xpp/parameters/print_dbg + +sets the module xpp to print general debugging messages (1) and procfs +debuggingmessages (32). + +vmwineon (xpd_fxs):: + Enable (1) or disable (0) sending voicemail message waiting indication + to phones with a neon lamp. Disabled by default as it requires extra + work of the driver even without such a phone and may potentially have + some strange sideeffects with some phones. + +usb1 (xpp_usb):: + Enable (1) or disable (0) support of USB1 devices. Disabled by default. + + + + + USB1 devices are not well-tested. It seems that they don't work at all + for Astribank BRI. Generally they should work with the current code, but + we expect quality issues. Hence we would like to make it very clear that + you if you have a USB1 port (rather than a USB2 one, as recommended) you + will have to take an action to enable the device. + +poll intervals (various):: + There are various values which the driver occasionally polls the device + for. For instance ,the parameter poll_battery_interval for xpd_fxo + to poll the battery (if the telco is actually connected). + + + + + The value of those parameters is typically a number in milliseconds or 0 + to disable. Under normal operation there should be no reason to play + with such parameters. + +dtmf_detection (xpd_fxs):: + enable (1) or disable (0) support of DTMF detection by the Astribank. + Disabled by defualt and curently buggy. On some earlier versions (4372 - + 4415) it was enabled by default, and disabling it there may help. + + +TROUBLSHOOTING +-------------- +The following commands provide useful input for debugging: + +* USB level listing: one of the following: + + zaptel_hardware + + lsusb | grep e4e4 + + - Look for the USB product ID (the second number after e4e4). + - If you see *11x2* (e.g: 1152)- the FPGA firmware has been loaded. + Move on. + zaptel_hardware will also show you some more details if the driver + is loaded. lsusb will just list the device. + - If it shows something as product ID *11x0* - the USB firmware is not + loaded. Maybe you need fxload. Or maybe just unplug and replug the + device. + - If it shows a product ID of *11x1* - only the USB firmware is loaded + and not the FPGA firmware is loaded. If this is still the case after + a while - either the firmware loading has failed or you don't have + fpga_load - make sure you have libusb-dev(el) installed when + building Zaptel. + - It should list all of your Astribank devices. If it doesn't (for + more than a temporary while it takes for the initial firmware + loading) - Check that the Astribank is indeed connected. + +* Are Astribank spans registered? + + zt_registration + + - This should give useful results after the drivers have identified + and initialized your devices. + - It should list all Astribank XPDs. for each of them it should write + "on" or "off". If it is "off", the span has not been registered with + Zaptel and thus cannot yet be used. + - Registration is normally done as part of `/etc/init.d/zaptel start` . + To run it manually use the command: `zt_registration on` . + - Recall that we do not register Astribank spans automaitcally to give + you full control on the order of Zaptel spans. See the module + parameter **zap_autoreg** above to change that. + +* Zaptel-level listing: + + lszaptel + + cat /proc/zaptel/* + + - Those two are almost the same. lszaptel sorts more correctly if you + have more than 10 spans, and formats the output slightly nicer. + - Here you can see if your Zaptel spans and channels were loaded, if + they were configired by ztcfg and if they are in use (typically by + Asterisk). + - The fact that a file for a span is show whos that it has been + registered with Zaptel. A n example non-configured channel + (Astribank FXS): + + 42 FXS + + - When a channel has been configured with *ztcfg* (that applies + /etc/zaptel.conf), you will see an extra column for the signalling + of the channel. The same channel after it has been configured: + + 42 FXS FXOKS + + - If a program (which is typically asterisk uses it, you'll see: + + 42 FXS FXOKS (In use) + +* Information from Asterisk + + asterisk -rx 'zap show channels' + + - If you get the error connecting to asterisk.ctl: Asterisk is not + running. Maybe it has failed to load. This may be due to + misconfigured zapata.conf or whatever reason. Check + /var/log/asterisk/messages or /var/log/asterisk/full . + - If you get the error that "there is no such command": chan_zap.so is + not loaded. This can be one of two cases: + - chan_zap.so is not even built. To see that it is available run: + + ls -l /usr/lib/asterisk/modules/chan_zap.so -poll intervals: (various) -There are various values which the driver occasionally polls the device -for. For instance ,the parameter poll_battery_interval for xpd_fxo -to poll the battery (if the telco is actually connected). + - Your Asterisk has chan_zap.so but it is not loaded. Try loading + it: + + asterisk -rx 'load module chan_zap.so' -The value of those parameters is typically a number in milliseconds or 0 -to disable. Under normal operation there should be no reason to play -with such parameters. + - You see only "pseudo": in this case you have not configured any + channels. If you have configured channels in zapata.conf, you may + need to restart asterisk (or: `unload chan_zap.so` and + `load chan_zap.so`) to apply those changes. NOTE: XPP here does not stand for X Printing Panel, XML Pull Parser, |