This troubleshooting is conducted to give users a guideline to fix
problems. here, most of problems are list out, if user follows that exactly, most of the problems should be solved. （***keep updating***）
===Q1, You can not compile zaptel/mISDN and asterisk===
please make sure that:
1) You have installed all necessary packages and kernel source.
2) Make sure the version of kernel source is exactly same with the version of the kernel.
please check the few links:
3) make sure that you do not miss any packages or files in asterisk or zaptel.
4) make sure your system can access
===Q2, ZT_SPANCONFIG failed on span 1: Invalid argument (22)===
if you are using bristuff with bri cards, please check:
1) run lspci -vvvvv, make sure the system can detect the card. Tiger jet chip will be found. If there is no such Tiger jet chip, please clean the PCI slot and try again.
2) if lspc can find the card, make sure the pci id is included in the PCI table in our driver. how to patch the picid, please refer this link:
3) if step 1 and step 2 are ok, please check the zaptel.conf or system.conf to make sure that the setting is correct.
4) if step 3 is correct, please make sure that there is no mISDN tiger jet module in the system, if it is there, please remove that or add to blacklist.
5) if you still can not boot it up, you have to recompile bristuff and asterisk again.
===Q3, You can not make calls from asterisk===
there are few reasons why you can not make calls:
1) check your extensions from your asterisk side, make sure your sip is ready to make calls, and SIP is with a right context what you put in extensions.conf
2) your qozap.ko or hfcmulti.ko does not boot up(leds are off).
3) leds are up and card driver has boot up properly, but the zapata.conf is
, so asterisk does not boot up properly,
please check by run: zap show channels
if is empty or no such command, you should check your zapata.conf/misdn.conf
4) if you are using mISDN, please make sure the misdn stack is up and active.
5) You maybe recompile your zaptel/mISDN and asterisk again.
===Q4, How do you adjust the volume of voice for BRI cards?===
You can edit rxgain and txgain in chan_misdn or zapata.conf.
===Q5, list of drivers of BRI cards===
Bri cards can work with these drivers:
1) mISDN-1_1_X， links:
2) mISDN v2
%20B200E%20B400P%20B400E-User-Manual-mISDNv2.pdf
(v2)
3) Bristuff
P_B400P_B400E_User_Manual_bristuff.pdf
4) Dahdi wcb4xxp
%3D1
5) isdn4bsd
~hselasky/isdn4bsd/
Before implementing one of these drivers, please make an investigation for your business requirement.
===Q6, B200P_B400P_B800P pin assignment===
if you want to check the pin assignment, please refer this:
%3D2
===Q7, Use PCM connection with OpenVox BRI cards.===
if you want to use PCM cable to connect with the two BRI cards,
please refer this link:
%3D3
===Q8, netjetpci causes a problem with mISDN(B400P)+Zaptel(A400P)===
If you conbine the bri card and analog card, please remove the netjetpci,
this is a solution to solve the problem:
%3D3
===Q9, How can you open the debug for mISDN/asterisk?===
1) You can edit the file logger.conf under /etc/asterisk,
enable the debug or error, those message will be stored under
/var/log/asterisk
2) you also can start your asterisk in this way:
asterisk -vvvvvvvvgc -d
3) if you want to debug the mISDN, please enable the debug in mISDN.conf
===Q10, How can i check the IRQ of BRI cards?===
please run the command:
cat /proc/interrupts
you should see the IRQs, Make sure the card has OWN IRQ, Do NOT share with other devices.
more details, please check from here:
===Q11, the definations of NT and TE ===
the bri cards support NT and TE mode. you can refer these links for the definitions:
===Q12, Sound Quality Problems with Analog cards===
please refer this link:
===Q13, MISDN with asterisk/trixbox/elastix===
please refer these links:
%20B100P%20B200P%20B400P%20B800P%20with%20mISDN.pdf
===Q14, I am hearing an echo. What can I do to fix this?===
please refer these links:
===Q15, zaphfc: dropped audio (z1=2331, z2=2314, wanted 8 got 17, dropped 9)===
you can have a try to set please add apm=off in your grub.conf
===Q16, When will the LED's light up on my BRI cards===
Due to the difference of drivers, the LEDs of cards are different.
1) If the drivers are loaded correctly, the LEDs are in RED color.
2) If the layer1 and layer2 are up, and a conversation is established, the leds will be in GREEN.
3) B100P does not support LEDs
===Q17, Why is my card getting an IRQ miss?===
Each peice 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
MIS 0
Notice the T100P card sharing with the sound card, and the TDM400P card is sharing with the USB controller. This will most likely cause problems. If you are not using any USB devices that would probably be ok, but it would be best to disable USB or get the card on it's 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
refer this link from digium:
===Q18, Why am I having DTMF detection problems?===
Zaptel DTMF Detection Problems
DTMF detection problems can be caused by a number of different factors. The most common is running the X Windows System. Another cause of DTMF detection problems is the relaxdtmf option in Zapata.conf. It may need to be turned on or off. If you need to force all DTMF detection to be done in software, you can set vpmdtmfsupport to 0 in wctdm24xxp.c or wct4xxp.c and recompile, or you can specify it as a kernel module option at runtime.
SIP DTMF Detection Problems
If you are having problems sending DTMF digits amd are using a SIP phone, make sure the dtmfmode they have set is the same on the phone and in Asterisk. Also make sure you are not sending both inband and out-of-band (rfc2833) tones.
===Q19, I am getting error messages about PCI Master Aborts. What is wrong?===
This is a very rare case. When your computer's PCI subsystem experiences serious problems with OpenVox's cards upon initialization of the card, Linux will print out scrolling "PCI Master Abort" messages. What you should do is go into your system's BIOS, and turn off your motherboard's PNP (plug and play) feature. If this does not resolve your issue, You should contact OpenVox support.
===Q20, issues with wcb4xxp===
this is a link with dahdi wcb4xxp, you many refer these links:
===Q21, list of asterisk pbx distributions:===
===Q22, How can you install asterisk with Debian Ubutun===
http://ww2.eq.uc.pt/servicos/laca/recursos/debian/voip-resources/installation-of-misdn
===Q23, How can you install asterisk with Fedora?===
===Q24, How can you install asterisk with SuSe?===
===Q25, install asterisk with Free BSD===
===Q26, List of Asterisk OS Platforms===
===Q27, Centos with asterisk===
===Q28, How do you report a problem===
In order to solve customer's problems very effective and efficiency,
when seeking a help from us, please give these information:
1) versions of kernel and Linux distribution
2) versions of asterisk and zaptel/dahdi
3) the name of cards used in your system
4) debug and error information from your system and asterisk
5) sending us zaptel(zaptel.conf and zapata.conf) or dahdi (system.conf and chan_dahdi.conf)
configuration files and extension.conf
6) after loading the driver, run the command: demsg and send the information to us
7) sending us the result of the command: cat /proc/interrupts
8) sending us the message of asterisk console when you making a call
9) inform the protocols you are using in your system
10) send us a working ssh account with root permission if you need us to check the system.
11) make a backup for your important files
12) describe the problem in details
13) if you are using mISDN, please open the debug mode and run dmesg to get the
error or log message.
===Q29,FATAL: Module qozap.ko cannot be found ===
if this problem occurred, please make sure:
1) the module is compiled and installed properly
2) you entered a right kernel, which you used to compile the zaptel
3) make sure you have a access permission to load the module.
4) make sure the qozap.ko is under /lib/modules/2.6.XX/extra
===Q30,FATAL: Module zaphfc.ko not found ===
if this problem occurred, please make sure:
1) the module is compiled and installed properly
2) you entered a right kernel, which you used to compile the zaptel
3) make sure you have a access permission to load the module.
4) make sure the zaphfc.ko is under /lib/modules/2.6.XX/extra
===Q31, Disable Hisax and isdn in Centos/debian ===
If you are running a BRI card in the centos/FC or debian, please remove
Hisax and ISDN service from your system, add those services or modules into the system black list.
those packages will be conflict with mISDN/Bristuff/wcb4xxpdriver.
more details, please check the link:
===Q32, How to debug brisutff/mISDN ===
When loading the qozap.ko/zaphfc.ko with a debug mode,
please loadding the driver in this way:
modprobe qozap,ko debug=1 // open the debug and check the /var/log/message
if you run misdn, please enable the debug in misdn.conf
===Q33, RHEL/Centos 5.2: xpp/xdefs.h:117: error: conflicting types for ‘bool’ ===
please refer this:
===Q34, xpp modules do not compile with kernel 2.6.19-1.2919.fc7===
please refer this:
===Q35, spinlock.h error with RHEL 4===
please refer this link:
===Q36, Compile error on CentOS-4.6 with Kernel-2.6.9-67.0.15.ELsmp and CONFIG_DAHDI_NET===
please refer this link:
===Q37, dahdi_compat.h:31:27: error: zaptel/zaptel.h: No such file ===
please read this:
===Q38, when compiling zaptel/bristuff, error: You do not appear to have the sources for...===
please refer this:
===Q39, Bug#439814: zaptel-source: oslec_echo_can_identify undefined symbol===
please refer this:
===Q40, How to install Octasic SoftEcho ===
please refer these links:
===Q41, Bug in Zaptel 1.2.20.1 and 1.4.5.1 - Only MG2 ===
please refer this:
===Q42, Howto: OSLEC echo canceling + DAHDI 2.1.0.4 + Asterisk 1.4 ===
please refer this:
===Q43, Difference between zaptel and dahdi ===
please refer these links:
===Q44, Tonezones for zaptel.conf ===
The file zonedata.c contains the information about the tone zones used in libtonezone (and hence also in ztcfg). Here is a list of those zones:
us United States / North America
au Australia
fr France
nl Netherlands
uk United Kingdom
fi Finland
es Spain
jp Japan
no Norway
at Austria
nz New Zealand
it Italy
us-old United States Circa 1950 / North America
gr Greece
tw Taiwan
cl Chile
se Sweden
be Belgium
sg Singapore
il Israel
br Brazil
hu Hungary
lt Lithuania
pl Poland
za South Africa
pt Portugal
ee Estonia
mx Mexico
in India
de Germany
ch Switzerland
dk Denmark
cz Czech Republic
cn China
ar Argentina
my Malaysia
th Thailand
bg Bulgaria
ve Venezuela
ph Philippines
ru Russian Federation
tr Turkey
===Q45, Tools from zaptel to dahdi ===
ztcfg -> dahdi_cfg
ztmonitor -> dahdi_monitor
ztscan -> dahdi_scan
ztspeed -> dahdi_speed
zttest -> dahdi_test
zttool -> dahdi_tool
zapconf -> dahdi_genconf (deprecates genzaptelconf)
===Q46, Why are you unable to call out with Asterisk 1.4.22? ===
If you are using wctdm or opvxa1200 with Zaptel and Asterisk 1.4.22 then there is a known issue with outbound calls. The reason you are not able to call out is because Asterisk 1.4.22 has a new feature which detects if a analog line is plugged in or not, but this feature only works with Dahdi. So to fix the issue you can do one of the following.
edit the file under /asterisk-1.4.22、channels/chan_dahdi.c" find this line
#ifdef DAHDI_CHECK_HOOKSTATE return 0;
#else return 1;
Change the "0" to a "1"
#ifdef DAHDI_CHECK_HOOKSTATE return 1;
#else return 1;
===Q47, install Asterisk zaphfc ===
please refer this link:
===Q48, Install bri card and analog cards in one system ===
if you want to install analog cards and bri cards in one system, it can be done in two ways:
1) install bristuff for both of analog cards and bri cards.
2) install mISDN with bri cards and zaptel with analog cards
please refer this link:
===Q49, mISDN v2(LCR) with debian/asterisk ===
please refer these links:
http://blog.runtux.com/2009/03/09/61/
===Q50, patch---mISDN rejects incoming calls ===
misdn rejects incoming calls, please refer this patch:
阅读(3532) | 评论(0) | 转发(0) |
