> Hi Kristian,
> Thanks for your answer
> Respect to meet me performance, i am trying G.711 u law codec, I try the
> same codec with the same hardware with Asterisk 1.2 and it works fine.
>
> Best Regards
>
> Gustavo Persak
> Syscom Argentina S.A.

----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 23, 2006 1:13 AM
Subject: Astlinux-users Digest, Vol 12, Issue 33


> Send Astlinux-users mailing list submissions to
> [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.kriscompanies.com/mailman/listinfo/astlinux-users
> or, via email, send a message with subject or body 'help' to
> [EMAIL PROTECTED]
>
> You can reach the person managing the list at
> [EMAIL PROTECTED]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Astlinux-users digest..."
>
>
> Today's Topics:
>
>    1. Re: How to use ssmtp to send an attachment (Angus Comber)
>    2. Re: How to use ssmtp to send an attachment (Daryl Sanders)
>    3. Re: How to use ssmtp to send an attachment (Enzo Michelangeli)
>    4. Re: Astlinux-users Digest, Vol 12, Issue 32 (Gustavo Persak)
>    5. Re: Astlinux-users Digest, Vol 12, Issue 32 (Matt Riddell [NZ])
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 22 Feb 2006 18:41:20 -0000
> From: "Angus Comber" <[EMAIL PROTECTED]>
> Subject: Re: [Astlinux-users] How to use ssmtp to send an attachment
> To: "Discussion of AstLinux - Asterisk on Compact Flash"
> <[EMAIL PROTECTED]>
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; format=flowed; charset="iso-8859-1";
> reply-type=original
>
> I see.
>
> I firstly had problems using uuencode.  ie uuencode -m myinputfile
> encodedfile  didn't work!  Stranglely.  Any ideas why?
>
> But actually all I want to do is email the Master.csv file periodically.
As
> it is text I can make up the email headers, add in the Master.csv text,
add
> a footer and then hey presto - I might actually get it to work!  But
problem
> is each line cannot be longer than 76 characters.  So the MIME rfc says
you
> need to put in a '=' as a soft break.  Any ideas on how to put in a = and
a
> carriage return after the 76th character in each line?
>
> Angus
>
>
>
> ----- Original Message -----
> From: "Enzo Michelangeli" <[EMAIL PROTECTED]>
> To: "Discussion of AstLinux - Asterisk on Compact Flash"
> <[EMAIL PROTECTED]>
> Sent: Wednesday, February 22, 2006 12:46 AM
> Subject: Re: [Astlinux-users] How to use ssmtp to send an attachment
>
>
> > ----- Original Message -----
> > From: "Angus Comber" <[EMAIL PROTECTED]>
> > To: "Astlinux Users Mailing List" <[EMAIL PROTECTED]>
> > Sent: Wednesday, February 22, 2006 7:10 AM
> > Subject: [Astlinux-users] How to use ssmtp to send an attachment
> >
> >
> >> Hello
> >>
> >> I can send a standard email using ssmtp.  But how can I attach a file.
> > I
> >> just want to email the Master.csv file on a regular basis.  What would
> > be
> >> the easiest way to do this?
> >
> > Well, creating the RFC-822 message is a job for the UA (mail client) not
> > an MTA like ssmtp. For MIME messages containing attachments doing it
> > manually requires a fair amount of work, especially if the attachment is
> > binary. Astlinux doesn't have mmencode installed, but Busybox'
> > "uuencode -m" is a possible replacement (just cut off first and last
line
> > of the file sent to stdout). The MIME headers may be handcrafted, basing
> > your code on a sample MIME message created by a "real" mail client and
> > consulting the documents from http://www.ietf.org/rfc/rfc2045.txt to
> > http://www.ietf.org/rfc/rfc2049.txt to clarify doubts...
> >
> > There is also an old command-line utility called "Metamail" that would
do
> > most of the work for you, but it's not included in Astlinux.
> >
> > Cheers --
> >
> > Enzo
> >
> > _______________________________________________
> > Astlinux-users mailing list
> > [email protected]
> > http://lists.kriscompanies.com/mailman/listinfo/astlinux-users
> >
> > Donations to support AstLinux are graciously accepted via PayPal to
> > [EMAIL PROTECTED]
> >
> >
>
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 22 Feb 2006 14:37:57 -0700
> From: "Daryl Sanders" <[EMAIL PROTECTED]>
> Subject: Re: [Astlinux-users] How to use ssmtp to send an attachment
> To: "Discussion of AstLinux - Asterisk on Compact Flash"
> <[EMAIL PROTECTED]>
> Message-ID:
> <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=ISO-8859-1
>
> You might have a look at BIABAM at http://mmj.dk/biabam/ and see it
> can do anything for you. I'm also working on a solution for mailing
> out attachments from AstLinux. I plan to compile mutt for i586-Generi
> tonight. If you want I can send you the binary when I'm done.
>
> I'm using msmtp from astup right now which seems to work as expected.
> The problem I am running into is that some application want to use a
> MUA to generate the mail before it's sent to msmtp. (I have a kinda
> bastardized version of AstLinux that sends out log
> notifications/attachments and such via email with msmtp.)
>
> I'd also like my AstLinux box to be able to send asterisk voicemail to
> users via email, so I'm hoping to find a solution that will allow that
> too.
>
> - Daryl
>
> On 2/22/06, Angus Comber <[EMAIL PROTECTED]> wrote:
> > I see.
> >
> > I firstly had problems using uuencode.  ie uuencode -m myinputfile
> > encodedfile  didn't work!  Stranglely.  Any ideas why?
> >
> > But actually all I want to do is email the Master.csv file periodically.
As
> > it is text I can make up the email headers, add in the Master.csv text,
add
> > a footer and then hey presto - I might actually get it to work!  But
problem
> > is each line cannot be longer than 76 characters.  So the MIME rfc says
you
> > need to put in a '=' as a soft break.  Any ideas on how to put in a =
and a
> > carriage return after the 76th character in each line?
> >
> > Angus
> >
> >
> >
> > ----- Original Message -----
> > From: "Enzo Michelangeli" <[EMAIL PROTECTED]>
> > To: "Discussion of AstLinux - Asterisk on Compact Flash"
> > <[EMAIL PROTECTED]>
> > Sent: Wednesday, February 22, 2006 12:46 AM
> > Subject: Re: [Astlinux-users] How to use ssmtp to send an attachment
> >
> >
> > > ----- Original Message -----
> > > From: "Angus Comber" <[EMAIL PROTECTED]>
> > > To: "Astlinux Users Mailing List" <[EMAIL PROTECTED]>
> > > Sent: Wednesday, February 22, 2006 7:10 AM
> > > Subject: [Astlinux-users] How to use ssmtp to send an attachment
> > >
> > >
> > >> Hello
> > >>
> > >> I can send a standard email using ssmtp.  But how can I attach a
file.
> > > I
> > >> just want to email the Master.csv file on a regular basis.  What
would
> > > be
> > >> the easiest way to do this?
> > >
> > > Well, creating the RFC-822 message is a job for the UA (mail client)
not
> > > an MTA like ssmtp. For MIME messages containing attachments doing it
> > > manually requires a fair amount of work, especially if the attachment
is
> > > binary. Astlinux doesn't have mmencode installed, but Busybox'
> > > "uuencode -m" is a possible replacement (just cut off first and last
line
> > > of the file sent to stdout). The MIME headers may be handcrafted,
basing
> > > your code on a sample MIME message created by a "real" mail client and
> > > consulting the documents from http://www.ietf.org/rfc/rfc2045.txt to
> > > http://www.ietf.org/rfc/rfc2049.txt to clarify doubts...
> > >
> > > There is also an old command-line utility called "Metamail" that would
do
> > > most of the work for you, but it's not included in Astlinux.
> > >
> > > Cheers --
> > >
> > > Enzo
> > >
> > > _______________________________________________
> > > Astlinux-users mailing list
> > > [email protected]
> > > http://lists.kriscompanies.com/mailman/listinfo/astlinux-users
> > >
> > > Donations to support AstLinux are graciously accepted via PayPal to
> > > [EMAIL PROTECTED]
> > >
> > >
> >
> >
> >
> > _______________________________________________
> > Astlinux-users mailing list
> > [email protected]
> > http://lists.kriscompanies.com/mailman/listinfo/astlinux-users
> >
> > Donations to support AstLinux are graciously accepted via PayPal to
[EMAIL PROTECTED]
> >
>
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 23 Feb 2006 07:43:29 +0800
> From: "Enzo Michelangeli" <[EMAIL PROTECTED]>
> Subject: Re: [Astlinux-users] How to use ssmtp to send an attachment
> To: "Discussion of AstLinux - Asterisk on Compact Flash"
> <[EMAIL PROTECTED]>
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Angus,
>
> The "=" to break lines is part of the so-called "quoted-printable" Content
> Transfer Encoding, an alternative to base64 to pass binary content inside
> a MIME message suitable to 7-bit transports such as the original SMTP.
> It's convenient when there are few non-ASCII characters (e.g., sparse
> ISO-8859 characters with umlauts) and/or overlong lines, whereas base64
> makes the text unreadable but is more compact for true binaries such as
> executables etc. However, in your case you might be able to get away with
> plaintext non-MIME messages, because the line length limits (established
> in pre-MIME times by RFC822, now updated by RFC2822:
> http://www.ietf.org/rfc/rfc2822.txt ) are actually less restrictive:
>
>  [...]
>  - Lines of characters in the body MUST be limited to 998 characters,
>    and SHOULD be limited to 78 characters, excluding the CRLF.
>  [...]
>
> Most MTA's in current use can handle long lines (> 78 chars but <= 998)
> just fine.
>
> Regarding uuencode: it's second parameter (or first, if there is just one
> and the input is taken from stdin) is actually the remote filename, placed
> together with the original attribute bits on the first line for retrieval
> at decode time, and superfluous for MIME use (in which case, always pass
> "-m" as well to use base64 encoding and remove first and last line). The
> encoded output is always sent to stdout, so you should use:
>
>  uuencode -m <myinputfile remotefilename >myoutfile
>
> Cheers --
>
> Enzo
>
>
> ----- Original Message -----
> From: "Angus Comber" <[EMAIL PROTECTED]>
> To: "Discussion of AstLinux - Asterisk on Compact Flash"
> <[EMAIL PROTECTED]>
> Sent: Thursday, February 23, 2006 2:41 AM
> Subject: Re: [Astlinux-users] How to use ssmtp to send an attachment
>
>
> > I see.
> >
> > I firstly had problems using uuencode.  ie uuencode -m myinputfile
> > encodedfile  didn't work!  Stranglely.  Any ideas why?
> >
> > But actually all I want to do is email the Master.csv file periodically.
> As
> > it is text I can make up the email headers, add in the Master.csv text,
> add
> > a footer and then hey presto - I might actually get it to work!  But
> problem
> > is each line cannot be longer than 76 characters.  So the MIME rfc says
> you
> > need to put in a '=' as a soft break.  Any ideas on how to put in a =
> and a
> > carriage return after the 76th character in each line?
> >
> > Angus
> >
> >
> >
> > ----- Original Message -----
> > From: "Enzo Michelangeli" <[EMAIL PROTECTED]>
> > To: "Discussion of AstLinux - Asterisk on Compact Flash"
> > <[EMAIL PROTECTED]>
> > Sent: Wednesday, February 22, 2006 12:46 AM
> > Subject: Re: [Astlinux-users] How to use ssmtp to send an attachment
> >
> >
> > > ----- Original Message -----
> > > From: "Angus Comber" <[EMAIL PROTECTED]>
> > > To: "Astlinux Users Mailing List" <[EMAIL PROTECTED]>
> > > Sent: Wednesday, February 22, 2006 7:10 AM
> > > Subject: [Astlinux-users] How to use ssmtp to send an attachment
> > >
> > >
> > >> Hello
> > >>
> > >> I can send a standard email using ssmtp.  But how can I attach a
> file.
> > > I
> > >> just want to email the Master.csv file on a regular basis.  What
> would
> > > be
> > >> the easiest way to do this?
> > >
> > > Well, creating the RFC-822 message is a job for the UA (mail client)
> not
> > > an MTA like ssmtp. For MIME messages containing attachments doing it
> > > manually requires a fair amount of work, especially if the attachment
> is
> > > binary. Astlinux doesn't have mmencode installed, but Busybox'
> > > "uuencode -m" is a possible replacement (just cut off first and last
> line
> > > of the file sent to stdout). The MIME headers may be handcrafted,
> basing
> > > your code on a sample MIME message created by a "real" mail client and
> > > consulting the documents from http://www.ietf.org/rfc/rfc2045.txt to
> > > http://www.ietf.org/rfc/rfc2049.txt to clarify doubts...
> > >
> > > There is also an old command-line utility called "Metamail" that would
> do
> > > most of the work for you, but it's not included in Astlinux.
> > >
> > > Cheers --
> > >
> > > Enzo
> > >
> > > _______________________________________________
> > > Astlinux-users mailing list
> > > [email protected]
> > > http://lists.kriscompanies.com/mailman/listinfo/astlinux-users
> > >
> > > Donations to support AstLinux are graciously accepted via PayPal to
> > > [EMAIL PROTECTED]
> > >
> > >
> >
> >
> >
> > _______________________________________________
> > Astlinux-users mailing list
> > [email protected]
> > http://lists.kriscompanies.com/mailman/listinfo/astlinux-users
> >
> > Donations to support AstLinux are graciously accepted via PayPal to
> [EMAIL PROTECTED]
> >
>
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 22 Feb 2006 20:57:38 -0300
> From: "Gustavo Persak" <[EMAIL PROTECTED]>
> Subject: Re: [Astlinux-users] Astlinux-users Digest, Vol 12, Issue 32
> To: <[EMAIL PROTECTED]>
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Kristian,
> Thanks for your answer
> Respect to meet me performance, i am trying G.711 u law codec, I try the
> same codec with the same hardware with Asterisk 1.2 and it works fine.
>
> Best Regards
>
> Gustavo Persak
> Syscom Argentina S.A.
>
>
> ----- Original Message -----
> From: <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, February 22, 2006 2:00 PM
> Subject: Astlinux-users Digest, Vol 12, Issue 32
>
>
> > Send Astlinux-users mailing list submissions to
> > [email protected]
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> > http://lists.kriscompanies.com/mailman/listinfo/astlinux-users
> > or, via email, send a message with subject or body 'help' to
> > [EMAIL PROTECTED]
> >
> > You can reach the person managing the list at
> > [EMAIL PROTECTED]
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of Astlinux-users digest..."
> >
> >
> > Today's Topics:
> >
> >    1. Re: How to use ssmtp to send an attachment (Enzo Michelangeli)
> >    2. Re: Meet me perforfarmance (Kristian Kielhofner)
> >    3. Re: mISDN + hfc (Kristian Kielhofner)
> >    4. vmware image of development environment? (Tom Lynn)
> >    5. Re: Destination Nat (Tom Lynn)
> >    6. ACPI conflicting with eith0 & eth1 (Rich Sias)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Wed, 22 Feb 2006 08:46:54 +0800
> > From: "Enzo Michelangeli" <[EMAIL PROTECTED]>
> > Subject: Re: [Astlinux-users] How to use ssmtp to send an attachment
> > To: "Discussion of AstLinux - Asterisk on Compact Flash"
> > <[EMAIL PROTECTED]>
> > Message-ID: <[EMAIL PROTECTED]>
> > Content-Type: text/plain; charset="iso-8859-1"
> >
> > ----- Original Message -----
> > From: "Angus Comber" <[EMAIL PROTECTED]>
> > To: "Astlinux Users Mailing List" <[EMAIL PROTECTED]>
> > Sent: Wednesday, February 22, 2006 7:10 AM
> > Subject: [Astlinux-users] How to use ssmtp to send an attachment
> >
> >
> > > Hello
> > >
> > > I can send a standard email using ssmtp.  But how can I attach a file.
> > I
> > > just want to email the Master.csv file on a regular basis.  What would
> > be
> > > the easiest way to do this?
> >
> > Well, creating the RFC-822 message is a job for the UA (mail client) not
> > an MTA like ssmtp. For MIME messages containing attachments doing it
> > manually requires a fair amount of work, especially if the attachment is
> > binary. Astlinux doesn't have mmencode installed, but Busybox'
> > "uuencode -m" is a possible replacement (just cut off first and last
line
> > of the file sent to stdout). The MIME headers may be handcrafted, basing
> > your code on a sample MIME message created by a "real" mail client and
> > consulting the documents from http://www.ietf.org/rfc/rfc2045.txt to
> > http://www.ietf.org/rfc/rfc2049.txt to clarify doubts...
> >
> > There is also an old command-line utility called "Metamail" that would
do
> > most of the work for you, but it's not included in Astlinux.
> >
> > Cheers --
> >
> > Enzo
> >
> >
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Tue, 21 Feb 2006 20:50:04 -0500
> > From: Kristian Kielhofner <[EMAIL PROTECTED]>
> > Subject: Re: [Astlinux-users] Meet me perforfarmance
> > To: Discussion of AstLinux - Asterisk on Compact Flash
> > <[EMAIL PROTECTED]>
> > Message-ID: <[EMAIL PROTECTED]>
> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> >
> > Gustavo Persak wrote:
> > > Dear Sirs,
> > > I was trying meet me feature with Astlinux 0.3.0 running in a 64 MB CF
> > > card and the voice quality experimented is very bad, even in a two
party
> > > conference.
> > > I am running Astlinux in a Celeron 400 Mhz Box. I also try this box
with
> > > the latest version of Asterisk and the voice quality is very good,
just
> > > to see if there is a matter of processot lack.
> > > What I hear is a very cut unintelegible speach.
> > > What coul be the cause of this performance.
> > > Best Regards
> > >
> > > Gustavo Persak
> > > Syscom Argentina S.A.
> > >
> >
> > Gustavo,
> >
> > What codecs were you trying to use?
> >
> > --
> > Kristian Kielhofner
> >
> >
> > ------------------------------
> >
> > Message: 3
> > Date: Tue, 21 Feb 2006 20:52:19 -0500
> > From: Kristian Kielhofner <[EMAIL PROTECTED]>
> > Subject: Re: [Astlinux-users] mISDN + hfc
> > To: Discussion of AstLinux - Asterisk on Compact Flash
> > <[EMAIL PROTECTED]>
> > Message-ID: <[EMAIL PROTECTED]>
> > Content-Type: text/plain; charset=iso-8859-1; format=flowed
> >
> > Juergen K. Zick wrote:
> > > Ciao Giovanni,
> > >
> > > actually I use chan_capi-cm to be precise. I grabbed the recent
version
> and
> > > compiled it with Kris' development package ... I also made a new
kernel
> > > which includes some more NICs and ISDN cards I have available here ...
> > >
> > > Basically, you can install the devel-package on your normal LINUX
> > > development box and then you can follow the same way to compile
> > > chan_capi-cm as Kris has done e.g. with chan_misdn ...
> > >
> > > -J?rgen
> > >
> >
> > Jurgen (sorry about the u),
> >
> > Would you mind typing something up quickly describing how to do this?
> > I'd really appreciate it!
> >
> > --
> > Kristian Kielhofner
> >
> >
> > ------------------------------
> >
> > Message: 4
> > Date: Tue, 21 Feb 2006 21:12:00 -0800
> > From: "Tom Lynn" <[EMAIL PROTECTED]>
> > Subject: [Astlinux-users] vmware image of development environment?
> > To: "Discussion of AstLinux - Asterisk on Compact Flash"
> > <[EMAIL PROTECTED]>
> > Message-ID:
> > <[EMAIL PROTECTED]>
> > Content-Type: text/plain; charset=ISO-8859-1
> >
> > How difficult is it to set up the development environment in a vmware
> > player image?
> >
> > I'm hitting the point where I'd like to begin trying the various fax
> > options and it's becoming clear that I'm going to have to compile some
> > stuff.  Is this something trivial, or would it be best to leave it to
> > the pros?
> >
> > I don't have another PC to put a linux image onto, so it's vmware or
> > you'll soon see me on the street corner with a sign reading "will work
> > for castoff-500mhz PCs."
> >
> > Tom
> >
> >
> >
> > ------------------------------
> >
> > Message: 5
> > Date: Tue, 21 Feb 2006 21:13:37 -0800
> > From: "Tom Lynn" <[EMAIL PROTECTED]>
> > Subject: Re: [Astlinux-users] Destination Nat
> > To: "Discussion of AstLinux - Asterisk on Compact Flash"
> > <[EMAIL PROTECTED]>
> > Message-ID:
> > <[EMAIL PROTECTED]>
> > Content-Type: text/plain; charset=ISO-8859-1
> >
> > Thanks everybody.  I'm good now.
> >
> > On 2/20/06, Darrick Hartman <[EMAIL PROTECTED]> wrote:
> > > Mark Edwards wrote:
> > > > problem solved then...
> > > > ;-)
> > > >
> > > > I just wonder why the script didn't work in the first place?
> > >
> > > If you're looking for a firewalls script that only uses /bin/sh, try
> > > Arno's Firewall script.
> > >
> > > http://rocky.molphys.leidenuniv.nl/
> > >
> > > Works well and only involves one configuration file.  It would be easy
> > > to adapt this to work with the rc.conf file instead of it's own
> > > configuration file.
> > >
> > > Darrick
> > > --
> > > Darrick Hartman
> > > DJH Solutions, LLC
> > > 877.901.3113
> > > _______________________________________________
> > > Astlinux-users mailing list
> > > [email protected]
> > > http://lists.kriscompanies.com/mailman/listinfo/astlinux-users
> > >
> > > Donations to support AstLinux are graciously accepted via PayPal to
> [EMAIL PROTECTED]
> > >
> >
> >
> >
> > ------------------------------
> >
> > Message: 6
> > Date: Wed, 22 Feb 2006 16:15:03 +0000
> > From: Rich Sias <[EMAIL PROTECTED]>
> > Subject: [Astlinux-users] ACPI conflicting with eith0 & eth1
> > To: [EMAIL PROTECTED], Discussion of AstLinux - Asterisk on Compact
> > Flash <[EMAIL PROTECTED]>
> > Message-ID: <[EMAIL PROTECTED]>
> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> >
> > I can get rid of conflict with eth0 by adding kernal boot parm: livecd
> > acpi=noirq
> > NOW, I will get a conflict with eth1 on same IRQ 11 being held by acpi.
> > I am about ready to pay for a bios upgrade that supports "acpi 2.0" in
> > hopes that I can get the NICs to separate from the acpi in their need
> > for IRQ11.
> >
> > Are there anyway to get both NICs and the acpi to boot up peaceably with
> > astlinux ?
> >
> > I am about to start using my IDE/CF adapter, I think I got a boot once
> > just recent and noticed the same NIC vs acpi conflicts.
> >
> > Rich
> >
> >
> > ------------------------------
> >
> > _______________________________________________
> > Astlinux-users mailing list
> > [email protected]
> > http://lists.kriscompanies.com/mailman/listinfo/astlinux-users
> >
> > Donations to support AstLinux are graciously accepted via PayPal to
> [EMAIL PROTECTED]
> >
> > End of Astlinux-users Digest, Vol 12, Issue 32
> > **********************************************
> >
>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Thu, 23 Feb 2006 17:33:02 +1300
> From: "Matt Riddell [NZ]" <[EMAIL PROTECTED]>
> Subject: Re: [Astlinux-users] Astlinux-users Digest, Vol 12, Issue 32
> To: Discussion of AstLinux - Asterisk on Compact Flash
> <[EMAIL PROTECTED]>
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Gustavo Persak wrote:
> > Hi Kristian,
> > Thanks for your answer
> > Respect to meet me performance, i am trying G.711 u law codec, I try the
> > same codec with the same hardware with Asterisk 1.2 and it works fine.
>
> What were the audio issues you encountered?
>
> May be a problem with timing which meetme requires.
>
> Do you have the same problem with music on hold?
>
> --
> Cheers,
>
> Matt Riddell
> _______________________________________________
>
> http://www.sineapps.com/news.php (Daily Asterisk News - html)
> http://freevoip.gedameurope.com (Free Asterisk Voip Community)
> http://www.sineapps.com/rssfeed.php (Daily Asterisk News - rss)
>
>
> ------------------------------
>
> _______________________________________________
> Astlinux-users mailing list
> [email protected]
> http://lists.kriscompanies.com/mailman/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to
[EMAIL PROTECTED]
>
> End of Astlinux-users Digest, Vol 12, Issue 33
> **********************************************
>


_______________________________________________
Astlinux-users mailing list
[email protected]
http://lists.kriscompanies.com/mailman/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to [EMAIL 
PROTECTED]

Reply via email to