similar to: Zaptel 1.2.22.1 and 1.4.7.1 released

The Asterisk.org development team has announced the release of Zaptel versions 1.2.22 and 1.4.7. These releases contain (among other things) many bug fixes to the TC400B driver, a bug fix on the wctdm24xxp driver for users with a VPM150M, as well as numerous improvements and fixes to the Xorcom driver suite. The much better performing version of fxotune from 1.4 has now been put into 1.2, so

The Asterisk.org development team has announced the release of Zaptel versions 1.2.22 and 1.4.7. These releases contain (among other things) many bug fixes to the TC400B driver, a bug fix on the wctdm24xxp driver for users with a VPM150M, as well as numerous improvements and fixes to the Xorcom driver suite. The much better performing version of fxotune from 1.4 has now been put into 1.2, so

I am trying to get a zaptel install converted to dahdi. I can get dahdi installed, and the pseudo device even shows up; however, dahdi show channels shows me nothing. There is a TE122 and a TDM800 in there, and neither show up. dahdi show status shows both cards, and dahdi tools show that the cards are there, working, and have no alarms. What am I missing? Michael Munger, dCAP, MCPS, MCNPS,

Hi, I have been trying to get a Wildcard TE122 card running here the last couple of days. libpri and zaptel are all installed and configured to E1 specs. The jumper on the card is on, so configured for E1 (I'm in Norway). When running zttool, I get 'Alarms: RED' on the single card installed. Other information in zttool: Current alarms: Red Alarm Sync source: Internally clocked

Asterisk Project Security Advisory - AST-2007-024 +------------------------------------------------------------------------+ | Product | Zaptel | |--------------------+---------------------------------------------------| | Summary | Potential buffer overflow from command line | | |

Asterisk Project Security Advisory - AST-2007-024 +------------------------------------------------------------------------+ | Product | Zaptel | |--------------------+---------------------------------------------------| | Summary | Potential buffer overflow from command line | | |

Hello ! I am having issues since the upgrade in debian from zaptel 1.4.7.1 to 1.4.8. I did m-a a-i zaptel to upgrade what i still get is: cat /sys/module/zaptel/version 1.4.7.1 It doesn't seem that it wants to load the new driver, any ideas ? Kind regards, Jan -- Jan Prunk <janprunk AT SPAMFREE gmail DOT com> http://www.prunk.si GnuPG: 1024D/00E80E86 77C5 156E 29A4 EB6C 1C4A 5EBA

Hi List! I got this error while upgrading zaptel: make -C firmware hotplug-install DESTDIR= make[1]: Entering directory `/usr/src/zaptel-1.4.7.1/firmware' Attempting to download zaptel-fw-oct6114-064-1.05.01.tar.gz --10:53:09-- http://downloads.digium.com/pub/telephony/firmware/releases/zaptel-fw-oct6114-064-1.05.01.tar.gz Resolving downloads.digium.com... failed: Temporary

---------- Forwarded message ---------- From: Juan Carlos Huerta <juancarloshuerta at gmail.com> Date: 07-abr-2009 13:41 Subject: Re: [asterisk-r2] MFCR2 With Unicall - can unicall affect zaptel commands? To: asterisk-r2 at lists.digium.com Please wirte to asterisk-users at lists.digium.com to get help about this problem. Juan Carlos ~ Lo que no te mata te fortalece ~ On Tue, Apr 7,

Hi, After upgrading to DAHDI 2.4.0 from Zaptel, I noticed a lot of HDLC errors on my console: [Nov 27 01:15:09] NOTICE[2743] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [Nov 27 01:15:09] NOTICE[2743] chan_dahdi.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 These errors prevented calls from being made and received on my PRI spans. This seems

I have recently built a single-T1 Asterisk box using an HP DL120G6 with a Digium TE122 card. I was finding that I was getting missed interrupts on the TE122, causing the driver to report that it was increasing latency. It kept doing this until the T1 did not work reliably. I tried my usual procedure of disabling the USB subsystem in the BIOS (or so I thought), but I found that the USB drivers

hi all i have a te110p installed in my system with a lot of Echo.. i decide to install the oslec echo supressor but when y try to add the module i have this problem. [root at asterisk zaptel-1.4.7.1]# insmod wct1xxp.ko insmod: error inserting 'wct1xxp.ko': -1 Unknown symbol in module [root at asterisk zaptel-1.4.7.1]# some advice? thanks. -- .-

Does anyone know if the TE122 is recognized by any of the 1.2 zaptel drivers? It seems that 1.2.16 knows it not... :) Cheers, j

The Asterisk.org development team has announced the release of Zaptel version 1.4.10.1. This release is a bug fix release for a regression in which the Zaptel udev rules were not installed correctly, as well as a few minor fixes in the xpp drivers. This release is available as a tarball as well as a patch against the previous release. It is available for download from downloads.digium.com.

The Asterisk.org development team has announced the release of Zaptel version 1.4.10.1. This release is a bug fix release for a regression in which the Zaptel udev rules were not installed correctly, as well as a few minor fixes in the xpp drivers. This release is available as a tarball as well as a patch against the previous release. It is available for download from downloads.digium.com.

Hi all... I did some Google searches and didn't find any info on this so I'm posting it here... if this was recently discussed, I apologize for the duplication -- please point me to the appropriate thread. System Description: Supermicro SuperServer 5015M-MF w/ PDSMi Motherboard Intel Pentium 4 2.8 Ghz CPU 2 GB DDR2 Memory Digium T400P 4 Port T1 Card CentOS 5.1 (Final) Kernel:

Hello, there has been a post to this list somewhere arount april which said that it is possible to use a Sangoma BRI A500 card with zaptel and asterisk bristuff. That is, without sangoma_brid and sangoma_mgd daemons and without woomera channels. Could anybody give me a short hint how to configure this? I tried wanpipe-driver + zaptel + asterisk-bristuffed, but I couldn't get zaptel to

Hi, Before I report a bug on http://bugs.digium.com, I would like to know if someone is seeing the same error message. Personally I am not using wctdm24xxp but other modules such as wcte12xp and wctdm. The latter modules load fine and are compiled with pci_register_driver as expected. The only module that seems to require the deprecated function pci_module_init is wctdm24xxp. Is this normal?

This is just a low priority curiosity question because I have a usable workaround. I have Digium card that uses the Zaptel driver (can't get to my home machine right now to get the exact model, but it probably doesn't matter). It's a card with one POTS line and three extension hookups. I'm using Asterisk 1.4 and Zaptel 1.4.7 . One of the extension ports is connected to a modem

Hello Since TDM cards are known for being particular when it comes to motherboards (PCI 2.2, etc.), I was wondering if there is a utility that can check that the Zaptel driver works OK and can tell if the TDM card is compatible? That way, if an FXO module is not reporting an incoming call, we'd know it's because of the Zaptel driver, and not something elsewhere. Are "dmesg",