asterisk into unstable

[Tzafrir Cohen]

On Mon, Feb 16, 2009 at 09:59:00PM +1100, Mark Purcell wrote:
> On Monday 16 February 2009 20:57:16 Tzafrir Cohen wrote:
> > So how do we move forward with getting Asterisk into Unstable?
> >
> > The newer libpri and the DAHDI packages are prerequirements.
> 
> Lets upload these first especially as dahdi needs to clear NEW as well.
> We are allowed to break unstable at the moment, but we have been asked to 
> coordinate soname bumps with debian-release.
> 
> Are we going to depreciate bristuff while we work on asterisk 1.6?

Yes. Specifically: forward-porting the libpri patch to libpri >= 1.4.4
is quite non-trivial and I don't see anybody doing this. (Forward porting
the Asterisk part should not be a major problem, as I have already done
this for 1.4.22)

Thus we are left with the functionality of Asterisk 1.6.0 and DAHDI .
Which basically means the following changes:

* The Zaptel driver cwian was not ported to DAHDI. 
  Doing this port should not be a major issue if someone actually comes
  up with such hardware on a rebootable machine.

* ztgsm was likewise not ported. But also:

* We never actually got to make the ztgsm card work in our package .
  This requires packaging libgsmat and forward-porting the bristuff-gsm
  patch to 1.6 . I figure it is doable but takes some work.

* qozap was not ported to DAHDI. However with a bit of extra effort
  those cards should be supported in DAHDI with the driver wcb4xxp:
  http://bugs.digium.com/view.php?id=13897

* Libpri does not support (yet?) NT/ptmp . 

* Hopefully there are no other major regressions in the ISDN stack.


> 
> > 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,
> 
> asterisk 1.4 is still available so we can work around 1.6 to converge on a 
> working solution.
> 
> > and hence it may be useful
> > to add the following two subpackages:
>  [...]
> > Both packages will provide "asterisk-timing" and the main asterisk
> > package will depend on:
> >
> >   asterisk-dahdi | asterisk-timing
> 
> Sounds like a reasonable break out.
> 
> In svn I suppose we should also make asterisk/branches/lenny	and then merge 
> asterisk/branches/experimental into trunk.

So continue with 1.6.0 (1.6.0.5) or 1.6.1 (1.6.1-rc1)?

The separate timing modules are new feature of 1.6.1 .

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