Re: [Astlinux-users] Asterisk 1.4 branch

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Kristian,<br>
<br>
thanks a lot for the clarification. However, I asure I wouldn0t do any
of this if it wasn't necessary.<br>
<br>
You say you are working on zaptel, but I didn't have a problem with it.
I used the latest version (+patch) from Digium's site and it compiled
fine. However, asterisk wouldn't let me compile chan_zap until I
changed the paths in asterisk.mk, I am quite certain of that.<br>
<br>
As for chan_misdn, it should work with 1.4, in fact it is a part of
1.4, and very important for European users like myself.<br>
<br>
Anyway, I am trying to learn more about inner workings of Asterisk and
Astlinux, so I don't mind putting in a little time. If I make some
progress I will share it, of course.<br>
<br>
<pre class="moz-signature" cols="72">Niksa Baldun
</pre>
<br>
<br>
Kristian Kielhofner wrote:
<blockquote
 cite="mid...@ma..."
 type="cite">
  <pre wrap="">On 5/8/07, Niksa Baldun <a class="moz-txt-link-rfc2396E" href="mailto:nik...@lu...">&lt;nik...@lu...&gt;</a> wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap=""> Well, I've been at it all day, so I don't remember all the details. For
those packages that wouldn't compile, I checked which was the latest version
and updated the version number in the corresponding .mk file. I also updated
zaptel (I had to remove existing patch files and put the one I found on
Digium server). I had to change paths in asterisk.mk file so that configure
script would look for zaptel and libpri in correct places
(--with-pri=$(BUILD_DIR)/libpri-1.4.0
--with-zaptel=$(BUILD_DIR)/zaptel
--with-tonezone=$(BUILD_DIR)/zaptel).

 Also, there was some code in asterisk.mk that would always execute, even if
asterisk had already been built. For a lack of a better solution, I just
removed it temporarily.

 If there was anything else, I can't remember it now. Anyway, this is
obviously a work in progress, things like chan_misdn and spandsp are broken,
and who knows what else. I am sure Kristian and Darrick are rather busy, so
I wanted to work on this myself, I was just wandering what is the best way
to proceed.
 Niksa Baldun

    </pre>
  </blockquote>
  <pre wrap=""><!---->
Niksa,

  I'd hate to see you do work that you don't have to do...

  The asterisk-beta branch should be well synced with trunk for
packages OTHER than libpri, zaptel, and asterisk.  I just merged the
latest stuff from trunk into it.  There weren't any significant
package updates.

  I build asterisk-beta about as often as I build trunk on the same
systems using the same methods.  There aren't any more quirks than
there are in trunk - everything is identical EXCEPT for the asterisk,
zaptel, and libpri packages.  Even so all of those build fine on my
systems...

  The latest zaptel does not build but I am working on that.

  Using --with-* and referencing ($BUILD_DIR) is not correct.  The
necessary libraries and headers are copied to the proper locations in
$(STAGING_DIR) for Asterisk to find them.  It might work for you, but
what is there now should work and is more correct.  If you have to
hack this (or anything else), we should find out why and fix the real
problem.

  As far as add on packages like spandsp, chan_misdn, etc...  They
will be supported:

a)  Once Asterisk 1.4 itself has had enough testing
b)  Once the packages themselves support Asterisk 1.4 we can update
our packages to use versions that might actually have a chance of
working
c)  In some cases, they might not even be needed with Asterisk 1.4
(like app_conference)

  </pre>
</blockquote>
</body>
</html>