astlinux-users — AstLinux Users Mailing List

Re: [Astlinux-users] 1.4 revisited

[<gl...@gm...>]

Typo: Sandbox, member of the portage package.

On 5/12/07, Guilherme G=F3es <gl...@gm...> wrote:
> The link to snadbox in the branch asterisk-beta is broken also.
>
> On 5/11/07, Darrick Hartman <dha...@dj...> wrote:
> > Niksa Baldun wrote:
> > > I downloaded the latest 1.4 branch and tried to build it. This time I
> > > took note of all problems I found and resolved, as follows:
> > >
> > > 1. Zaptel wouldn't build. I played with zaptel.mk until it worked. Fo=
r
> > > some reason, it wouldn't build using "make -C", I had to cd to zaptel
> > > build dir and then it worked. I also had to build menuselect manually=
.
> > > While I was at it, I figured that menuselect should be presented
> > > before build, as there is no reason to build modules you won't need,
> > > so I included that, too. Patch file is attached.
> > This seems odd.  As Kristian mentioned before, there are several things
> > that may need to be changed with Zaptel and other associated asterisk
> > packages to get them to work with 1.4.  As we make changes, they are
> > being committed to SVN.  Your best bet is to subscribe to the svn commi=
t
> > list to see when something changes.
> >
> > > 2. func_curl wouldn't build, I just skipped it in menuselect.
> > I don't personally use it.
> > >
> > > 3. app_conference wouldn't build, but, as Kristian pointed out, it is
> > > candidate for removal anyway.
> > Will likely be removed.
> > >
> > > 4. flex wouldn't download, it took several retries, probably some
> > > problem with the server.
> > Will check for updates
> > >
> > > 5. openssh wouldn't download, .mk file looks for file
> > > openssh-4.5p1.tar.gz, but it doesn't exist on server, rather
> > > openssh-4.6p1.tar.gz (perhaps a typo?). Changed the version in .mk
> > > file and it worked.
> > This is not a typo.  That version of openssh is still available on the
> > server (I checked).  Openssh-4.6p1 is the latest release.  We need to
> > bump the version, but sometimes this requires changing a patch.  We'll
> > add it to the list.
> > >
> > > 6. zoneinfo wouldn't download, similar as previous, files
> > > tzcode2007c.tar.gz and tzdata2007c.tar.gz didn't exist, but rather
> > > tzcode2007f.tar.gz and tzdata2007f.tar.gz.
> > Updated (in trunk, 0.4 and asterisk-beta)
> >
> > >
> > > That is about it. Also, two minor things:
> > > 1. package "netsnmp" was recompiled each time I ran "make", I didn't
> > > investigate why.
> > haven't seen this.  I have seen this with apcupsd, but not netsnmp
> > > 2. whenever some package couldn't be found on corresponding server, i=
t
> > > was downloaded from astlinux site, but each time it was corrupted and
> > > couldn't be unpacked.
> > This is intended.  If for some reason the parent site moved files, the
> > fail over is to grab them from an astlinux site.  They should not be
> > corrupt however.  If there is a specific file that is corrupt, notify
> > Kristian and he'll look into it.  With some of the other issues, I'm
> > going to say that your internet connection is less than ideal and
> > perhaps the source of some of the problems you are having.
> >
> > Darrick
> >
> > --
> > Darrick Hartman
> > DJH Solutions, LLC
> > http://www.djhsolutions.com
> >
> >
> > -----------------------------------------------------------------------=
--
> > 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.
> > http://sourceforge.net/powerbar/db2/
> > _______________________________________________
> > Astlinux-users mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> >
> > Donations to support AstLinux are graciously accepted via PayPal to pay=
pa...@kr....
> >
>
>
> --
> Guilherme Loch G=F3es
>
> MSN:gl...@gm...
> (48) 99115299
>


--=20
Guilherme Loch G=F3es

MSN:gl...@gm...
(48) 99115299

Re: [Astlinux-users] 1.4 revisited

[<gl...@gm...>]

The link to snadbox in the branch asterisk-beta is broken also.

On 5/11/07, Darrick Hartman <dha...@dj...> wrote:
> Niksa Baldun wrote:
> > I downloaded the latest 1.4 branch and tried to build it. This time I
> > took note of all problems I found and resolved, as follows:
> >
> > 1. Zaptel wouldn't build. I played with zaptel.mk until it worked. For
> > some reason, it wouldn't build using "make -C", I had to cd to zaptel
> > build dir and then it worked. I also had to build menuselect manually.
> > While I was at it, I figured that menuselect should be presented
> > before build, as there is no reason to build modules you won't need,
> > so I included that, too. Patch file is attached.
> This seems odd.  As Kristian mentioned before, there are several things
> that may need to be changed with Zaptel and other associated asterisk
> packages to get them to work with 1.4.  As we make changes, they are
> being committed to SVN.  Your best bet is to subscribe to the svn commit
> list to see when something changes.
>
> > 2. func_curl wouldn't build, I just skipped it in menuselect.
> I don't personally use it.
> >
> > 3. app_conference wouldn't build, but, as Kristian pointed out, it is
> > candidate for removal anyway.
> Will likely be removed.
> >
> > 4. flex wouldn't download, it took several retries, probably some
> > problem with the server.
> Will check for updates
> >
> > 5. openssh wouldn't download, .mk file looks for file
> > openssh-4.5p1.tar.gz, but it doesn't exist on server, rather
> > openssh-4.6p1.tar.gz (perhaps a typo?). Changed the version in .mk
> > file and it worked.
> This is not a typo.  That version of openssh is still available on the
> server (I checked).  Openssh-4.6p1 is the latest release.  We need to
> bump the version, but sometimes this requires changing a patch.  We'll
> add it to the list.
> >
> > 6. zoneinfo wouldn't download, similar as previous, files
> > tzcode2007c.tar.gz and tzdata2007c.tar.gz didn't exist, but rather
> > tzcode2007f.tar.gz and tzdata2007f.tar.gz.
> Updated (in trunk, 0.4 and asterisk-beta)
>
> >
> > That is about it. Also, two minor things:
> > 1. package "netsnmp" was recompiled each time I ran "make", I didn't
> > investigate why.
> haven't seen this.  I have seen this with apcupsd, but not netsnmp
> > 2. whenever some package couldn't be found on corresponding server, it
> > was downloaded from astlinux site, but each time it was corrupted and
> > couldn't be unpacked.
> This is intended.  If for some reason the parent site moved files, the
> fail over is to grab them from an astlinux site.  They should not be
> corrupt however.  If there is a specific file that is corrupt, notify
> Kristian and he'll look into it.  With some of the other issues, I'm
> going to say that your internet connection is less than ideal and
> perhaps the source of some of the problems you are having.
>
> Darrick
>
> --
> Darrick Hartman
> DJH Solutions, LLC
> http://www.djhsolutions.com
>
>
> -------------------------------------------------------------------------
> 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.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to paypa=
l...@kr....
>


--=20
Guilherme Loch G=F3es

MSN:gl...@gm...
(48) 99115299

[Astlinux-users] files.astlinux.org some files corrupt

[Darrick H. <dha...@dj...>]

Kristian,

I get the following error.  Perhaps Niksa was correct earlier and some 
of the files on your server are not quite right.

bzcat 
/home/dhartman/astlinux/branches/asterisk-beta/dl/asterisk-native-sounds-20060209-01-g729.tar.bz2 
| tar -C 
/home/dhartman/astlinux/branches/asterisk-beta/build_i586/root/stat/var/lib/asterisk/   
-xf -
bzcat: 
/home/dhartman/astlinux/branches/asterisk-beta/dl/asterisk-native-sounds-20060209-01-g729.tar.bz2 
is not a bzip2 file.

Same issue with openssh from the files.astlinux.org site

net-snmp does build each time.  There are also some other oddball issues 
with this build.

I'll confirm sometime over the weekend whether this happens in trunk too 
or just in asterisk-beta.

Darrick

-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

Re: [Astlinux-users] 1.4 revisited

[Darrick H. <dha...@dj...>]

Niksa Baldun wrote:
> I downloaded the latest 1.4 branch and tried to build it. This time I 
> took note of all problems I found and resolved, as follows:
>
> 1. Zaptel wouldn't build. I played with zaptel.mk until it worked. For 
> some reason, it wouldn't build using "make -C", I had to cd to zaptel 
> build dir and then it worked. I also had to build menuselect manually. 
> While I was at it, I figured that menuselect should be presented 
> before build, as there is no reason to build modules you won't need, 
> so I included that, too. Patch file is attached.
This seems odd.  As Kristian mentioned before, there are several things 
that may need to be changed with Zaptel and other associated asterisk 
packages to get them to work with 1.4.  As we make changes, they are 
being committed to SVN.  Your best bet is to subscribe to the svn commit 
list to see when something changes.

> 2. func_curl wouldn't build, I just skipped it in menuselect.
I don't personally use it.
>
> 3. app_conference wouldn't build, but, as Kristian pointed out, it is 
> candidate for removal anyway.
Will likely be removed.
>
> 4. flex wouldn't download, it took several retries, probably some 
> problem with the server.
Will check for updates
>
> 5. openssh wouldn't download, .mk file looks for file 
> openssh-4.5p1.tar.gz, but it doesn't exist on server, rather 
> openssh-4.6p1.tar.gz (perhaps a typo?). Changed the version in .mk 
> file and it worked.
This is not a typo.  That version of openssh is still available on the 
server (I checked).  Openssh-4.6p1 is the latest release.  We need to 
bump the version, but sometimes this requires changing a patch.  We'll 
add it to the list.
>
> 6. zoneinfo wouldn't download, similar as previous, files 
> tzcode2007c.tar.gz and tzdata2007c.tar.gz didn't exist, but rather 
> tzcode2007f.tar.gz and tzdata2007f.tar.gz.
Updated (in trunk, 0.4 and asterisk-beta)

>
> That is about it. Also, two minor things:
> 1. package "netsnmp" was recompiled each time I ran "make", I didn't 
> investigate why.
haven't seen this.  I have seen this with apcupsd, but not netsnmp
> 2. whenever some package couldn't be found on corresponding server, it 
> was downloaded from astlinux site, but each time it was corrupted and 
> couldn't be unpacked.
This is intended.  If for some reason the parent site moved files, the 
fail over is to grab them from an astlinux site.  They should not be 
corrupt however.  If there is a specific file that is corrupt, notify 
Kristian and he'll look into it.  With some of the other issues, I'm 
going to say that your internet connection is less than ideal and 
perhaps the source of some of the problems you are having.

Darrick

-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

Re: [Astlinux-users] how can I use modem to send or recive fax withastlinux

[IS <is...@es...>]

modem.conf is used by isdn4linux. mISDN is a kind of successor of isdn4linux.

Read http://www.voip-info.org/wiki/index.php?page=Asterisk+ISDN4Linux

I can only suggest that you go for iaxmodem+hylafax. That is the best
solution. Of course it also works with ISDN and mISDN...

regards,

Ingmar

quoting Darrick Hartman
> I take part of this back.  There is a modem.conf in /stat/etc/asterisk.
> It is intended for use with ISDN lines.
>
> Perhaps Ingmar can share more about this.
>
> Darrick
>
> Darrick Hartman wrote:
>> Nedi wrote:
>>
>>> hi all,
>>> I see modem.conf  in the Astlinux
>>> how can I use  modem to send or recive fax  with astlinux
>>>
>>> has anyone sample or working conf files for faxing with astlinux?
>>>
>>>
>> Nedi,
>>
>> You see iaxmodem.conf, not modem.conf (or at least you should).
>> Iaxmodem is included along with efax on the 0.4.5 release.  It is not
>> very well tested and it is not recommended for use with voip lines.
>> What is recommended is using inbound analog lines with an FXO adapter
>> (such as a Digium TDM400 card) using iaxmodem as the virtual modem, with
>> Hylafax running on a separate box.  Saying all that, I have been able to
>> send and receive faxes with VoIP lines.  Do not expect it to work if
>> your line is heavily loaded or you are experiencing alot of jitter or
>> latency.
>>
>> You can find examples of how to use iaxmodem at the iaxmodem website
>> (iaxmodem.sourceforge.net)
>>
>> Darrick
>>
>>
>
>
> --
> Darrick Hartman
> DJH Solutions, LLC
> http://www.djhsolutions.com
>
>
> -------------------------------------------------------------------------
> 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 li
> mits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to
> pa...@kr....

[Astlinux-users] 1.4 revisited

[Niksa B. <nik...@lu...>]

I downloaded the latest 1.4 branch and tried to build it. This time I 
took note of all problems I found and resolved, as follows:

1. Zaptel wouldn't build. I played with zaptel.mk until it worked. For 
some reason, it wouldn't build using "make -C", I had to cd to zaptel 
build dir and then it worked. I also had to build menuselect manually. 
While I was at it, I figured that menuselect should be presented before 
build, as there is no reason to build modules you won't need, so I 
included that, too. Patch file is attached.

2. func_curl wouldn't build, I just skipped it in menuselect.

3. app_conference wouldn't build, but, as Kristian pointed out, it is 
candidate for removal anyway.

4. flex wouldn't download, it took several retries, probably some 
problem with the server.

5. openssh wouldn't download, .mk file looks for file 
openssh-4.5p1.tar.gz, but it doesn't exist on server, rather 
openssh-4.6p1.tar.gz (perhaps a typo?). Changed the version in .mk file 
and it worked.

6. zoneinfo wouldn't download, similar as previous, files 
tzcode2007c.tar.gz and tzdata2007c.tar.gz didn't exist, but rather 
tzcode2007f.tar.gz and tzdata2007f.tar.gz.

That is about it. Also, two minor things:
1. package "netsnmp" was recompiled each time I ran "make", I didn't 
investigate why.
2. whenever some package couldn't be found on corresponding server, it 
was downloaded from astlinux site, but each time it was corrupted and 
couldn't be unpacked.

Hope this helps someone.

-- 
Niksa Baldun

Re: [Astlinux-users] restart astlinux dayly at 04.00 at morning

[Bryce C. <br...@rh...>]

Nedi,
That's the VI[M] text editor. Please have a look here 
(http://www.ph.unimelb.edu.au/~ssk/vim/howto.html) for an introduction 
on how to use it. Needless to say, it's not like "most" text editors 
these days in that you have to select an input mode before you can 
actually edit things.

Regards,
Bryce Chidester
Rhino Equipment Corp.
br...@rh...
Tel: +1 (480) 621-4015
Fax: +1 (480) 961-1826
FWD: 633686 x6351
IP: asterisk.rhinoequipment.com x6351

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE  PROPRIETARY MATERIAL and is thus for use only by the intended  recipient. If you received this in error, please contact the sender  and delete the email and its attachments from all computers.



Nedi wrote:
> I have tryed to edit my crontab to restart astlinux  dayly at  04.00 at 
> morning
> and  if I type
>
> allversal ~ # crontab -l
> crontab: no crontab for root
> allversal ~ # crontab /etc/crontab
> crontab: unable to open /etc/crontab
> crontab: unable to read replacement file
> allversal ~ #
>
>
>
> should a Mount Read/Write:  to edit ?
>
> If I type
> allversal ~ # crontab -e  in my console  i get only
> editor and i can't type anything  I thing I make something wrong .
>
> ------------------------------------------------------------------------------------------------------
> ~
> ~
> ~
> ~
> ~
> ~
> ~
> ~
> - /var/spool/cron/crontab.1135 1/1 100%
>
> nedi 
>
>
> -------------------------------------------------------------------------
> 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.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
>
>   

[Astlinux-users] restart astlinux dayly at 04.00 at morning

[Nedi <ne...@gm...>]

I have tryed to edit my crontab to restart astlinux  dayly at  04.00 at 
morning
and  if I type

allversal ~ # crontab -l
crontab: no crontab for root
allversal ~ # crontab /etc/crontab
crontab: unable to open /etc/crontab
crontab: unable to read replacement file
allversal ~ #



should a Mount Read/Write:  to edit ?

If I type
allversal ~ # crontab -e  in my console  i get only
editor and i can't type anything  I thing I make something wrong .

------------------------------------------------------------------------------------------------------
~
~
~
~
~
~
~
~
- /var/spool/cron/crontab.1135 1/1 100%

nedi 

Re: [Astlinux-users] Net5501?

[Mark P. <g7...@g7...>]

Looks like I'll have to order one for my test bench and do some load
testing.  

I gotta find me a new hobby. This one costs me too much ;-}

Mark



On Thu, 2007-05-10 at 22:00 -0400, Kristian Kielhofner wrote:
> On 5/10/07, ast...@el... <ast...@el...> wrote:
> >
> > Well, that teaches me to do a search before I open my mouth...
> >
> > But the net5501 is shipping now-ish/shortly, so I figured since
> > Astlinux gives Soekris so much love, that they would put Kristian near
> > the top of the shipping list.
> >
> 
> asterisk,
> 
>   I have ordered one and Soren has told me that I am towards the top
> of the list.  I should say we (astlinux-users) are towards the top of
> the list ;).
> 
> 

Re: [Astlinux-users] Net5501?

[Graham S. <gu...@bt...>]

Just wondering if anyone has got one of the PC Engines Alix boards yet
as I see they are now available in beta format for testing?

----- Original Message ----
From: Kristian Kielhofner <kri...@gm...>
To: AstLinux Users Mailing List <ast...@li...>
Sent: Friday, 11 May, 2007 3:00:40 AM
Subject: Re: [Astlinux-users] Net5501?

On 5/10/07, ast...@el... <ast...@el...> wrote:
>
> Well, that teaches me to do a search before I open my mouth...
>
> But the net5501 is shipping now-ish/shortly, so I figured since
> Astlinux gives Soekris so much love, that they would put Kristian near
> the top of the shipping list.
>

asterisk,

  I have ordered one and Soren has told me that I am towards the top
of the list.  I should say we (astlinux-users) are towards the top of
the list ;).


-- 
Kristian Kielhofner

-------------------------------------------------------------------------
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.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] Net5501?

[Kristian K. <kri...@gm...>]

On 5/10/07, ast...@el... <ast...@el...> wrote:
>
> Well, that teaches me to do a search before I open my mouth...
>
> But the net5501 is shipping now-ish/shortly, so I figured since
> Astlinux gives Soekris so much love, that they would put Kristian near
> the top of the shipping list.
>

asterisk,

  I have ordered one and Soren has told me that I am towards the top
of the list.  I should say we (astlinux-users) are towards the top of
the list ;).


-- 
Kristian Kielhofner

Re: [Astlinux-users] Net5501?

[Darrick H. <dha...@dj...>]

Lonnie Abelbeck wrote:
> The comment I quoted was from the SVN not here in the mailing list.   
> Don't be so hard on yourself... ;)
>
>  From the Soekris site, it appears the net5501 has not made it to the  
> US shores yet.  The availability is still "May" not "Yes" yet.
>   
I have one of these on order and have been assured that I will receive 
one of these in the initial order.  Testing will ensue when received.  
(and no I did not receive a confirmation on the shipping date).

Darrick

-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

Re: [Astlinux-users] Net5501?

[Lonnie A. <li...@lo...>]

The comment I quoted was from the SVN not here in the mailing list.   
Don't be so hard on yourself... ;)

 From the Soekris site, it appears the net5501 has not made it to the  
US shores yet.  The availability is still "May" not "Yes" yet.

Lonnie


On May 10, 2007, at 8:22 PM, ast...@el... wrote:

> On 5/11/07, Lonnie Abelbeck <li...@lo...> wrote:
>> Kristian's comment (2 days ago)
>> "Initial support for the Soekris net5501
>> I don't actually have one of these, so this config
>> is based upon my best guesses from reading the
>> available docs on this board.
>>
>> Let me know how it goes..."
>>
>> Lonnie
>
> Well, that teaches me to do a search before I open my mouth...
>
> But the net5501 is shipping now-ish/shortly, so I figured since
> Astlinux gives Soekris so much love, that they would put Kristian near
> the top of the shipping list.
>
> ---------------------------------------------------------------------- 
> ---
> 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.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to  
> pa...@kr....
>

Re: [Astlinux-users] Net5501?

[<ast...@el...>]

On 5/11/07, Lonnie Abelbeck <li...@lo...> wrote:
> Kristian's comment (2 days ago)
> "Initial support for the Soekris net5501
> I don't actually have one of these, so this config
> is based upon my best guesses from reading the
> available docs on this board.
>
> Let me know how it goes..."
>
> Lonnie

Well, that teaches me to do a search before I open my mouth...

But the net5501 is shipping now-ish/shortly, so I figured since
Astlinux gives Soekris so much love, that they would put Kristian near
the top of the shipping list.

Re: [Astlinux-users] Net5501?

[Lonnie A. <li...@lo...>]

Kristian's comment (2 days ago)
"Initial support for the Soekris net5501
I don't actually have one of these, so this config
is based upon my best guesses from reading the
available docs on this board.

Let me know how it goes..."

Lonnie


On May 10, 2007, at 6:56 PM, ast...@el... wrote:

> So I saw that net5501 update in trunk. That means Kristian probably
> got a hold of one recently. Care to give some first impressions of the
> device?
>
> ---------------------------------------------------------------------- 
> ---
> 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.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to  
> pa...@kr....
>

[Astlinux-users] Net5501?

[<ast...@el...>]

So I saw that net5501 update in trunk. That means Kristian probably
got a hold of one recently. Care to give some first impressions of the
device?

Re: [Astlinux-users] how can I use modem to send or recive fax with astlinux

[Darrick H. <dha...@dj...>]

I take part of this back.  There is a modem.conf in /stat/etc/asterisk.  
It is intended for use with ISDN lines.

Perhaps Ingmar can share more about this.

Darrick

Darrick Hartman wrote:
> Nedi wrote:
>   
>> hi all,
>> I see modem.conf  in the Astlinux 
>> how can I use  modem to send or recive fax  with astlinux
>>
>> has anyone sample or working conf files for faxing with astlinux?
>>   
>>     
> Nedi,
>
> You see iaxmodem.conf, not modem.conf (or at least you should).  
> Iaxmodem is included along with efax on the 0.4.5 release.  It is not 
> very well tested and it is not recommended for use with voip lines.  
> What is recommended is using inbound analog lines with an FXO adapter 
> (such as a Digium TDM400 card) using iaxmodem as the virtual modem, with 
> Hylafax running on a separate box.  Saying all that, I have been able to 
> send and receive faxes with VoIP lines.  Do not expect it to work if 
> your line is heavily loaded or you are experiencing alot of jitter or 
> latency.
>
> You can find examples of how to use iaxmodem at the iaxmodem website 
> (iaxmodem.sourceforge.net)
>
> Darrick
>
>   


-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

Re: [Astlinux-users] how can I use modem to send or recive fax with astlinux

[Darrick H. <dha...@dj...>]

Nedi wrote:
> hi all,
> I see modem.conf  in the Astlinux 
> how can I use  modem to send or recive fax  with astlinux
>
> has anyone sample or working conf files for faxing with astlinux?
>   
Nedi,

You see iaxmodem.conf, not modem.conf (or at least you should).  
Iaxmodem is included along with efax on the 0.4.5 release.  It is not 
very well tested and it is not recommended for use with voip lines.  
What is recommended is using inbound analog lines with an FXO adapter 
(such as a Digium TDM400 card) using iaxmodem as the virtual modem, with 
Hylafax running on a separate box.  Saying all that, I have been able to 
send and receive faxes with VoIP lines.  Do not expect it to work if 
your line is heavily loaded or you are experiencing alot of jitter or 
latency.

You can find examples of how to use iaxmodem at the iaxmodem website 
(iaxmodem.sourceforge.net)

Darrick

-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

[Astlinux-users] how can I use modem to send or recive fax with astlinux

[Nedi <ne...@gm...>]

hi all,
I see modem.conf  in the Astlinux 
how can I use  modem to send or recive fax  with astlinux

has anyone sample or working conf files for faxing with astlinux?

or a working sample for faxing trough sip 

regards 
nedi

[Astlinux-users] Write to Flash for each SIP register

[Lonnie A. <li...@lo...>]

Question,

Does it concern anyone that for every SIP register, an update to the  
astdb is made, which in my case is on flash?

Maybe there is too much made about limited writes to CF, considering  
the wear-leveling and oversized cards, but I thought I would ask.

Lonnie

[Astlinux-users] mDNSResponder: Unknown DNS packet type 2800 and 7800 ..

[Nedi <ne...@gm...>]

Hi all,

I use DynDNS on my Astlinux and I get some erors in the console
can anyone help me what is wrong ?

I get
mDNSResponder: Unknown DNS packet type 2800  from 24.64.36.130 :2608  to 
192.168.1.132 :5353 on 00000000  (ignored)

and

mDNSResponder: Unknown DNS packet type 7800  from 24.64.36.130 :2608  to 
192.168.1.132 :5353 on 00000000  (ignored)

I have every days problems wit any provider  the number is registered but 
some hours later  i can't make phone til I reboot Astlinux.

in my rc.conf I have  ports for sip open and my astlinx is 192.168.1.132 and 
i set it to DMZ on my router.

##EXTOPEN
##A list of ports (with protocol) that will be opened on the external
#interface to the AstLinux machine.  Here you can add access to IAX
##SIP, etc.
##t= tcp u= udp
EXTOPEN="t22 u4569 u5060 u10000:20000

i try to disable firewall on my router

Nedi


 

Re: [Astlinux-users] Asterisk 1.4 branch

[Niksa B. <nik...@lu...>]

<!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">
Well, sure, but there is not much point. I already explained the
modifications I made, and they are not that extensive. If you really
want it, I'll send them tomorrow when I am back at work. But I am just
learning this stuff, so this is probably not the best way to do things,
as Kristian pointed out.<br>
<pre class="moz-signature" cols="72">Niksa Baldun
</pre>
<br>
<br>
Guilherme G&oacute;es wrote:
<blockquote
 cite="mid...@ma..."
 type="cite">
  <pre wrap="">Can you send me your asterisk, libpri and zaptel dirs ?

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

Niksa Baldun

Guilherme G&oacute;es wrote:
Niksa,
    </pre>
  </blockquote>
  <pre wrap=""><!---->
What patch for zaptel from Digium are you talking about ? Can you
  </pre>
  <blockquote type="cite">
    <pre wrap="">post the url ?
    </pre>
  </blockquote>
  <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="">Kristian,
    </pre>
  </blockquote>
  <pre wrap=""><!---->
thanks a lot for the clarification. However, I asure I wouldn0t
  </pre>
  <blockquote type="cite">
    <pre wrap="">do any of
    </pre>
  </blockquote>
  <pre wrap=""><!---->this if it wasn't necessary.

You say you are working on zaptel,
  </pre>
  <blockquote type="cite">
    <pre wrap="">but I didn't have a problem with it. I
    </pre>
  </blockquote>
  <pre wrap=""><!---->used the latest version (+patch) from
  </pre>
  <blockquote type="cite">
    <pre wrap="">Digium's site and it compiled fine.
    </pre>
  </blockquote>
  <pre wrap=""><!---->However, asterisk wouldn't let me
  </pre>
  <blockquote type="cite">
    <pre wrap="">compile chan_zap until I changed the paths
    </pre>
  </blockquote>
  <pre wrap=""><!---->in asterisk.mk, I am quite
  </pre>
  <blockquote type="cite">
    <pre wrap="">certain of that.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
As for chan_misdn, it should work with 1.4, in fact it is
  </pre>
  <blockquote type="cite">
    <pre wrap="">a part of 1.4, and
    </pre>
  </blockquote>
  <pre wrap=""><!---->very important for European users like myself.

Anyway, I
  </pre>
  <blockquote type="cite">
    <pre wrap="">am trying to learn more about inner workings of Asterisk and
    </pre>
  </blockquote>
  <pre wrap=""><!---->Astlinux, so I
  </pre>
  <blockquote type="cite">
    <pre wrap="">don't mind putting in a little time. If I make some progress
    </pre>
  </blockquote>
  <pre wrap=""><!---->I will share
  </pre>
  <blockquote type="cite">
    <pre wrap="">it, of course.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Niksa Baldun


Kristian Kielhofner wrote:
On 5/8/07, Niksa
  </pre>
  <blockquote type="cite">
    <pre wrap="">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.
    </pre>
  </blockquote>
  <pre wrap=""><!---->For

  </pre>
  <blockquote type="cite">
    <pre wrap="">those packages that wouldn't compile, I checked which was the latest
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
  <blockquote type="cite">
    <pre wrap="">version
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
  <blockquote type="cite">
    <pre wrap="">and updated the version number in the corresponding .mk file. I also
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
  <blockquote type="cite">
    <pre wrap="">updated
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
  <blockquote type="cite">
    <pre wrap="">zaptel (I had to remove existing patch files and put the one I found
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
  <blockquote type="cite">
    <pre wrap="">on
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
  <blockquote type="cite">
    <pre wrap="">Digium server). I had to change paths in asterisk.mk file so that
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
  <blockquote type="cite">
    <pre wrap="">configure
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
  <blockquote type="cite">
    <pre wrap="">script would look for zaptel and libpri in correct
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
  <blockquote type="cite">
    <pre wrap="">places
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
  <blockquote type="cite">
    <pre wrap="">(--with-pri=$(BUILD_DIR)/libpri-1.4.0
    </pre>
  </blockquote>
  <pre wrap=""><!---->--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
    </pre>
  </blockquote>
  <pre wrap=""><!---->if
  </pre>
  <blockquote type="cite">
    <pre wrap="">asterisk had already been built. For a lack of a better solution, I
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
  <blockquote type="cite">
    <pre wrap="">just
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
  <blockquote type="cite">
    <pre wrap="">removed it temporarily.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
 If there was anything else, I can't remember

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



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

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

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

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

  </pre>
  <blockquote type="cite">
    <pre wrap="">chan_misdn, etc... They
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
  <blockquote type="cite">
    <pre wrap="">will be supported:
    </pre>
  </blockquote>
  <pre wrap=""><!---->
a) Once Asterisk 1.4 itself has

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

  </pre>
  <blockquote type="cite">
    <pre wrap="">1.4
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
  <blockquote type="cite">
    <pre wrap="">(like app_conference)
    </pre>
  </blockquote>
  <pre wrap=""><!---->


  </pre>
  <blockquote type="cite">
    <pre wrap="">-------------------------------------------------------------------------
    </pre>
  </blockquote>
  <pre wrap=""><!---->This
  </pre>
  <blockquote type="cite">
    <pre wrap="">SF.net email is sponsored by DB2 Express
    </pre>
  </blockquote>
  <pre wrap=""><!---->Download DB2 Express C - the FREE
  </pre>
  <blockquote type="cite">
    <pre wrap="">version of DB2 express and take
    </pre>
  </blockquote>
  <pre wrap=""><!---->control of your XML. No limits. Just data.
  </pre>
  <blockquote type="cite">
    <pre wrap="">Click to get it
now.
    </pre>
  </blockquote>
  <pre wrap=""><!----><a class="moz-txt-link-freetext" href="http://sourceforge.net/powerbar/db2/">http://sourceforge.net/powerbar/db2/</a>
_______________________________________________
Astlinux-users
  </pre>
  <blockquote type="cite">
    <pre wrap="">mailing
list
    </pre>
  </blockquote>
  <pre wrap=""><!----><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
  </pre>
  <blockquote type="cite">
    <pre wrap="">to support AstLinux are graciously accepted via PayPal
to
    </pre>
  </blockquote>
  <pre wrap=""><!----><a class="moz-txt-link-abbreviated" href="mailto:pa...@kr...">pa...@kr...</a>.


  </pre>
  <pre wrap=""><!---->
  </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>

Re: [Astlinux-users] Asterisk 1.4 branch

[<gl...@gm...>]

Can you send me your asterisk, libpri and zaptel dirs ?

On 5/8/07, Niksa Baldun <nik...@lu...> wrote:
> ftp://ftp.digium.com/pub/zaptel/releases/zaptel-1.4.2.tar.gz
> ftp://ftp.digium.com/pub/zaptel/releases/zaptel-1.4.2-patch.gz
>
> Niksa Baldun
>
> Guilherme G=F3es wrote:
> Niksa,

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

On 5/8/07, Niksa Baldun <nik...@lu...> wrote:

> 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 <nik...@lu...> wrote:

>
>  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=3D$(BUILD_DIR)/libpri-1.4.0
--with-zaptel=3D$(BUILD_DIR)/zaptel
--with-tonezone=3D$(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



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



> -------------------------------------------------------------------------
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.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Astlinux-users
> mailing
> list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations
> to support AstLinux are graciously accepted via PayPal
> to
pa...@kr....


>

>
> -------------------------------------------------------------------------
> 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.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to
> pa...@kr....
>


--=20
Guilherme Loch G=F3es

MSN:gl...@gm...
(48) 99115299

Re: [Astlinux-users] Asterisk 1.4 branch

[Niksa B. <nik...@lu...>]

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

Re: [Astlinux-users] Asterisk 1.4 branch

[<gl...@gm...>]

Niksa,

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

On 5/8/07, Niksa Baldun <nik...@lu...> wrote:
> 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 pa=
ths
> 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 progre=
ss
> I will share it, of course.
>
> Niksa Baldun
>
>
> Kristian Kielhofner wrote:
> On 5/8/07, Niksa Baldun <nik...@lu...> wrote:

>  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=3D$(BUILD_DIR)/libpri-1.4.0
--with-zaptel=3D$(BUILD_DIR)/zaptel
--with-tonezone=3D$(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


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


>
> -------------------------------------------------------------------------
> 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.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to
> pa...@kr....
>


--=20
Guilherme Loch G=F3es

MSN:gl...@gm...
(48) 99115299