asterisk users - Jul 2007 - Zaptel 1.2.19 and 1.4.4 released

The Asterisk.org development team has announced the release of Zaptel
versions 1.2.18 and 1.4.4.  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.

Both releases are available as a tarball as well as a patch against the
previous release.  They are available for download from ftp.digium.com.

Thank you for your support!

On Mon, Jul 16, 2007 at 01:51:52PM -0500, The Asterisk Development Team
wrote:
> The Asterisk.org development team has announced the release of Zaptel
> versions 1.2.18 and 1.4.4.  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.
> 
> Both releases are available as a tarball as well as a patch against the
> previous release.  They are available for download from ftp.digium.com.
One thing I'd like to ask your help in:

If you install from xpp/utils (in 1.4 this is enabled by default, and
generally condtioned on building the driver xpp, on 1.2 it requires
runningan explicit 'make -C xpp/utils install'), you'll now also get
the
zaptel-perl modules and utilities.

You can also run the directly from the Zaptel source distribution
without installing anything. For instance:

  ./xpp/utils/lszaptel
  ./xpp/utils/zaptel_hardware

They all include documentation in perldoc format:

  perldoc xpp/utils/lszaptel

I would appreciate it if you could take the time to run:

  ./xpp/utils/zaptel_hardware

from an extracted zaptel 1.2.19 / zaptel 1.4.4 tarball or latest SVN,
and report to me if it hasn't found your hardware. Specifically, what
card it is, and what is its PCI ID (from lspci -n).

For PCI cards, Much of the dirty work is done in 
xpp/utils/zconf/Zaptel/Hardware/PCI.pm .

-- 
               Tzafrir Cohen       
icq#16849755                    jabber:tzafrir at jabber.org
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com       
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir

On 7/16/07, The Asterisk Development Team <asteriskteam at digium.com>
wrote:
> 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.
>
Is there any more information available on this change?

2007-07-13 08:22 +0000 [r2733-2736]  Tzafrir Cohen <tzafrir.cohen at
xorcom.com
>
          * Fix a digit mapping bug with hardware dtmf detection (r4357)

I assume those revision numbers (4xxx) in the changelog are from another SVN
repo - I was trying to figure out what exactly had changed, but the large
number of files changed across 3 revs makes it a bit tough to isolate.

I'm fighting with a DTMF problem right now where directly dialed SIP->Zap
(PRI) calls produce doubled-up DTMF on the other side (not every digit, but
just one causes the remote IVR to go into fits).  The problem first appeared
when we moved from 1.2.x to * 1.4.4/Zaptel 1.4.3.  I haven't had much time
to investigate - it happens whether the SIP agent connected to * is using
inband, rfc2833 or info and across Grandstream, Aastra and Polycom units.

Interestingly, if I send the SIP phone into DISA() pointing at it's own
context, I get no DTMF problems on the remote side.

Thanks

-- 
j.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20070717/942b3873/attachment.htm

James FitzGibbon wrote:
> Is there any more information available on this change?
> 
> 2007-07-13 08:22 +0000 [r2733-2736]  Tzafrir Cohen 
> <tzafrir.cohen at xorcom.com <mailto:tzafrir.cohen at
xorcom.com>>
> 
>           * Fix a digit mapping bug with hardware dtmf detection (r4357)
> 
> I assume those revision numbers (4xxx) in the changelog are from another 
> SVN repo - I was trying to figure out what exactly had changed, but the 
> large number of files changed across 3 revs makes it a bit tough to
isolate.
This change was to the xpp driver for the Astribank.  The revision number is 
from an internal svn server at Xorcom, I think.

-- 
Russell Bryant
Software Engineer
Digium, Inc.