Discussion: Asterisk hardware

Comments Filter

Bluenet PRI Taping box released

Bluenet providers PRI Taping box. It had worked with kinds of PBX, such as Nortel Avaya etc

by bluenet, Wednesday 08 of February, 2012 (06:42:39 UTC)
OpenVox B200P/B400P

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.

by james.zhu, Thursday 12 of July, 2007 (05:28:17 UTC)
OpenVox B200P/B400P

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.

by james.zhu, Thursday 12 of July, 2007 (05:14:15 UTC)
Reusing old analog boards

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.


by Miramon, Monday 27 of March, 2006 (10:50:19 UTC)
TE110P on P4 - 3Ghz machine

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.


by chrisre, Friday 17 of March, 2006 (17:29:23 UTC)
Re: TDM400 on Kernel 2.6 w/Debian 3.1 (sarge)

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.

by Scagnetti, Monday 04 of April, 2005 (17:14:13 UTC)
Nforce AMD Athlon Mobo very bad experience

(: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.

by al3x, Friday 25 of February, 2005 (18:08:54 UTC)
Bad experiences with X100P/X101P

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.

by , Tuesday 11 of January, 2005 (21:22:35 UTC)
TDM400 on Kernel 2.6 w/Debian 3.1 (sarge)

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.

by , Sunday 12 of December, 2004 (04:54:15 UTC)
Motherboard II

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.

by meowmeow64, Saturday 28 of August, 2004 (04:08:56 UTC)