login | register
Sat 17 of May, 2008 [08:55 UTC]

voip-info.org

Navigation
Today's Deals
Recently Visited Pages
Search with Google
Search this site with Google. Results may not include recent changes.
 
Google Ads
Last Changes
Shoutbox
  • Juan Ortega, Thu 15 of May, 2008 [10:33 UTC]: Hi everybody, I'm Juan, an ITCom student, and I need to know what basic elements I need to create a VoIP network. Can anybody helpme, please?,Thank you very much
  • gineta, Wed 14 of May, 2008 [03:58 UTC]: any here not fine the configuration of firewall juniper -screem for VOIP asterisk????
  • Anoop Prabhakaran, Tue 13 of May, 2008 [12:16 UTC]: I am developing Asterisk IVR, Whenever i make a internation call to the IVR system, the DTMF is not getting detected properly, this happens only for the first time, second call onwards system works fine. why this is happening
  • joe, Mon 12 of May, 2008 [04:27 UTC]: Is there an opensource browser based softphone, or a system like Busta where everything is not manages through their website?
  • Nick Barnes, Fri 09 of May, 2008 [11:36 UTC]: Christopher - yesterday I tried an Asterisk install on a CentOS 5.1 box with stock GUI and it all worked fine. Sorry I can't help.
  • aero, Fri 09 of May, 2008 [08:20 UTC]: can someone help me out on this, i tried to play some sound files on my asterisk box and this is the error message i got. WARNING[4429]: format_wav.c:169 check_header: Unexpected freqency 22050 May 8 11:17:39 WARNING[4433]: codec_gsm.c:194 gsmtolin_fra
  • Christopher Faust, Thu 08 of May, 2008 [14:15 UTC]: I beleive that I may have to change something in the xserver configuration. Please advise
  • Christopher Faust, Thu 08 of May, 2008 [14:14 UTC]: Everything was perfect. In the bios I have increased the memory allocated Still receive input not supported on my display.
  • Christopher Faust, Thu 08 of May, 2008 [14:13 UTC]: This would not be my main box. I am doing some testing to see if I can install zaptel and asterisk 1.4 on a full centos 5.1 box with development software Its bizzare, because before I went through the asterisk and zaptel installation everything was perfe
  • Nick Barnes, Thu 08 of May, 2008 [13:44 UTC]: Christopher - I can't see any way in which an Asterisk installation would muck your GUI, but remember that it is advised not to use a GUI on an Asterisk box anyway.
Server Stats
  • Execution time: 0.97s
  • Memory usage: 2.39MB
  • Database queries: 38
  • GZIP: Disabled
  • Server load: 0.66

Asterisk hardware

Page Contents

This page is a reference page of hardware that is known to work with Asterisk.
For finding out how to determine the hardware sizing needs of your Asterisk system see Asterisk dimensioning.

For phones to use with Asterisk, including VoIP phones (both hard and soft phones) and Analog Telephone Adapters, see Asterisk phones.

PSTN Interface cards (analog, ISDN-PRI and R2/MFC)


This section contains hardware for connecting analog or digital phone lines from the Public Switched Telephone Network to your Asterisk server.

Atcom

  • IP04: 4 ports fxo/fxs asterisk embedded ippbx
  • IP08: 8 ports fxo/fxs asterisk embededded ippbx
  • AX-100P: one fxo pci card, compatible digium x100p
  • AX-400P: Suitable for SOHO PBX application.
  • AX-1600P: 16 ports anolog pci board
  • AX-4E: Same as Tormenta2 and Digium's E400P cards
  • AX-4T: Same as Tormenta2 and Digium's E400P cards
  • AX-4S: 4 Basic Rate Interface ports (I.421) for TE and NT mode
  • AX-1E: One PRI port 30 channels

beroNet

  • BN2S0: 2xS0/2xBRI (TE/NT) PCI interface card for Asterisk
  • BN4S0: 4xS0/4xBRI (TE/NT) PCI interface card for Asterisk
  • BN8S0: 8xS0/8xBRI (TE/NT) PCI interface card for Asterisk
  • BN2S0 miniPCI: 2xS0/2xBRI (TE/NT) miniPCI interface card for Asterisk
  • BN4S0 miniPCI: 4xS0/4xBRI (TE/NT) miniPCI interface card for Asterisk
  • BN1E1: 1xE1/1xPRI PCI interface card for Asterisk
  • BN2E1: 2xE1/2xPRI PCI interface card for Asterisk
  • BN1E1 miniPCI: 1xE1/1xPRI miniPCI interface card for Asterisk
  • BN1GSM: 1xGSM (2 SIM card holders) interface card for Astersik
  • BN2GSM: 2xGSM (4 SIM card holders) interface card for Astersik
  • BN3GSM: 3xGSM (6 SIM card holders) interface card for Astersik

BroadTel


ChinaRoby

  • TDM400P Modular FXO/FXS Analog PCI

Digium


Digivoice

  • VB0408PCI - 4/8 FXO, with built in aLaw, uLaw and GSM codec, Echo Cancelation into DSP
  • VB0404FX - 4 FXS, with built in aLaw, uLaw and GSM codec, Echo Cancelation into DSP
  • VB6060PCI - 2 E1, with built in aLaw, uLaw and GSM codec, Echo Cancelation and R2D/MFC protocol into DSP
  • VB3030PCI - 1 E1, with built in aLaw, uLaw and GSM codec, Echo Cancelation and R2D/MFC protocol into DSP

DMLink


Dialogic Eicon

The Diva Server V-Series provides a dedicated range of telephony adapters that provide rich media processing capabilities for enabling voice, speech and conferencing applications. For an explanation of the different cards please see this document



Magiclink


OpenVox


Parabel


PBX Hardware (PhonicEQ Inc) - The creator of Tormenta III card

PBX Hardware - Affordable Quad/Double/Single T1/E1/J1 and BRI/Analog PCI cards and more! -> http://pbxhardware.com
More discounts for resellers/distributors - contact the store via email

Pika Technologies Inc



Pika offers a variety of analog and digital boards to support the Asterisk environment.

For information on the Digital Gateway T1/E1 Boards, Pika Low Density Analog Boards and the Pika High Density Analog Boards

For the latest driver downloads


Redfone

  • REDFONE Communications Quad or Dual T1/E1 to Ethernet bridge.
    • Solid-state appliance designed for deploying high-availability, redundant Asterisk clusters.

Rhino Equipment Corp

  • Analog PCI Plug-In telephony cards
    • R4FXO-EC - 4 Analog Lines PCI Plug-In Card with on-board Echo Cancellation
    • R24FXO-EC - 24 Port FXO PCI Plug-In Card with on-board Echo Cancellation
    • R24FXS-EC - 24 Port FXS PCI Plug-In Card with on-board Echo Cancellation
    • R8FXX-EC - 8 Analog Channels Modular PCI Plug-In Card with on-board Echo Cancellation
    • R24FXX-EC - 24 Analog Channels Modular PCI Plug-In Card with on-board Echo Cancellation
    • Dual FXO Module - Dual FXO Module for R8FXX & R24FXX Modular Cards
    • Dual FXS Module - Dual FXS Module for R8FXX & R24FXX Modular Cards
  • Digital PCI cards
    • R1T1 - 1 Port E1/T1/J1 Digital Telephony PCI Plug-In Card
    • R1T1-EC - 1 Port E1/T1/J1 Digital Telephony PCI Plug-In Card With Echo Clear
    • R2T1 - 2 Port E1/T1/J1 Digital Telephony PCI Plug-In Card
    • R2T1-e - 2 Port E1/T1/J1 Digital Telephony PCI Express Plug-In Card
    • R4T1 - 4 Port E1/T1/J1 Digital Telephony PCI Plug-In Card
    • R4T1-e - 4 Port E1/T1/J1 Digital Telephony PCI Express Plug-In Card
    • Echo Cancellation Module(EU) - Echo Cancellation Module for all Digital PCI Plug-In Cards
  • Channel Banks
  • Ceros - Ceros telephony system
  • Ceros-Mini - Ceros Mini 1U telephony system

Sangoma cards

  • A101 One port T1/E1 card
  • A102 Two port T1/E1 card
  • A104 Four port T1/E1 card PCIx and PCI Express
  • A104d Four port T1/E1 card PCIx and PCI Express with 128ms telco grade hardware echo canceller
  • A108 Eight Port T1/E1 card PCIx and PCI Express
  • A108d Eight Port T1/E1 card card PCIx and PCI Express with 128ms telco grade hardware echo canceller
  • A200 expandable 2 to 24 analog ports of FXO and or FXS
  • A200d expandable 2 to 24 analog ports of FXO and or FXS with 128ms telco grade hardware echo canceller
  • A400 expandable 2 to 48 analog ports of FXO and or FXS

SIPbase

External solution for connecting every VoIP-PBX with ISDN-Network (BRI or PRI). 100% reliable, no hardware and software conflicts and very easy to setup.



Varion

Zapata Telephony T1 and E1 cards: http://www.govarion.com

Voicetronix cards


Xorcom

Asterisk Channel Banks and iPBXs
  • Astribank-8 - The first channel bank designed for Asterisk - 8 FXS/FXO ports.
  • Astribank-16 - The first channel bank designed for Asterisk - 16 FXS/FXO ports.
  • Astribank-32 - The first channel bank designed for Asterisk - 32 FXS/FXO ports.
  • Astribank-BRI - ISDN BRI channel banks - 2, 4 and 8 port models. Each port NT/TE by user's definition.
  • XR1000 Asterisk Appliance - with FXS, FXO and BRI ISDN ports


X100P.com

Single port FXO Card
  • Authentic X100P Special Edition One port FXO PCI Interface for Digium Asterisk
  • Special Edition: 3.3+5v PCI, Global Line Compat. +More!
  • DTMF Detection and Voice Quality Tested under Asterisk
  • All Product comes with 1 Year Limited Warranty

Voxzone.com

Single port FXO Card

Yeastar

  • TDM800 8 Ports FXS/FXO PCI Analog Interface Card with Intuitive LED. Red light for FXO module and Green light for FXS module.

ZapMicro

  • Analog Interface PCI cards
    • ZMA100P - Single port analog interface card
    • ZMA400P - Quad port analog interface card series: With SoftEcho Echo Cancellation Software
    • ZMA800P - Octal port analog interface card series: With SoftEcho Echo Cancellation Software
  • Digital Interface PCI Cards
    • ZMD110P - Single port Digital interface E1/T1 card
  • Analog Modules

X100P clone cards.

These are voice WinMODEMs marked with Intel 537, Ambient MD3200, or Motorola 62802 chipsets. These cards install and behaves exactly like a Digium Wildcard X101P card. (There are problems with intel 537EP & FA82537EP chipsets, but the 537PU & 537PG should work.) OEM X100P "clone" cards are sold based upon this soft modem chipset. People report very mixed results. Most start their Asterisk learning with these very inexpensive cards.

There are some possible Caller ID issues: Getting the following checksum error on the CLI, but the information is still passed correctly.
      • NOTICE[-1252213840]: callerid.c:238 callerid_feed: Caller*ID failed checksum
Actual Caller ID problems are confirmed on one particular Motorola based card.


















ISDN-BRI Interface cards (can be used as PSTN cards, or as terminal equipment)

  • ATCOM
    • AX-4E:Same as Tormenta2 and Digium's E400P cards
    • AX-4T:Same as Tormenta2 and Digium's E400P cards
    • AX-4S:4 Basic Rate Interface ports (I.421) for TE and NT mode
    • AX-1E:One PRI port 30 channels


    • Diva Server provides a set of robust all-in-one communication adapters for the integration of multiple applications, including Fax, Unified Messaging and Voice - all on a common hardware platform. For an explanation of the different cards please see this document







PC/Server Motherboards


While Asterisk will run on many different systems, the limitations will be determined by what type of interface cards you choose for connecting to phone lines or phones.

PCI Slot Requirements: Carefully check what the requirements are for any PCI card you select in terms of PCI slot type, 5 volt vs. 3.3V, 32 bit vs. 64 bit, 33 Mhz or higher. The X100P clone cards require 5 volts and won't work in motherboards that can't supply 5 volts. The cards should be keyed so they will only fit in 5V slots, but at least some of the clone cards have the notch in the PCI connector that will allow them to fit into 3.3V slots. Symptoms of putting a 5V card in a 3.3V only slot is that the system won't power up.

Pictorial guides to identifying types of PCI slots:

The DIGIUM TE410 PRI card, requires a motherboard with a 64bit 3.3v PCI slot. Given the bandwidth requirements, it would be better to have a 133Mhz slot if available.

The newer DIGIUM TE405P PRI card uses the more commonly available 32bit 5 volt PCI slot, so you have a wider selection of motherboards for this card. Other than the PCI slot type, this board is virtually identical to the TE410P.

Note: Some cards like the TDM400's are 3.3V cards, but to make up for their higher power requirements, they require an available hard drive power connector in order to get 5V or 12V. If all of your connectors are in use you may require a Y (splitter) cable.

PCI interrupts: A lot of issues are reported with MB's that share interrupts on a single PCI slot, with the Digium hardware. Better quality MB's allow BIOS specifcation of the IRQ to a PCI slot to avoid this issue.

See also: Asterisk hardware interrupts

You can use the command "cat /proc/interrupts" to see the interrupt allocations and possible conflicts.
The command "lspci -bv" can also provide additional information regarding IRQs.

If you find the interrupts are not shared, but hear ticking noises in your digium hardware anyhow, I've discovered the IDE harddisk write can be the cause. Digium support susguested the following command. $ hdparm -u1 /dev/hda This command sets "get/set unmaskirq flag (0/1)". By default the disk will ask for interrupt priority to write to the disk. Changing this setting hardly affects performance, but the sound problems go away.

The DIGIUM T100P has issues with at least one chipset (the SiS 740) with shared-memory onboard video. If you're trying to run a T100P or TE4xx on a board with shared-memory video, and the zaptel driver locks up the computer soon after you configure the spans with ztcfg, try adding a PCI or AGP video card, then go into the BIOS setup and disable the onboard video. The theory is that the T100P is too "busy" a device for the 740 to cope with, and causes the chipset to lock up. Machines that use dedicated-memory video (where the video chip has its own memory, just as if it were on a card) are apparently not affected. If you have this problem with another shared-memory chipset, please note it here.

There has also been trouble with the Tyan S2466 Athlon MP motherboard. When running more than two T400P boards, the system will lock up soon after starting the zaptel drivers. No workaround has been found.

Asterisk / Trixbox Hardware Compatibilty Forum



    • Supermicro
      • Supermicro 7043A-ib, 614H-Xi, kernel 2.6.9 uniprocessor and Supermicro 6014H-X8 kernel 2.6.9 SMP - T100P, Sangoma A101, 102, and A104
      • Supermicro PDSME, Intel E7230 chipset, Dual LAN, 2x 64-bit 133MHz PCI-X, 2x 64-bit 100MHz PCI-X, Sangoma A200D, 3ware 8006-2LP SATA RAID 1, kernel 2.6.9 SMP
    • Unknown
      • 7500i Systems
      • Crystal CS100 with single PIV SBC running kernel 2.6 and a single T100P - Asterisk 1.0 stable







Complete systems

IBM NEBS compliant Blade Server for Telco applications.

  • Have successfully run multiple Asterisks with HA fail over. (without dropping connected SIP calls)
  • Up to 4 processors x 8 Blades (32 3GB Xeon processors)
  • Up to 8 GB per Blade.
  • 2 1 gigabit builtin switches.
  • Redundant power supplies
  • Redundant Managent Modules

Sun Netra T1 AC200


Specs:
  • Around $150 - $300 on eBay for maxed out configurations.
  • 500 Mhz UltraSparc IIi.
  • Usually 512MB - 1GB of RAM.
  • Usually two 18GB hot swap SCSI drives.
  • One PCI slot.
  • Two 10/100 ethernet ports.
  • Two serial ports, one of which is a "lights out" port and lets you remotely power on and power off the machine.

Positives:
  • NEBS compliant.
  • Lights out management.
  • Great interrupt handling.
  • Surprisingly capable processing power.

Negatives:
  • The Zaptel drivers aren't ported to Solaris (not that I care, but you might).
  • The Zaptel drivers are not ported to mixed 32/64 bit userspace/kernelspace.
  • So you need to either run a 32 bit kernel (and 32 bit userspace) or run a 64 bit userspace (on a 64 bit kernel).


Channel Banks


Cable Info T1, Amp50, Punch Down etc


Paging Systems


GSM and other cellular networks


See also


Created by jpiterak, Last modification by lolo on Fri 09 of May, 2008 [08:22 UTC]

Comments

Comments Filter

OpenVox B200P/B400P

by james.zhu on Thursday 12 of July, 2007 [05:28:17 UTC]
OpenVox Provides B200P/B400P。 It supports bristuff-0.3.0-PRE-1y and ly-g version. If you want to more info about B200P/B400P, please go to:openvox.com.cn.

OpenVox B200P/B400P

by james.zhu on Thursday 12 of July, 2007 [05:14:15 UTC]
OpenVox Provides B200P/B400P。 It supports bristuff-0.3.0-PRE-1y and ly-g version. If you want to more info about B200P/B400P, please go to:openvox.com.cn.

Reusing old analog boards

by Jesus on Monday 27 of March, 2006 [10:50:19 UTC]
Hi,

I would like how to know if an analog board is supported by the Zaptel library?
It is a TEI-141 (TEIMA).
It has a DSP from TI (TMS320C3) to hand the phone interfaces, and a PLX chip to control the PCI bus.
It is not mentionned in the Asterisk hardware support, but I guess it is not an exahustive list, I search for hints to support these boards.

TE110P on P4 - 3Ghz machine

by chrisre on Friday 17 of March, 2006 [17:29:23 UTC]
Just spent over 5 weeks trying to get a Digium TE110P working in a new self built machine P4 3Ghz 630 in a socket LGA775, no other hardware besides Digium card. Bought 2 TE110P cards (1 as a spare) and tried them both (not at the same time) in an Intel 915 motherboad, a Abit AA8 DuraMax board (925 chipset) and SuperMicro P8SCT (Intel E7221 chipset) motherboard. On all boards we suffered interrupt handling issues resulting in HDLC framing errors against our E1 line and dropped calls. We tried 2.6.9 kernels and 2.6.15 kernels, disabling SATA, Hyperthreading, USB, Soundcards, serial ports, parallel ports, apic ioapic, integrated network cards, PCI 3com and realtek network cards. All resulted in the errors. Even Digium support were unable to solve the problem with remote access to the machine.<br><br>

Returned the cards and bought a Sangoma A101 card, re-enabled everything in the machine (SATA, USB, Sound, HyperThreading, Network), installed the card and 30 mins later I was up and running. Have yet to have a single dropped call or any sort of HDLC error with the line, after 1000 minutes spread over 400 calls.<br><br>

According to the person at Digium the 2 and 4 port cards use a different chipset on the card so are more reliable in these situations but as these are more expensive and we only needed 1 channel we went for the Sangoma single line card instead.

Re: TDM400 on Kernel 2.6 w/Debian 3.1 (sarge)

by Scagnetti on Monday 04 of April, 2005 [17:14:13 UTC]
The two ring delay is caused by the CallerID detection. The caller info is sent just before the 2nd ring so Asterisk has to wait for it.

Nforce AMD Athlon Mobo very bad experience

by al3x on Friday 25 of February, 2005 [18:08:54 UTC]
(:twisted:)
From the painful experience - avoid nForce chipset MB - just  wasted a week trying to make TE110XP work on one of these. After we put the card into old Celeron 375/Intel 440BX it started working like a charm - no echo/lag at all.
Edit

Bad experiences with X100P/X101P

by Anonymous on Tuesday 11 of January, 2005 [21:22:35 UTC]
We use a number of these for testing. They tend to have lots of echo issues, and many of the cards started out or degraded to very bad, with horrible static on the line. Swap in a new one and it goes away.

I contacted Digium customer service regarding the line quality, and just got a canned response that they do not support the X100P any more.
Edit

TDM400 on Kernel 2.6 w/Debian 3.1 (sarge)

by Anonymous on Sunday 12 of December, 2004 [04:54:15 UTC]
Does exactly what it says on the tin, and Linux Kernel 2.6 support seems to work well. A great example of how a hardware manufacturer like Digium can work with the Linux community and everyone wins.

If you're dealing with more than a couple of phone lines, this card is much more elegant than dealing with modems and ALSA, especially with motherboards skimping on the number of PCI slots these days.

Disclaimer: Have only used this card with FXO modules loaded (I.E., to deal with PSTN phone lines rather than FXS modules which let you use analogue phones with Asterisk).

Caller ID works well.

Some tips for working with Asterisk on Debian 3.1/Sarge with Kernel 2.6:
- Check that your TDM400 is not sharing any IRQs - use cat /proc/interrupts to check (you'll need to have the wctdm driver loaded).
- You'll need the zaptel-source package to compile the (wctdm, wcfxo, wcfxs) drivers for your running kernel. As long as you're running a stock Debian kernel, this should be quite easy. Hint: you need the EXACT kernel-headers-* package to match your current running kernel. If you get "wrong magic" errors when trying to insmod the wctdm driver, then you're compiling with the wrong kernel-headers directory symlinked to /usr/src/linux.
- If you run 'make linux26' (as instructed for those running 2.6 kernels) to build the zaptel drivers in /usr/src/modules/zaptel, 'make install', and then try to insmod them only to find that Asterisk cannot open the zap channels anyway - try doing 'make' instead (without the 'linux26' bit). I'm running kernel-image-2.6.8-1-386 and for some reason a dist-upgrade/kernel-upgrade/reboot the other day now makes my zaptel modules useless if I do 'make linux26'. Odd.
- Don't forget to insmod wcfxo and wcfxs. If you have only FXO modules you'll need FXS signalling and hence the wcfxs module; and vice versa. It's harmless to just do both even if you only have one type of module installed on your card.
- Don't forget to install the zaptel package for the userland tools, which includes the ztcfg utility.
- It seems that with Kernel 2.6 at least (perhaps 2.4 too but I haven't tried), there is an issue where Asterisk can't open the zaptel channels when launched through the init.d scripts as the asterisk user (kept getting "permission denied" on /dev/zap/* even though permissions were all good). The work-around seems to be: make sure ztcfg is run as root before asterisk is started. I ended up placing a one-liner script in init.d that was simply "ztcfg". Don't forget to use update-rc.d to setup the rc.x symlinks and give it a sequence number so that it is run before asterisk on bootup.
- Don't forget to use signalling=fxs_ks in your zapata.conf so that your FXO module can detect remote end hangup reliably.
- Want to be able to pickup a line even if it isn't ringing? Perhaps it's just me but I got confused thinking that the zapbarge Asterisk command would be what I wanted. Of course, the solution is much simpler.

Below are some lines out of my extensions.conf that allow anyone on a SIP phone (or other) to pickup a PSTN line by dialing *X, where X is the line number (1-3). This is useful for when you still have analogue phones sharing the same lines that are going into your TDM400 card, and you want to be able to pickup a line that has already been answered with an analogue phone.

[zaplines]
exten =_ *1,1,Dial(Zap/1/)
exten =_ *2,1,Dial(Zap/2/)
exten =_ *3,1,Dial(Zap/3/)

My only complaint about this card with Asterisk is that my SIP phones don't start ringing for about two rings on the Zap channel, but there's probably an option somewhere to fix that.

Motherboard II

by meowmeow64 on Saturday 28 of August, 2004 [04:08:56 UTC]
I had intel serverboard and problem with interrupts and irq misses horrendosuly high and it had static noise and echo. I was using redhat 9 (2.4 kernel which does not support acpi) then.
I upgraded Fedora2 (2.6 kernel which does support acpi) with most recent kernel and all my interrupts releated problem is gone(no more high irq misses and sharing issues). If you have similar problem and your biose does support acpi and you are running linux without acpi support.
Then, try to upgrade your kernel with acpi support.
I think fedora1 also supports acip but I am not sure.

my2cents here.

Motherboad

by meowmeow64 on Saturday 21 of August, 2004 [04:47:35 UTC]
if you want to install multiple digium cards on machine, avoid intel mobo.
IRQ sharing and interrupt becomes issue.
also stay away from any integrated video mobo stuff.
go with mobo which you know you can configure irq stuff at the bios(supermicro etc.)

Please update this page with new information, just login and click on the "Edit" or "Add Comment" button above. Get a free login here: Register Thanks! - support@voip-info.org

Page Changes | Comments

Sponsored by:
Terms of Service Privacy Policy
© 2003-2008 VOIP-Info.org LLC

Powered by bitweaver