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">
<a class="moz-txt-link-freetext" href="ftp://ftp.digium.com/pub/zaptel/releases/zaptel-1.4.2.tar.gz">ftp://ftp.digium.com/pub/zaptel/releases/zaptel-1.4.2.tar.gz</a><br>
<a class="moz-txt-link-freetext" href="ftp://ftp.digium.com/pub/zaptel/releases/zaptel-1.4.2-patch.gz">ftp://ftp.digium.com/pub/zaptel/releases/zaptel-1.4.2-patch.gz</a><br>
<br>
<pre class="moz-signature" cols="72">Niksa Baldun
</pre>
<br>
Guilherme G&oacute;es wrote:
<blockquote
 cite="mid...@ma..."
 type="cite">
  <pre wrap="">Niksa,

What patch for zaptel from Digium are you talking about ? Can you post the url ?

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="">Kristian,

thanks a lot for the clarification. However, I asure I wouldn0t do any of
this if it wasn't necessary.

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.

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.

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.

Niksa Baldun

Kristian Kielhofner wrote:
On 5/8/07, Niksa Baldun <a class="moz-txt-link-rfc2396E" href="mailto:nik...@lu...">&lt;nik...@lu...&gt;</a> wrote:
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
  <blockquote type="cite">
    <pre wrap=""> Well, I've been at it all day, so I don't remember all the details.
For
    </pre>
  </blockquote>
  <pre wrap=""><!---->those packages that wouldn't compile, I checked which was the latest
  </pre>
  <blockquote type="cite">
    <pre wrap="">version
    </pre>
  </blockquote>
  <pre wrap=""><!---->and updated the version number in the corresponding .mk file. I also
  </pre>
  <blockquote type="cite">
    <pre wrap="">updated
    </pre>
  </blockquote>
  <pre wrap=""><!---->zaptel (I had to remove existing patch files and put the one I found
  </pre>
  <blockquote type="cite">
    <pre wrap="">on
    </pre>
  </blockquote>
  <pre wrap=""><!---->Digium server). I had to change paths in asterisk.mk file so that
  </pre>
  <blockquote type="cite">
    <pre wrap="">configure
    </pre>
  </blockquote>
  <pre wrap=""><!---->script would look for zaptel and libpri in correct
  </pre>
  <blockquote type="cite">
    <pre wrap="">places
    </pre>
  </blockquote>
  <pre wrap=""><!---->(--with-pri=$(BUILD_DIR)/libpri-1.4.0
--with-zaptel=$(BUILD_DIR)/zaptel
--with-tonezone=$(BUILD_DIR)/zaptel).

  </pre>
  <blockquote type="cite">
    <pre wrap="">Also, there was some code in asterisk.mk that would always execute, even
if
    </pre>
  </blockquote>
  <pre wrap=""><!---->asterisk had already been built. For a lack of a better solution, I
  </pre>
  <blockquote type="cite">
    <pre wrap="">just
    </pre>
  </blockquote>
  <pre wrap=""><!---->removed it temporarily.

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

  </pre>
  <blockquote type="cite">
    <pre wrap="">Niksa,
    </pre>
  </blockquote>
  <pre wrap=""><!---->
 I'd hate to see you do work that you don't have to do...

 The
  </pre>
  <blockquote type="cite">
    <pre wrap="">asterisk-beta branch should be well synced with trunk for
    </pre>
  </blockquote>
  <pre wrap=""><!---->packages OTHER
  </pre>
  <blockquote type="cite">
    <pre wrap="">than libpri, zaptel, and asterisk. I just merged the
    </pre>
  </blockquote>
  <pre wrap=""><!---->latest stuff from trunk
  </pre>
  <blockquote type="cite">
    <pre wrap="">into it. There weren't any significant
    </pre>
  </blockquote>
  <pre wrap=""><!---->package updates.

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

 The latest
  </pre>
  <blockquote type="cite">
    <pre wrap="">zaptel does not build but I am working on that.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
 Using --with-* and
  </pre>
  <blockquote type="cite">
    <pre wrap="">referencing ($BUILD_DIR) is not correct. The
    </pre>
  </blockquote>
  <pre wrap=""><!---->necessary libraries and headers
  </pre>
  <blockquote type="cite">
    <pre wrap="">are copied to the proper locations in
    </pre>
  </blockquote>
  <pre wrap=""><!---->$(STAGING_DIR) for Asterisk to find
  </pre>
  <blockquote type="cite">
    <pre wrap="">them. It might work for you, but
    </pre>
  </blockquote>
  <pre wrap=""><!---->what is there now should work and is more
  </pre>
  <blockquote type="cite">
    <pre wrap="">correct. If you have to
    </pre>
  </blockquote>
  <pre wrap=""><!---->hack this (or anything else), we should find out why
  </pre>
  <blockquote type="cite">
    <pre wrap="">and fix the real
    </pre>
  </blockquote>
  <pre wrap=""><!---->problem.

 As far as add on packages like spandsp,
  </pre>
  <blockquote type="cite">
    <pre wrap="">chan_misdn, etc... They
    </pre>
  </blockquote>
  <pre wrap=""><!---->will be supported:

a) Once Asterisk 1.4 itself has
  </pre>
  <blockquote type="cite">
    <pre wrap="">had enough testing
    </pre>
  </blockquote>
  <pre wrap=""><!---->b) Once the packages themselves support Asterisk 1.4 we
  </pre>
  <blockquote type="cite">
    <pre wrap="">can update
    </pre>
  </blockquote>
  <pre wrap=""><!---->our packages to use versions that might actually have a chance
  </pre>
  <blockquote type="cite">
    <pre wrap="">of
    </pre>
  </blockquote>
  <pre wrap=""><!---->working
c) In some cases, they might not even be needed with Asterisk
  </pre>
  <blockquote type="cite">
    <pre wrap="">1.4
    </pre>
  </blockquote>
  <pre wrap=""><!---->(like app_conference)

  </pre>
  <blockquote type="cite">
    <pre wrap="">-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
<a class="moz-txt-link-freetext" href="http://sourceforge.net/powerbar/db2/">http://sourceforge.net/powerbar/db2/</a>
_______________________________________________
Astlinux-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ast...@li...">Ast...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/astlinux-users">https://lists.sourceforge.net/lists/listinfo/astlinux-users</a>

Donations to support AstLinux are graciously accepted via PayPal to
<a class="moz-txt-link-abbreviated" href="mailto:pa...@kr...">pa...@kr...</a>.

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

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