A400P FAQ
From Asterisk Australia
The LED of A400 is not on after compiled zaptel & asterisk
This is because you haven’t configured /etc/zaptel.conf and /etc/asterisk/zapata.conf, please go to /usr/src/zaptel-xxxx/kernel/xpp/utils，run the command: ./genzaptelconf -sdvM for auto-configuration. If the LED is on after you run the command, it means your hardware is working fine. Otherwise, please check if you have connected the system power to your card or run the command ： dmesg After that, if you see the output same as the underline one below, it looks like that you really forget to plug in the power cable to the A400P. Please shutdown your computer and plug the power cable to the card. -- DID YOU REMEMBER TO PLUG IN THE HD POWER CABLE TO THE A400P?? Unable to do INITIAL ProSLIC powerup on module 0 Init ProSlic with Manual Calibration Unable to do INITIAL ProSLIC powerup on module 0 Module 0: FAILED FXS (FCC)
What are the differences between FXS and FXO interfaces?
FXS (Foreign eXchange Station) is an interface which drives a telephone. FXS interfaces get phones plugged into them, delivery battery, and provide ringing. FXS interfaces are signalled with FXO signalling. FXO (Foreign eXchange Office) is an interface that connects to a PSTN line. It enables your PBX to have the access to the public telephone network. FXO interfaces use FXS signalling. FXS interfaces allow you to hook telephones to your PBX, and FXO interfaces allow you to connect your PBX to real PSTN lines.
Do I have to install OpenVox card when installing Zaptel? What is Zaptel?
No, you don’t have to. Zaptel is the driver for asterisk hardware. It can detect the hardware by read the configuration file in etc/zaptel.conf. The zaptel.conf can be set by hand or automatically set by running the genzaptelconf –sdvM under /usr/src/zaptel-1.4.11/kernel/xpp/utils/ (The zaptel is supposed to be installed in zaptel-1.4.11)
No Channels are found when runs the Command “Zap Show Channels”in CLI
Environment： CentOS 5.0 zaptel-1.4.12.1 asterisk-1.4.21.1 *CLI> zap show channels Chan Extension Context Language MOH Interpret pseudo default default *CLI> 1> edit command ztcfg -vvvvv root@bogon ~]# ztcfg -vvvvv Zaptel Version: 1.4.12.1 Echo Canceller: MG2 Configuration ====================== Channel map: Channel 01: FXO Kewlstart (Default) (Slaves: 01) Channel 02: FXO Kewlstart (Default) (Slaves: 02) Channel 03: FXS Kewlstart (Default) (Slaves: 03) Channel 04: FXS Kewlstart (Default) (Slaves: 04) 4 channels to configure. When your card’s FXS+FXO channels are corresponding to the output, it means your zaptel drive works fine. 2> If you use “genzaptelconf –sdvM” to automatically generated profile，then edit “asterisk –r”, input “reload” and check the output like: /etc/asterisk/zapata-channels.conf: Found And enter /etc/asterisk/zapata.conf Add a new line “#include zapata-channels.conf” at last line of this file, save and quit. -- Reloading module 'chan_zap.so' (Zapata Telephony) == Parsing '/etc/asterisk/zapata.conf': Found
- Then restart the asterisk, and use command “zap show channels” to check the output *CLI> zap show channels Chan Extension Context Language MOH Interpret pseudo default default 1 from-internal default 2 from-internal default 3 from-pstn default 4 from-pstn default
Why my card gets an IRQ miss?
Each piece of hardware takes 1,000 interrupts per second. When, for some reason the cards get less than this, an IRQ miss occurs. You can see if the card is missing interrupts using 'zttool.' IRQ misses can cause different problems with Asterisk. Symptoms of IRQ misses are bad audio quality or perhaps PRI errors, although IRQ misses will not cause alarms. Also DTMF detection not working is something that can be caused by IRQ misses as well. Several common things that contribute to IRQ misses are: -Running the X window system -Shared IRQs -No hard drive DMA -Hard drive DMA too high (shoot for udma3) -Running serial terminals or frame buffers To check for shared IRQs you can run: # cat /proc/interrupts CPU0 0 10756672 XT-PIC timer 2 0 XT-PIC cascade 5 10812879 XT-PIC uhci_hcd, uhci_hcd, wctdm 10 226219 XT-PIC t1xxp, CS46XX 11 1550046 XT-PIC eth0, nvidia 12 387234 XT-PIC i8042 14 32641 XT-PIC ide0 15 18 XT-PIC ide1 NMI 0 LOC 10757616 ERR 40481
- IS 0 Notice the A100P card sharing with the sound card, and the A400P card is sharing with the USB controller. This is likely to cause problems at most of the time. If you are not using any USB devices, then it would probably be fine. But it would be better to disable USB or get the card on its own IRQ. There are several ways to move cards to their own IRQ. -Turn on APIC -Tweak BIOS settings -Try a different PCI slot -Use setpci
3) Connect analog telephone to FXS channel but find no dialing tone It’s probably because your channels haven’t been configured correctly. Please use command “ ztcfg –vvvv” Check the output , it should like： It means your configuration in /etc/zaptel.conf have some error，FXS channels use the FXO signaling，FXO channel use the FXS signaling，so edit zaptel.conf: fxsks=1 fxsks=2 …… Run command “ztcfg –vvvv” again to check Then check /etc/asterisk/zapata.conf ，if you use command “./genzaptelconf –sdvM”, please check /etc/asterisk/zapata-channels.conf, make sure the channels config is the same as zaptel.conf（FXS channels use the FXO signaling，FXO channel use the FXS signaling），restart asterisk。
How to remove the old asterisk before install a new one?
First, please stop asterisk module and uninstall it. The red color command will stop asterisk and close all. killall -9 safe_asterisk killall -9 asterisk then please remove zaptel driver and check what modules have loaded： [root@zebru]# lsmod | grep zaptel zaptel 214820 2 wcfxo,wctdm crc_ccitt 2113 1 zaptel edit command to remove： modprobe -r wcfxo modprobe -r wctdm modprobe -r zaptel enter “lsmod | grep zaptel” again , the output should be null。 Remove Asterisk: Run the following command，then you can remove the asterisk system(Unrecoverable)。Before you do this, please backup the file you wish to keep. For example, the log file and asterisk’s config。 rm -rf /etc/asterisk rm -f /etc/zaptel.conf rm -rf /var/log/asterisk rm -rf /var/lib/asterisk rm -rf /var/spool/asterisk rm -rf /usr/lib/asterisk now your asterisk is completely removed。
When dialup on the analog telephone, it shows busy tone in CLI
This problem may be caused by the configuration in your extensions.conf，asterisk doesn’t “recognize” the number you dial, then it reports you busy tone. The following picture shows us their relationships: zapata.conf#include zapata-channels.confzapata-channels.conf [from-interal] [from-pstn] exten => 600,1,Dial(zap/1) exten => s,1,answer() exten => 600,2,Hangup() exten =>s,2,playback(xx) „„ „„extensions.conf指向指向 zapata-channels.confshow us each channel in extensions.conf (Dial-up rules config file) Corresponding context
SIP softphone can’t be registered the asterisk server
1. Please check if the Linux system’s firewall and SELinux is close. If not, please close them or it will cause the problem below . 2.cd the sip.conf，check your sip extension to see if the setting is correct . The follow is a basic configuration : [202] type=friend username=202 secret=111111 host=dynamic context=internal
Why can’t I get any Caller IDs?
In some PSTN connections, you have to subscribe to CALLER ID from the telco. In other cases, the caller id is delivered between the first and second ring, so start by waiting a while before answering, i.e. exten => s, 1, wait(2), exten => s, 2, answer
echo problem
Please verify that your rxgain and txgain are set to 0 in your zapata.conf during testing. High rxgain and txgain settings can cause echo. Please verify that your echocancelwhenbridged option is set to no. Generally, it is not necessary, and in fact undesirable, to echo cancel when the circuit path is entirely TDM. You may need to enable this only under the rare circumstance that you are unable to completely eliminate echo otherwise. The echocancel option in the zapata.conf file only enables echo cancellation for Zap channels. Please try an echocancel setting of 64 and an echotraining setting of 800 for testing. Valid settings for echocancel are 32, 64, 128, and 256. Valid settings for echotraining are 10 - 2000. The echocancel and echotraining options may need to be tweaked in order to fully eliminate echo. This will be a trial and error test that must be performed in order to determine the best echocancel and echotraining settings for your system. Start with an echocancel setting of 32. Start with an echotraining setting of 100. Increment the echotraining setting by 100. Do not exceed an echotraining setting of 1200.
- Increment the echocancel option to the next highest setting if you still exhibit echo after reaching an echotraining setting of 1200. Repeat this process until you find the settings that completely eliminate echo. Asterisk must be restarted in order for these changes to take effect.
Does the openvox card have echo cancel software?
No, zaptel has the echocancel function. You can also use Octasic SoftEcho but you will have to buy the licence first。
Common Problems with trixbox CE
zapata-channels.conf hasn’t been included by zapata.conf Please refer to chapter 2, question 1
Asterisk can’t detect hang-up signal properly
There are several settings in zaptel.conf and zapata.conf that you can experiment with. If you are using loopstart, try using kewlstart instead. Kewlstart is loopstart with disconnect supervison. Your telco must have whats called "disconnect supervision" configured on the line. Another name for disconnect supervision is "forward disconnect". You may also edit the ZT_KEWLTIME variable in zaptel.h. Navigate to the #define ZT_KEWLTIME line and change the value from 500 to 1000 (You'll need to recompile zaptel before this takes effect). You can enable busydetect and busycount to detect when a call has been hungup. Set 'busydetect=yes' and 'busycount=10'. You may experience hangups if your busycount number is too low, so increase the number until you find a variable that you're comfortable with. You can also try enabling callprogress, and set your progzone to your current country code. Callprogress is experimental, so if you experience frequent disconnects, you should disable it. Busydetect and callprogress are ways to try and detect a hangup in software which isn't as reliable as having the actual signalling indicate the hangup. If you're telcom uses polarity switching to signal for answer and/or disconnects, you should use 'answeronpolarityswitch=yes' and 'hanguponpolarityswitch=yes'
Why am I getting a clicking noise?
If a clicking noise is present when dialing through an FXO or when getting dialtone from an FXS, this is caused by echotraining. Turn it off to get rid of the clicking. The click is necessary for the echotraining.
How to solve the hang-up problems in random calls
If you have busydetect=yes or callprogress=yes in zapata.conf then this is why the problem happens. You might want to try to set busycount=10 if using busydetect. As a last resort you may just change busydetect to no: busydetect=no. Then asterisk won't try to detect the hangup on incoming calls. Notice that if "Loopstart with Remote Disconnection Supervision" (Kewlstart) is working for you than you don't need busydetect=yes at all. You can know if your current config is set to Kewlstart if you have a line fxsks=channel_no in zaptel.conf and signalling=fxs_ks in zapata.conf.