Fernando Berretta wrote:
Tzafir,
I'm sorry, my question wasn't clear.
Apparently Asterisk 1.6.0b2 and b4 has support for t38 because of some
modifications on app_fax so the questions are:
1 - If I use Asterisk 1.6.0b2 o b4 and a fax is received from a FXO Card
and this FXO port is
I haven't tried all of them but.. at least Linksys ATA AdminGuide
doesn't specify such limitation
FAX Enable T38
To enable the use of the ITU-T T.38 standard for faxing, select yes.
Otherwise, select no.
The default is yes
Thomas Kenyon wrote:
Fernando Berretta wrote:
Tzafir,
I'm
T.38 will not work with the fxo card.
Zoa
Fernando Berretta wrote:
Dear All,
Are you telling me Asterisk 1.6.0b2/4 has support for t38 and rxfax
etc. and will be able to receive faxes and negotiate with voip CPE's
like ATA's to transmit faxes which comes from FXO cards to VoIP
Devices
Benny Amorsen wrote:
Steve Underwood [EMAIL PROTECTED] writes:
Try reading the GPL and the FSF's interpretation of it. If things are
running in the same address space as my code, they need to be GPL
compatible, or I am likely to take action.
The GPL is not an EULA. You don't
Tzafir,
I'm sorry, my question wasn't clear.
Apparently Asterisk 1.6.0b2 and b4 has support for t38 because of some
modifications on app_fax so the questions are:
1 - If I use Asterisk 1.6.0b2 o b4 and a fax is received from a FXO Card
and this FXO port is forwarded to other ATA/Gateway is
zoa wrote:
T.38 will not work with the fxo card.
Zoa
That statement is a bit vague. What has been put in add-ons so far is
only support for T.38 termination. Not T.38 gateway operation.
Steve
Fernando Berretta wrote:
Dear All,
Are you telling me Asterisk 1.6.0b2/4 has support for
Thanks for clarify.. so Asterisk will be able to receive faxes which
comes from a Gateway using t38 but will not be able to relay faxes which
comes from PSTN through a FXO card to other Gateway using t38
can this version of app_fax be used with Asterisk 1.4x ?
Steve Underwood wrote:
zoa
Fernando Berretta wrote:
Tzafir,
I'm sorry, my question wasn't clear.
Apparently Asterisk 1.6.0b2 and b4 has support for t38 because of some
modifications on app_fax so the questions are:
1 - If I use Asterisk 1.6.0b2 o b4 and a fax is received from a FXO
Card and this FXO port is
Dear All,
Are you telling me Asterisk 1.6.0b2/4 has support for t38 and rxfax etc.
and will be able to receive faxes and negotiate with voip CPE's like
ATA's to transmit faxes which comes from FXO cards to VoIP Devices using
T38 ? it is possible to compile this version of app_fax to work with
On Mon, Feb 25, 2008 at 05:32:24PM -0300, Fernando Berretta wrote:
Dear All,
Are you telling me Asterisk 1.6.0b2/4 has support for t38 and rxfax etc.
and will be able to receive faxes and negotiate with voip CPE's like
ATA's to transmit faxes which comes from FXO cards to VoIP Devices
On Sun, Feb 24, 2008 at 04:35:35PM +1100, Rob Hillis wrote:
Your original comment was that you cannot use T.38 and G.729 in Asterisk
at the same time. On a technical level, this is /not/ true, especially
if the T.38 implementation does not rely on SpanDSP. (whether or not
such an
Rob Hillis wrote:
T.38 is for all intents and purposes a codec. It's purpose is to
re-encode a fax transmission as a data stream to be re-assembled at
the other end as if it were a fax call. Seems to me to be pretty
close to the definition of a codec to me.
T.38 is not a simple
Tzafrir Cohen wrote:
I'm also curious as to why you assert that using G.729 in Asterisk
(/not/ ABE) at the same time as a T.38 implementation that relies on
SpanDSP since these are two completely separate plugins that are
installed and acquired separately.
They are not installed
On Sun, Feb 24, 2008 at 08:25:15PM +1100, Rob Hillis wrote:
Tzafrir Cohen wrote:
I'm also curious as to why you assert that using G.729 in Asterisk
(/not/ ABE) at the same time as a T.38 implementation that relies on
SpanDSP since these are two completely separate plugins that are
Tzafrir Cohen wrote:
On Sun, Feb 24, 2008 at 08:25:15PM +1100, Rob Hillis wrote:
To my mind, this is a ridiculous situation and needlessly limiting. It
goes from the ridiculous IP extremes of companies such as Microsoft to
the other end of the scale.
IP is the Internet Protocol. We're
Steve Underwood [EMAIL PROTECTED] writes:
Try reading the GPL and the FSF's interpretation of it. If things are
running in the same address space as my code, they need to be GPL
compatible, or I am likely to take action.
The GPL is not an EULA. You don't have to agree to it to use the
T.38 is a codec in exactly the same way that GSM or G.729 is a codec, so
yes it /can/ be used at the same time as any other codec - just that
only /one/ codec will be used at a time. What often happens is that the
call will initially be established with a codec such as G.729 or G.711a,
but once
Will the built-in T.38 support eliminate the need for spandsp? I'm curious
how this will affect iaxmodem.
MD
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob Hillis
Sent: Saturday, February 23, 2008 7:12 AM
To: Asterisk Users List
Subject: Re: [asterisk-users] FXO
T.38 is not a codec. A codec has one input and one output. T.38 is an
interactive protocol. This, however, has nothing to do with what I said.
If you use G.729 in the same asterisk as my spandsp library, you are
breaking my licence conditions.
Steve
Rob Hillis wrote:
T.38 is a codec in
Steve Underwood wrote:
I thought * was still not capable for T.38 gateway operation. Doesn't
beta 4 just added T.38 termination? And, I believe it misses out some
key elements of doing that properly. Note that T.38 termination is an
addon, so it can't be used with, say, G.729.
The only
Michelle Dupuis wrote:
Will the built-in T.38 support eliminate the need for spandsp? I'm
curious how this will affect iaxmodem.
Why on earth would you want to eliminiate spandsp? (which app_fax from
asterisk addons appears to use).
___
--
Steve Underwood wrote:
T.38 is not a codec. A codec has one input and one output. T.38 is an
interactive protocol. This, however, has nothing to do with what I said.
If you use G.729 in the same asterisk as my spandsp library, you are
breaking my licence conditions.
Steve
I should hope
I think you are missing something.
Steve means that since its in add-ons its probably a GPL addition and
not compatible with the g729 licensing.
A t.38 gateway involves more than origination and termination, those 2
are pretty easy and do not involve any modems, the gatewaying is the
harder
Users List
Subject: Re: [asterisk-users] FXO Cards - T38
Michelle Dupuis wrote:
Will the built-in T.38 support eliminate the need for spandsp? I'm
curious how this will affect iaxmodem.
Why on earth would you want to eliminiate spandsp? (which
app_fax from asterisk addons appears
Michelle Dupuis wrote:
Wow, an answer phrased in the form of a flame...
A more supportive tone might actually encourage the Asterisk userbase to
grow!
Okay, if you really want a more constructive answer.
The addition to asterisk was an API change to allow app_fax from
asterisk-addons to
About the only reason for eliminating SpanDSP is compatibility with the
GPL license. Remember that /any/ feature added to the free version of
Asterisk is going to be added to ABE as well - ergo, the licensing of
any libraries required need to be compatible with a /non/-open source
license.
T.38 is for all intents and purposes a codec. It's purpose is to
re-encode a fax transmission as a data stream to be re-assembled at the
other end as if it were a fax call. Seems to me to be pretty close to
the definition of a codec to me.
Your original comment was that you cannot use T.38 and
Not unless you're running CallWeaver or Asterisk 1.6.0-beta4. Asterisk
has had passthrough support for T.38 for a while (somewhere in 1.4 it
became available IIRC) but is currently completely incapable of
terminating or encoding a fax call to T.38.
The only real option available at the moment
Rob Hillis wrote:
Not unless you're running CallWeaver or Asterisk 1.6.0-beta4. Asterisk
has had passthrough support for T.38 for a while (somewhere in 1.4 it
became available IIRC) but is currently completely incapable of
terminating or encoding a fax call to T.38.
I thought * was
29 matches
Mail list logo
