asterisk into unstable

[Tzafrir Cohen]

On Mon, Feb 16, 2009 at 03:56:40PM +0200, Faidon Liambotis wrote:
> Tzafrir Cohen wrote:
> > As it has to spend time in the new queue anyway, I wonder if it won't be
> > best to go for Asterisk 1.6.1 and experiment with the alternative timing
> > sources. I guess that even if they don't really work well on 1.6.1, they
> > will work well by the time 1.6.2 is released, and hence it may be useful
> > to add the following two subpackages:
> > 
> >   asterisk-dahdi:
> >     chan_dahdi.so
> >     res_timing_dahdi.so
> >     codec_dahdi.so
> >     app_dahdibarge.so
> >     app_dahdiras.so
> >     app_dahdiscan.so
> > 
> >   asterisk-timing-pthread:
> >     res_timing_pthread.so
> > 
> > Both packages will provide "asterisk-timing" and the main asterisk
> > package will depend on:
> > 
> >   asterisk-dahdi | asterisk-timing
> > 
> > As for the moment we'll still default to the DAHDI timing source, until
> > a new one proves useful.
> > 
> > The over-engeneering here is because 1.6.2 has a third timing source:
> > res_timing_timerfd .
> I don't see the point.
> 
> I think we should just enable timerfd and disable all others.

On an Asterisk system with DAHDI hardware, dahdi timing would actually
be better. Though not on a system with dahdi_dummy.

I have DAHDI hardware :-)

> 
> timerfd will be supported in squeeze (and iirc is already supported in
> lenny -- not that it matters much) and it should be mature enough in
> Asterisk by the time squeeze will get released.

Should be supported in Lenny. It is important, as I'm going to stick
with Lenny for a while :-)

> 
> As far as I understand it (and correct me if I'm wrong), the only reason
> there are three different res_timing sources is backwards compatibility,
> which of course doesn't apply for us.
> 
> As for 1.6.1, we could do either of
> a) Backport res_timing_timerfd from 1.6.2,
> b) Package a pre-release of 1.6.2/trunk,
> c) Use timing_pthread until 1.6.2 gets released.

Considering 1.6.1 is not yet released, we're far from that. Squeeze is
far from release as well. Which is why I think that if backporting
res_timing_timerfd is not simple enough, we should just use 1.6.1 for
now. 

-- 
               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