[asterisk-users] Best Current Release for Long Term Use

[Danny Nicholas]

There are actually 793 items, so I guess a lot of folks are using it.  The
bug number for #1 is 14935.  I developed a similar app that was working
great in the 1.4.21/Zaptel environment, but is now iffy at best in the
1.4.25/1.6 environment.

https://issues.asterisk.org/view.php?id=14935

I'll tune my asterisk for 2-3 days, then turn my users loose and within 2-3
days have to shut down again because some customer can't talk to my boss
from his cell or a landline.  I don't have $2K and 3 days to go to
Huntsville to figure this out.


-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Tzafrir Cohen
Sent: Thursday, May 28, 2009 2:22 PM
To: asterisk-users at lists.digium.com
Subject: Re: [asterisk-users] Best Current Release for Long Term Use

On Thu, May 28, 2009 at 01:32:58PM -0500, Danny Nicholas wrote:
> There are over 100 open items on the Digium board related to DAHDI. 

Which is because people use it. I wonder which of those are actually
regressions from before the DAHDI times (not that others are less
serious. But this is what i relevant to your argument)

> I'm
> sure quite a few are "chair-to-keyboard" issues, but here are two real
ones:
> 1. DAHDI will not look for a connection when dialing, so if I make a call
> and play a file, X percent of the file plays before the person actually
(if
> ever) answers the phone.

Bug number?

I can think of a number of reasons why such a thing should happen (for
good reasons).

> 2. DAHDI (IMO and IME) is more difficult to tune than Zaptel.

Please be more specific. Any examples?

The only usability regression I can think of is that you have to
explicitly add 'echocancel' lines to /etc/dahdi/system.conf for every
channel, whereas in Zaptel there was one hardwired EC. I tried to give a
reasonable workaround for those who use dahdi_genconf .

> 
> I'm certain that DAHDI will be solid and great in a few years; It just
> doesn't seem to be yet.
> 
> Zaptel isn't the "end all" either; I upgraded to 1.4.25-rc1 because I
> couldn't get zaptel to tune sufficiently on 1.4.21.2.  We use POTS for our
> outgoing service and haven't gotten satisfactory results with DAHDI or
> Zaptel on TDM400 and TDM410.

Asterisk 1.4.x should work well with Zaptel. If it doesn't, it's a bug.
At the moment I can't think of any such issues in 1.4.25-rc1 or later.
Could you please be more specific?

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

_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users