similar to: [asterisk-dev] Zaptel 1.2.4 Released!

The Asterisk/Zaptel development team is pleased to announce the release of Zaptel 1.2.4. This release contains a number of bug fixes, along some with new functionality: * The driver for the Xorcom Astribank has been incorporated into this distribution. Xorcom will provide primary support and driver maintenance for customers using this product. * The driver for the Digium Wildcard TDM2400P has

The Asterisk/Zaptel development team is pleased to announce the release of Zaptel 1.2.4. This release contains a number of bug fixes, along some with new functionality: * The driver for the Xorcom Astribank has been incorporated into this distribution. Xorcom will provide primary support and driver maintenance for customers using this product. * The driver for the Digium Wildcard TDM2400P has

The Asterisk.org development team has announced the release of Zaptel versions 1.2.20 and 1.4.5. These releases are maintenance releases that fix various known issues. See the ChangeLog included in the releases for a full list of changes. The ChangeLogs are also available separately on the ftp site. This release also contains support for Digium's new 32 channel hardware echo canceler

The Asterisk.org development team has announced the release of Zaptel versions 1.2.20 and 1.4.5. These releases are maintenance releases that fix various known issues. See the ChangeLog included in the releases for a full list of changes. The ChangeLogs are also available separately on the ftp site. This release also contains support for Digium's new 32 channel hardware echo canceler

Does anyone know what date this memory leak was introduced and/or how to check source code for it? I am running a pre-1.2 CVS head version and would like to know if the potential problem exists. > -----Original Message----- > From: asterisk-announce-bounces@lists.digium.com [mailto:asterisk- > announce-bounces@lists.digium.com] On Behalf Of The Asterisk Development > Team > Sent:

Tzafrir, > cross-posting to asterisk-users and to asterisk-dev > is not a good idea. > You should know that by now, as you have been told > that numerous time. I cross-posting because nobody answer ! I think some people are able to answer this question ? Please, don't tell me people here are not here to serve you . > Your question, as phrased, was probably relevant to >

Hello, I am trying to update to dahdi 2.2.1. But somehow the xorcom (2BRI) device does not want to work. I pasted below the information I have. pbx at loicvoip1:~# /usr/share/dahdi/xpp_fxloader reset pbx at loicvoip1:~# /usr/share/dahdi/xpp_fxloader usb 'xpp_fxloader'[4937]: --------- FIRMWARE LOADING: (usb) [1 devices] ..Got all 1 devices 'xpp_fxloader'[5003]: ---------

Tzafrir, > cross-posting to asterisk-users and to asterisk-dev > is not a good idea. > You should know that by now, as you have been told > that numerous time. I cross-posting because nobody answer ! I think some people are able to answer this question ? Please, don't tell me people here are not here to serve you . > Your question, as phrased, was probably relevant to >

Hi Someone complained in #asterisk-gui that the Zaptel hardware detection did not work. It seems that zapscan.bin did not work properly, as no /etc/asterisk/zapscan.conf was generated. Solution: detect zaptel hardware with genzaptelconf, and generate zapscan.conf from it. genzaptelconf grep '^fx[os][kl]s=' /etc/zaptel.conf \ | sed 's/\(fx[os]\)..=\(.*\)/[\2]\nport=\1\n/'

Asterisk 1.2.4 and Zaptel 1.2.3 have been released! This update of Asterisk includes a fix for a significant memory leak in the expression parser that is present in all previous releases of Asterisk 1.2. This version of Zaptel includes support for the new generation of VPM100M echo cancellation modules from Digium. For further information about all changes that have been made, consult the

Asterisk 1.2.4 and Zaptel 1.2.3 have been released! This update of Asterisk includes a fix for a significant memory leak in the expression parser that is present in all previous releases of Asterisk 1.2. This version of Zaptel includes support for the new generation of VPM100M echo cancellation modules from Digium. For further information about all changes that have been made, consult the

Hi All I've got an asterisk system, using a couple of Xorcom Astribanks to provide FXS ports. (I'm using the zaptel 1.2 branch, if that matters) I've noticed that the ringing volume is a lot louder than on our old phone system, and people are starting to complain it's too loud. (This is the noise the phone makes when it rings, not the noise in your handset when you ring

The Asterisk and Zaptel development teams have released Zaptel version 1.4.1. This release contains a number of new features, along with some minor updates required for compatibility with Asterisk 1.4.2. The new features include: - Support for the Digium Wildcard TE120P T1/E1/J1 card - Support for the Digium Wildcard TDM800P analog card - Support for the Digium Wildcard TC400B transcoder card -

The Asterisk and Zaptel development teams have released Zaptel version 1.4.1. This release contains a number of new features, along with some minor updates required for compatibility with Asterisk 1.4.2. The new features include: - Support for the Digium Wildcard TE120P T1/E1/J1 card - Support for the Digium Wildcard TDM800P analog card - Support for the Digium Wildcard TC400B transcoder card -

The Asterisk development team is pleased to announce the release of Zaptel 1.2.13. This release contains a large number of bug fixes, an important performance improvement for most Digium cards, and support for new Digium hardware and some significant improvements in the XPP driver for Xorcom's Astribank hardware. In detail: * A modification was made to the drivers for all Digium PCI cards

The Asterisk development team is pleased to announce the release of Zaptel 1.2.13. This release contains a large number of bug fixes, an important performance improvement for most Digium cards, and support for new Digium hardware and some significant improvements in the XPP driver for Xorcom's Astribank hardware. In detail: * A modification was made to the drivers for all Digium PCI cards

, address 2 Dec 30 21:42:08 wedekindpbx1 kernel: [ 3746.344611] ERR-xpp_usb: XBUS-00: x= usb_listen: usb_submit_urb failed: -19 Dec 30 21:42:08 wedekindpbx1 kernel: [ 3746.353325] INFO-xpp: XBUS-00: [] D= isconnecting Dec 30 21:42:08 wedekindpbx1 kernel: [ 3746.353373] Zaptel: Master changed = to XBUS-00/XPD-01 Dec 30 21:42:08 wedekindpbx1 kernel: [ 3746.353382] Zaptel: Master changed = to

Hello, I've one astribank with 8 FXO unit and 8 pstn lines connected to the astribank. When I receive calls on my ipphone I get always Unknown callerid. It's is possible to receive the callerid from the lines on the astribank unit? This is my config: [channels] language=es context=from-zaptel signalling=fxs_ks ;rxwink=300 usecallerid=yes callerid=asreceived ;cidsignalling=bell

The Asterisk Development Team is pleased to announce the release of Zaptel 1.2.12. This release contains a number of updates: - compatibility with Linux kernel 2.6.19 - bug fixes to the Xorcom Astribank driver (XPP) - various other bug fixes Thanks for supporting Asterisk and Zaptel!

The Asterisk Development Team is pleased to announce the release of Zaptel 1.2.12. This release contains a number of updates: - compatibility with Linux kernel 2.6.19 - bug fixes to the Xorcom Astribank driver (XPP) - various other bug fixes Thanks for supporting Asterisk and Zaptel!