BRI Cards FAQ
Q1, 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.
Q2, How do you adjust the volume of voice for BRI cards?
You can edit rxgain and txgain in chan_misdn or zapata.conf.
Q3, list of drivers of BRI cards
Bri cards can work with these drivers:
1) mISDN-1_1_X， links:
2) mISDN v2
4) Dahdi wcb4xxp
Before implementing one of these drivers, please make an investigation for your business requirement.
Q4, B200P_B400P_B800P pin assignment
if you want to check the pin assignment, please refer this:
Q5, 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:
Q6, 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
Q7, 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
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
Q8, How can i check the IRQ of BRI cards?
please run the command:
you should see the IRQs, Make sure the card has OWN IRQ, Do NOT share with other devices.
more details, please check from here:
Q9, the definations of NT and TE
the bri cards support NT and TE mode. you can refer these links for the definitions:
Q10, Sound Quality Problems with Analog cards
please refer this link:
Q11, MISDN with asterisk/trixbox/elastix
please refer these links:
Q12, I am hearing an echo. What can I do to fix this?
please refer these links:
Q13, 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
Q14, 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
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: http://kb.digium.com/entry/63/
Q15, 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.
Q16, 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.
Q17, list of asterisk pbx distributions:
Q18, How can you install asterisk with Debian Ubutun
Q19, How can you install asterisk with Fedora?
Q20, How can you install asterisk with SuSe?
Q21, install asterisk with Free BSD
Q22, List of Asterisk OS Platforms
Q23, Centos with asterisk
Q24, 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.
Q25, 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:
Q26, 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
Q27, How to install Octasic SoftEcho
please refer these links:
Q28, Howto: OSLEC echo canceling + DAHDI 220.127.116.11 + Asterisk 1.4
Q29, 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;
Q30, install Asterisk zaphfc
Q31, 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:
Q32, To get the quick support, what information about the system I should send?
- Versions of kernel and Linux distribution
- Versions of asterisk and zaptel/dahdi
- Model of OpenVox products
- Debug and error information from your system and asterisk
- Zaptel(zaptel.conf and zapata.conf) or dahdi (system.conf and chan_dahdi.conf) configuration files and extension.conf if your have trouble with dialplan
- After loading the driver, run the command: demsg and send the information to us
- Output of the command: cat /proc/interrupts
- Message in asterisk console when you making a call, if you have trouble to drop/receive calls.
- Protocols you want to use(FXS,FXO,PRI..)
- Ssh account with root permission if you need us to check the system.
- Make a backup for your important files
- Describe the problem in details
- Serial numbers of OpenVox’s products
Q33, Disconnect cause codes
|0x1||1||Unallocated or unassigned number|
|0x2||2||No route to specified transit network (Transit Network Identity)|
|0x3||3||No route to destination|
|0x4||4||Send special information tone|
|0x5||5||Misdialled trunk prefix|
|0x7||7||Call awarded and being delivered in an established channel|
|0x8||8||Prefix 0 dialed but not allowed|
|0x9||9||Prefix 1 dialed but not allowed|
|0xA||10||Prefix 1 not dialed but required|
|0xB||11||More digits received than allowed, call is proceeding|
|0x10||16||Normal call clearing|
|0x12||18||No user responding|
|0x13||19||T.301 expired: – User Alerted, No answer from user|
|0x16||22||Number changed to number in diagnostic field.|
|0x17||23||Reverse charging rejected|
|0x1A||26||Non-selected user clearing|
|0x1B||27||Destination out of order|
|0x1C||28||Invalid number format or incomplete address|
|0x1D||29||EKTS facility rejected by network|
|0x1E||30||Response to STATUS ENQUIRY|
|0x21||33||Circuit out of order|
|0x22||34||No circuit/channel available|
|0x24||36||Out of order|
|0x26||38||Network out of order|
|0x27||39||Transit delay range cannot be achieved|
|0x28||40||Throughput range cannot be achieved|
|0x2A||42||Switching equipment congestion|
|0x2B||43||Access information discarded|
|0x2C||44||Requested circuit channel not available|
|0x2E||46||Precedence call blocked|
|0x2F||47||Resource unavailable, unspecified|
|0x31||49||Quality of service unavailable|
|0x32||50||Requested facility not subscribed|
|0x33||51||Reverse charging not allowed|
|0x34||52||Outgoing calls barred|
|0x35||53||Outgoing calls barred within CUG|
|0x36||54||Incoming calls barred|
|0x37||55||Incoming calls barred within CUG|
|0x38||56||Call waiting not subscribed|
|0x39||57||Bearer capability not authorized|
|0x3A||58||Bearer capability not presently available|
|0x3F||63||Service or option not available, unspecified|
|0x41||65||Bearer service not implemented|
|0x42||66||Channel type not implemented|
|0x43||67||Transit network selection not implemented|
|0x44||68||Message not implemented|
|0x45||69||Requested facility not implemented|
|0x46||70||Only restricted digital information bearer capability is available|
|0x4F||79||Service or option not implemented, unspecified|
|0x51||81||Invalid call reference value|
|0x52||82||Identified channel does not exist|
|0x53||83||A suspended call exists, but this call identity does not|
|0x54||84||Call identity in use|
|0x55||85||No call suspended|
|0x56||86||Call having the requested call identity has been cleared|
|0x57||87||Called user not member of CUG|
|0x59||89||Non-existent abbreviated address entry|
|0x5A||90||Destination address missing, and direct call not subscribed|
|0x5B||91||Invalid transit network selection (national use)|
|0x5C||92||Invalid facility parameter 93 Mandatory information element is missing|
|0x5D||93||Message type non-existent or not implemented|
|0x5F||95||Invalid message, unspecified|
|0x60||96||Mandatory information element is missing|
|0x61||97||Message type non-existent or not implemented|
|0x62||98||Message not compatible with call state or message type non-existent or not implemented|
|0x63||99||Information element nonexistent or not implemented|
|0x64||100||Invalid information element contents|
|0x65||101||Message not compatible with call state|
|0x66||102||Recovery on timer expiry|
|0x67||103||Parameter non-existent or not implemented – passed on|
|0x6F||111||Protocol error, unspecified|
|0x80+||128 orhigher||Proprietary diagnostic code (not necessarily bad). Typically used to pass proprietary control or maintenance messages between multiplexers.|
Q34, What to do when Telephony Cards are not Recognized
NOTE: You may need to comment out all other includes if you run into issues and make sure only chan_dahdi.conf and dahdi-channels.conf are included