Hi all,
After a long time having no time, I have finally done some fresh work on
my software fax machine. I have replaced the original carrier tracking
with something more robust. I have also added 4800, and 2400 bits per
second modes, and cleaned up a few bugs in areas like superfine mode
operation. I apologise for this update taking so long.
At ftp://ftp.opencall.org/pub/spandsp you will find a new version of the
software. You will need TIFF version 5.5.7 or later installed on your
machine. Make sure no earlier version is there - they seem to cause
crashes. Depending how TIFF has been installed on your machine, you may
need to copy the header files, tif_dir.h and tiffiop.h, which you can on
my FTP site, to your /usr/include directory (some systems seem to
install these, and some do not - spandsp needs them installed to build).
The spandsp library may be built by unpacking the tarball, cd'ing to the
directory and using the time honoured incantation:
./configure
make
make install
or if you are using RedHat, Fedora, or something else that uses RPMs
rpmbuild -tb spandsp-0.0.1.tar.gz
should build spandsp RPMs straight from the tar file. Then you just need
to install them.
Add the files rxfax.c, txfax.c and dtmftotext.c (the last one has
nothing to do with the fax machine, but my makefile patch expects it to
be present) to the apps directory of your * source tree. Then use
Makefile.patch to patch the makefile in the apps directory with:
patch < Makefile.patch
Now if you rebuild and install * it should install these new apps.
OK, so how do you use them? Something like the following:
exten => 5678,1,rxfax(/home/steveu/testfax.tif)
will receive a fax if a fax machine dials 5678. The fax will be stored
as the /home/steveu/testfax.tif. Similarly:
exten => 6789,1,txfax(/home/steveu/testfax.tif)
will send the fax file /home/steveu/testfax.tif, when a fax machine
dials 6789.
Regards,
Steve
Hi all, I should have said you will need TIFF version 3.5.7 or later installed on your machine. 5.5.7 or later is a mistake. Regards, Steve
Dear Steve
I have try your very nice app for * but i have found the problem (see
down) when i receive a fax to extension, can you give some more info about
it?
Another question how can i send a fax to a specified number?
Thanks in advance
Dimitri
--------------------------------------------------------------------------------------------------------------
CLI> -- Starting simple switch on 'Zap/33-1'
-- Executing RxFAX("Zap/33-1", "/home/user/testfax.tif")
in new stack
Changed from phase 0 to 1
Slow carrier up
Slow carrier down
Slow carrier up
Slow carrier down
Start receiving document
Changed from phase 1 to 4
Sending ident>>> CSI: 40 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
DIS:
Preferred octets: 256
Can receive fax
Supported data signalling rates: V.27ter and V.29
R8x7.7lines/mm and/or 200x200pels/25.4mm OK
2D coding OK
Scan line length: 215mm
Recording length: A4 (297mm)
Receiver's minimum scan line time: 0ms at 3.85 l/mm: T7.7 = T3.85
R8x15.4lines/mm OK
Minimum scan line time for higher resolutions: T15.4 =
T7.7>>> DIS: 80 00 ce f0 80 80 01
HDLC underflow in state 9
Changed from phase 4 to 3
Slow carrier up
<<< TSI: 43 37 30 38 30 35 33 31 33 33 30 20 20 20 20 20 20 20 20 20 20
TSI without final frame tag
Remote fax gave TSI as: "0331350807"
<<< DCS: 83 00 86 a0 00
DCS with final frame tag
In state 9
DCS:
Can receive fax
Selected data signalling rate: V.29, 9600bps
2D coding OK
Scan line length: 215mm
Recording length: A4 (297mm)
Minimum scan line time: 10ms
Get at 9600
Changed from phase 3 to 5
Fast carrier up
Coarse carrier frequency 1735.25 (9)
Fast carrier down
Fast carrier up
Coarse carrier frequency 1699.33 (86)
Fast carrier training failed
Fast carrier down
Fast carrier up
Coarse carrier frequency 1700.11 (4915)
Fast carrier down
Fast carrier up
Coarse carrier frequency 1699.27 (86)
Fast carrier training failed
Fast carrier down
Fast carrier up
Coarse carrier frequency 1700.09 (4914)
Fast carrier down
Fast carrier up
Coarse carrier frequency 1699.28 (86)
Fast carrier training failed
Fast carrier down
Fast carrier up
Coarse carrier frequency 1700.11 (2925)
Fast carrier down
-- Executing Hangup("Zap/33-1", "") in new stack
== Spawn extension (local, h, 1) exited non-zero on 'Zap/33-1'
-- Hungup 'Zap/33-1'
------------------------------------------------------------------------------------
On Tuesday 16 March 2004 15:00, Steve Underwood wrote:> Hi all,
>
> After a long time having no time, I have finally done some fresh work on
> my software fax machine. I have replaced the original carrier tracking
> with something more robust. I have also added 4800, and 2400 bits per
> second modes, and cleaned up a few bugs in areas like superfine mode
> operation. I apologise for this update taking so long.
>
> At ftp://ftp.opencall.org/pub/spandsp you will find a new version of the
> software. You will need TIFF version 5.5.7 or later installed on your
> machine. Make sure no earlier version is there - they seem to cause
> crashes. Depending how TIFF has been installed on your machine, you may
> need to copy the header files, tif_dir.h and tiffiop.h, which you can on
> my FTP site, to your /usr/include directory (some systems seem to
> install these, and some do not - spandsp needs them installed to build).
> The spandsp library may be built by unpacking the tarball, cd'ing to
the
> directory and using the time honoured incantation:
>
> ./configure
> make
> make install
>
> or if you are using RedHat, Fedora, or something else that uses RPMs
>
> rpmbuild -tb spandsp-0.0.1.tar.gz
>
> should build spandsp RPMs straight from the tar file. Then you just need
> to install them.
>
> Add the files rxfax.c, txfax.c and dtmftotext.c (the last one has
> nothing to do with the fax machine, but my makefile patch expects it to
> be present) to the apps directory of your * source tree. Then use
> Makefile.patch to patch the makefile in the apps directory with:
>
> patch < Makefile.patch
>
> Now if you rebuild and install * it should install these new apps.
>
> OK, so how do you use them? Something like the following:
>
> exten => 5678,1,rxfax(/home/steveu/testfax.tif)
>
> will receive a fax if a fax machine dials 5678. The fax will be stored
> as the /home/steveu/testfax.tif. Similarly:
>
> exten => 6789,1,txfax(/home/steveu/testfax.tif)
>
> will send the fax file /home/steveu/testfax.tif, when a fax machine
> dials 6789.
>
> Regards,
> Steve
>
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
Hi,
Can we do anything about this:
-- Executing RxFAX("Zap/38-1", "/usr/tmp/nativefax.tif")
in new stack
Changed from phase 0 to 1
Slow carrier up
Slow carrier down
Slow carrier up
Slow carrier down
Start receiving document
Changed from phase 1 to 4
Sending ident>>> CSI: 40 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
DIS:
Preferred octets: 256
Can receive fax
Supported data signalling rates: V.27ter and V.29
R8x7.7lines/mm and/or 200x200pels/25.4mm OK
2D coding OK
Scan line length: 215mm
Recording length: A4 (297mm)
Receiver's minimum scan line time: 0ms at 3.85 l/mm: T7.7 = T3.85
R8x15.4lines/mm OK
Minimum scan line time for higher resolutions: T15.4 =
T7.7>>> DIS: 80 00 ce f0 80 80 01
HDLC underflow in state 9
Changed from phase 4 to 3
Slow carrier up
<<< TSI: 43 4e 49 42 55 52 41 5a 20 58 45 4c 41 20 20 20 20 20 20 20 20
TSI without final frame tag
Remote fax gave TSI as: "ALEX ZARUBIN"
<<< DCS: 83 00 c6 70
DCS with final frame tag
In state 9
DCS:
Can receive fax
Selected data signalling rate: V.29, 9600bps
R8x7.7lines/mm and/or 200x200pels/25.4mm OK
2D coding OK
In state 9
DCS:
Can receive fax
Selected data signalling rate: V.29, 9600bps
R8x7.7lines/mm and/or 200x200pels/25.4mm OK
2D coding OK
Scan line length: 215mm
Recording length: A4 (297mm)
Minimum scan line time: 0ms
Get at 9600
Changed from phase 3 to 5
Fast carrier up
Fast carrier down
Fast carrier up
Fast carrier training failed
Fast carrier down
Fast carrier up
Fast carrier down
Fast carrier up
Fast carrier training failed
Fast carrier down
Fast carrier up
Fast carrier down
Fast carrier up
Fast carrier training failed
Fast carrier down
Fast carrier up
Fast carrier down
Coarse carrier frequency 1641.42 (4)
Coarse carrier frequency 1701.47 (71)
Coarse carrier frequency 1707.12 (73)
Coarse carrier frequency 1699.87 (4520)
Coarse carrier frequency 1700.98 (74)
Coarse carrier frequency 1699.83 (2934)
^M -- Channel 13, span 2 got hangup
[03/17/04 18:22:12.369] DEBUG[491546]: File app_rxfax.c, Line 200
(rxfax_exec): Got hangup
Thank you.
Alex Zarubin
Webley Systems
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20040317/b10eb08a/attachment.htm
Hi all,
It seems this week's release of spandsp fixed the major problems in the
previous release, but still people have had a lot of trouble. Working
with some of those who tried the software and gave me good feedback, I
have identified some apparently common bugs in fax machines, and I have
implemented workarounds for these in spandsp, and feedback so far seems
good. I also fixed a couple of bugs. I think this version will work
proper with a much wider range of fax machines. However, people have
warning me that fax machines have a bad habit of not following the specs
properly :-(
There is now a new tarball at
ftp://ftp.opencall.org/pub/spandsp/spandsp-0.0.1b.tar.gz Please try
this, and report any problems you find. This version has the following
changes:
A floating point exception has been fixed
A problem with the software not properly
Some fax machines send a little less than the specified 1.5 seconds
of training test data, so the training test failed every time. I now
only look for 1.25seconds of training test data.
Some fax machines do not correctly initialise the scrambler in their
V.29 transmit modem. I have changed the software to tolerate this.
Some fax machines send a burst of ones before the burst of zeros
that forms the training test data. I have changed the software to
tolerate this.
Regards,
Steve
Hi Steve. On Thu, 18 Mar 2004 22:06:46 +0800 Steve Underwood <steveu@coppice.org> wrote: snip> There is now a new tarball at > ftp://ftp.opencall.org/pub/spandsp/spandsp-0.0.1b.tar.gz Please try > this, and report any problems you find. This version has the following > changes: > > A floating point exception has been fixed > A problem with the software not properly > Some fax machines send a little less than the specified 1.5 seconds > of training test data, so the training test failed every time. I now > only look for 1.25seconds of training test data. > Some fax machines do not correctly initialise the scrambler in their > V.29 transmit modem. I have changed the software to tolerate this. > Some fax machines send a burst of ones before the burst of zeros > that forms the training test data. I have changed the software to > tolerate this.Many thanks for your great release !!!! rxfax function is works well with my Canon MFC Multipass B-30!! mack_jpn
On 2004.03.18 06:06 Steve Underwood wrote:> Some fax machines send a little less than the specified 1.5 > seconds of training test data, so the training test failed every > time. I now only look for 1.25seconds of training test data.You may even have to go as low as 1.00 sec., by the way.> Some fax machines do not correctly initialise the scrambler in > their V.29 transmit modem. I have changed the software to tolerate > this.This is probably off-topic on-list (feel free to respond privately), but can you elaborate?> Some fax machines send a burst of ones before the burst of zeros > that forms the training test data.This is actually quite normal. And in the case of a Class 1 transmitter, it is virtually impossible to avoid. For example, a DTE using a Class 1 modem can send TCF by issuing the AT+FTM=145 followed by the transmission of the requisite zero-fill as soon as the CONNECT response is received. However, per T.31 spec (8.3.3), the Class 1 modem will already have transmitted a series of consecutive 1s before the 0s begin. I know of no way to avoid this. Lee.
Hi,
This week's spandsp release is a big step ahead, there are no problems
so far receiving faxes from our HP OfficeJet R80xi and Panafax UF-560.
Still, we cannot get anything from our Dialogic fax boards. It goes like
this:
-- Executing RxFAX("Zap/42-1", "/usr/tmp/nativefax.tif")
in new stack
Changed from phase 0 to 1
Slow carrier up
[03/18/04 11:48:05.886] DEBUG[442394]: File chan_zap.c, Line 3332
(zt_exception): Exception on 57, channel 42
[03/18/04 11:48:05.886] DEBUG[442394]: File chan_zap.c, Line 2753
(zt_handle_event): Got event No event(0) on channe
l 42 (index 0)
[03/18/04 11:48:05.886] DEBUG[442394]: File chan_zap.c, Line 3234
(zt_handle_event): Dunno what to do with event 0 o
n channel 42
Slow carrier down
Slow carrier up
Slow carrier down
Start receiving document
Changed from phase 1 to 4
Sending ident>>> CSI: 40 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
DIS:
Preferred octets: 256
Can receive fax
Supported data signalling rates: V.27ter and V.29
R8x7.7lines/mm and/or 200x200pels/25.4mm OK
2D coding OK
Scan line length: 215mm
Recording length: A4 (297mm)
Receiver's minimum scan line time: 0ms at 3.85 l/mm: T7.7 = T3.85
R8x15.4lines/mm OK
Minimum scan line time for higher resolutions: T15.4 =
T7.7>>> DIS: 80 00 ce f0 80 80 01
HDLC underflow in state 9
Changed from phase 4 to 3
Slow carrier up
<<< TSI: 43 4e 49 42 55 52 41 5a 20 58 45 4c 41 20 20 20 20 20 20 20 20
TSI without final frame tag
Remote fax gave TSI as: "ALEX ZARUBIN"
<<< DCS: 83 00 c6 70
DCS with final frame tag
In state 9
DCS:
Can receive fax
Selected data signalling rate: V.29, 9600bps
R8x7.7lines/mm and/or 200x200pels/25.4mm OK
2D coding OK
Scan line length: 215mm
Recording length: A4 (297mm)
Minimum scan line time: 0ms
Get at 9600
Changed from phase 3 to 5
Fast carrier up
Coarse carrier frequency 1656.15 (8)
Fast carrier down
0 bad bits in trainability test>>> FTT: 44
Fast carrier up
Coarse carrier frequency 1701.02 (74)
Fast carrier training failed
Fast carrier down
0 bad bits in trainability test>>> FTT: 44
Fast carrier up
Coarse carrier frequency 1700.01 (4854)
Fast carrier down
0 bad bits in trainability test>>> FTT: 44
Fast carrier up
Coarse carrier frequency 1701.27 (74)
Fast carrier training failed
Fast carrier down
0 bad bits in trainability test>>> FTT: 44
Fast carrier up
Coarse carrier frequency 1700.08 (4871)
Fast carrier down
0 bad bits in trainability test>>> FTT: 44
Fast carrier up
Coarse carrier frequency 1701.12 (74)
Fast carrier training failed
Fast carrier down
0 bad bits in trainability test>>> FTT: 44
Fast carrier up
Coarse carrier frequency 1699.79 (2940)
Fast carrier down
0 bad bits in trainability test>>> FTT: 44
^M -- Channel 18, span 2 got hangup
[03/18/04 11:48:35.668] DEBUG[442394]: File app_rxfax.c, Line 200
(rxfax_exec): Got hangup
Thank you.
Alex Zarubin
Webley Systems
-----Original Message-----
From: Steve Underwood [mailto:steveu@coppice.org]
Sent: Thursday, March 18, 2004 8:07 AM
To: asterisk-users@lists.digium.com
Subject: [Asterisk-Users] Softfax/spandsp
Hi all,
It seems this week's release of spandsp fixed the major problems in the
previous release, but still people have had a lot of trouble...
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20040318/f7489f6e/attachment.htm
Hi,
We've tried J2 faxing with the newest release of spandsp and found
the same issue as with our own Dialogic based faxing.
Steve, we can fax to your system from our platform and/or J2 if you
think it can help.
Here is what we see on incoming fax from J2:
-- Executing RxFAX("Zap/28-1",
"/usr/tmp/nativefax-from-2132255675-1079649839.tif") in new stack
Changed from phase 0 to 1
Slow carrier up
[03/18/04 16:43:59.245] DEBUG[655386]: File chan_zap.c, Line 3332
(zt_exception): Exception on 43, chann
el 28
[03/18/04 16:43:59.245] DEBUG[655386]: File chan_zap.c, Line 2753
(zt_handle_event): Got event No event(
0) on channel 28 (index 0)
[03/18/04 16:43:59.246] DEBUG[655386]: File chan_zap.c, Line 3234
(zt_handle_event): Dunno what to do wi
th event 0 on channel 28
Slow carrier down
Start receiving document
Changed from phase 1 to 4
Sending ident>>> CSI: 40 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
DIS:
Preferred octets: 256
Can receive fax
Supported data signalling rates: V.27ter and V.29
R8x7.7lines/mm and/or 200x200pels/25.4mm OK
2D coding OK
Scan line length: 215mm
Recording length: A4 (297mm)
Receiver's minimum scan line time: 0ms at 3.85 l/mm: T7.7 = T3.85
R8x15.4lines/mm OK
Minimum scan line time for higher resolutions: T15.4 =
T7.7>>> DIS: 80 00 ce f0 80 80 01
HDLC underflow in state 9
Changed from phase 4 to 3
Slow carrier up
<<< TSI: 43 39 30 34 38 39 31 39 37 34 38 31 20 20 20 20 20 20 20 20 20
TSI without final frame tag
Remote fax gave TSI as: "18479198409"
<<< DCS: 83 00 06 f0 00
DCS with final frame tag
In state 9
DCS:
Can receive fax
Selected data signalling rate: V.29, 9600bps
Scan line length: 215mm
Recording length: A4 (297mm)
Minimum scan line time: 0ms
Get at 9600
Changed from phase 3 to 5
Fast carrier up
Coarse carrier frequency 1709.56 (90)
Fast carrier down
0 bad bits in trainability test>>> FTT: 44
Fast carrier up
Coarse carrier frequency 1702.22 (86)
Fast carrier training failed
Fast carrier down
0 bad bits in trainability test>>> FTT: 44
Fast carrier up
Coarse carrier frequency 1699.93 (5195)
Fast carrier down
0 bad bits in trainability test>>> FTT: 44
Fast carrier up
Coarse carrier frequency 1702.50 (85)
Fast carrier training failed
Fast carrier down
0 bad bits in trainability test>>> FTT: 44
Fast carrier up
Coarse carrier frequency 1699.92 (5195)
Fast carrier down
0 bad bits in trainability test>>> FTT: 44
Fast carrier up
Coarse carrier frequency 1702.55 (85)
Fast carrier training failed
Fast carrier down
0 bad bits in trainability test>>> FTT: 44
Fast carrier up
Coarse carrier frequency 1700.12 (3083)
Fast carrier down
0 bad bits in trainability test>>> FTT: 44
^M -- Channel 4, span 2 got hangup
[03/18/04 16:44:28.468] DEBUG[655386]: File app_rxfax.c, Line 200
(rxfax_exec): Got hangup
Thank you.
Alex Zarubin
Webley Systems
-----Original Message-----
From: Steve Underwood [mailto:steveu@coppice.org]
Sent: Thursday, March 18, 2004 8:07 AM
To: asterisk-users@lists.digium.com
Subject: [Asterisk-Users] Softfax/spandsp
Hi all,
It seems this week's release of spandsp fixed the major problems in the
previous release, but still people have had a lot of trouble...
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20040318/7685db27/attachment.htm
Can anyone decipher these error messages? Mar 18 18:10:21 WARNING[131081]: chan_zap.c:5949 zt_pri_error: PRI: Read on 39 failed: Unknown error 500 Mar 18 18:10:21 NOTICE[131081]: chan_zap.c:6664 pri_dchannel: PRI got event: 6 on span 1 Thanks, TL
Hi todd, same problem for me since yesterday, I solved changinf from span=1,0,0,ccs,hdb3,crc4 to span=1,1,0,ccs,hdb3,crc4 in zaptel.conf The second "1" tells the card to use line as clock source istead of internal timing. Hope it helps ! TL> Can anyone decipher these error messages? TL> Mar 18 18:10:21 WARNING[131081]: chan_zap.c:5949 zt_pri_error: PRI: Read on TL> 39 failed: Unknown error 500 TL> Mar 18 18:10:21 NOTICE[131081]: chan_zap.c:6664 pri_dchannel: PRI got event: TL> 6 on span 1 TL> Thanks, TL TL> _______________________________________________ TL> Asterisk-Users mailing list TL> Asterisk-Users@lists.digium.com TL> http://lists.digium.com/mailman/listinfo/asterisk-users TL> To UNSUBSCRIBE or update options visit: TL> http://lists.digium.com/mailman/listinfo/asterisk-users -- Best regards, Alessio mailto:afoc@interconnessioni.it
Hi, I have received more excellent problem report information, and I have resolved a number of issues affecting my soft FAX machine when working with various models of real FAX machine. The code now seems to be working with a much greater range of fax machines. A problem affecting the reliability of multi-page fax receive has also been corrected. You can get the latest code from ftp://ftp.opencall.org/pub/spandsp/spandsp-0.0.1f.tar.gz The application program ftp://ftp.opencall.org/pub/spandsp/app_rxfax.c has also been updated to remove a redundant variable. After building and installing the latest spandsp, rebuild the asterisk applications, as some data structures have changed. Regards, Steve
Hi all, If you have had trouble with multiple concurrent channels running app_rxfax or ap_txfax, where was a silly bug. Updated versions are available at ftp://ftp.opencall.org/pub/spandsp The latest spandsp-0.0.1f seems to working for quite a lot of people. I guess there will still be plenty more compatibility issues to deal with, though. If you try this software and find reliability problems try checking for frame slips. A single frame slip in the audio stream will kill a fax transfer. This is true for any fax modem, and is not a spandsp issue. Regards, Steve
Hey Steve, On Mon, Mar 22, 2004 at 22:13:37 +0800, Steve Underwood wrote:> Hi all, > > If you have had trouble with multiple concurrent channels running > app_rxfax or ap_txfax, where was a silly bug. Updated versions are > available at ftp://ftp.opencall.org/pub/spandsp > > The latest spandsp-0.0.1f seems to working for quite a lot of people. I > guess there will still be plenty more compatibility issues to deal with, > though. If you try this software and find reliability problems try > checking for frame slips. A single frame slip in the audio stream will > kill a fax transfer. This is true for any fax modem, and is not a > spandsp issue.Just to let you know that this is the first version that has actually worked for me. Previous versions seemed to abort at the beginning of the transfer, no matter what I tried. This one worked out of the box, using the exact same test-setup the earlier version failed in. :-) Grtz, Oliver
Hi,
With the latest release available (spandsp-0.0.1f) we still cannot receive
faxes from Dialogic. There are no problems with several fax machines we've
tried and
it works fine with J2, so it shouldn't be slipping...
-- Executing RxFAX("Zap/26-1",
"/usr/tmp/nativefax-from-8772308094-1079985146.tif") in new stack
Changed from phase 0 to 1
Slow carrier up
[03/22/04 13:52:26.985] DEBUG[507930]: File chan_zap.c, Line 3332
(zt_exception): Exception on 41, channel 26
[03/22/04 13:52:26.985] DEBUG[507930]: File chan_zap.c, Line 2753
(zt_handle_event): Got event No event(0) on channel 26 (index 0)
[03/22/04 13:52:26.985] DEBUG[507930]: File chan_zap.c, Line 3234
(zt_handle_event): Dunno what to do with event 0 on channel 26
Slow carrier down
Slow carrier up
Slow carrier down
Start receiving document
Changed from phase 1 to 4
Sending ident>>> CSI: 40 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
DIS:
Preferred octets: 256
Can receive fax
Supported data signalling rates: V.27ter and V.29
R8x7.7lines/mm and/or 200x200pels/25.4mm OK
2D coding OK
Scan line length: 215mm
Recording length: A4 (297mm)
Receiver's minimum scan line time: 0ms at 3.85 l/mm: T7.7 = T3.85
R8x15.4lines/mm OK
Minimum scan line time for higher resolutions: T15.4 =
T7.7>>> DIS: 80 00 ce f0 80 80 01
HDLC underflow in state 9
Changed from phase 4 to 3
Slow carrier up
<<< TSI: 43 4e 49 42 55 52 41 5a 20 58 45 4c 41 20 20 20 20 20 20 20 20
TSI without final frame tag
Remote fax gave TSI as: "ALEX ZARUBIN"
<<< DCS: 83 00 c6 70
DCS with final frame tag
In state 9
DCS:
Can receive fax
Selected data signalling rate: V.29, 9600bps
R8x7.7lines/mm and/or 200x200pels/25.4mm OK
2D coding OK
Scan line length: 215mm
Recording length: A4 (297mm)
Minimum scan line time: 0ms
Get at 9600
Changed from phase 3 to 5
Fast carrier up
Fast carrier down
0 bad bits in trainability test>>> FTT: 44
Fast carrier up
Coarse carrier frequency 1699.92 (56)
Training failed (only 120 1's)
Fast carrier training failed
Fast carrier down
0 bad bits in trainability test>>> FTT: 44
Fast carrier up
Coarse carrier frequency 1700.14 (4834)
Fast carrier down
0 bad bits in trainability test>>> FTT: 44
0 bad bits in trainability test>>> FTT: 44
Fast carrier up
Coarse carrier frequency 1699.87 (56)
Fast carrier trained
Fast carrier down
27 bad bits in trainability test>>> FTT: 44
Fast carrier up
Coarse carrier frequency 1700.01 (4848)
Fast carrier down
27 bad bits in trainability test>>> FTT: 44
Fast carrier up
Coarse carrier frequency 1699.69 (56)
Training failed (only 114 1's)
Fast carrier training failed
Fast carrier down
27 bad bits in trainability test>>> FTT: 44
Fast carrier up
Coarse carrier frequency 1699.84 (2904)
Fast carrier down
27 bad bits in trainability test>>> FTT: 44
Fast carrier up
Fast carrier down
27 bad bits in trainability test>>> FTT: 44
^M -- Channel 2, span 2 got hangup
[03/22/04 13:52:57.848] DEBUG[507930]: File app_rxfax.c, Line 237
(rxfax_exec): Got hangup
[03/22/04 13:52:57.848] DEBUG[507930]: File pbx.c, Line 1744 (ast_pbx_run):
Extension 8663222818, priority 1 returned normally even though call was hung
up
Thank you.
Alex Zarubin
Webley Systems
-----Original Message-----
From: Steve Underwood [mailto:steveu@coppice.org]
Sent: Monday, March 22, 2004 8:14 AM
To: asterisk-users@lists.digium.com
Subject: [Asterisk-Users] SoftFAX/spandsp
Hi all,
If you have had trouble with multiple concurrent channels running
app_rxfax or ap_txfax, where was a silly bug. Updated versions are
available at ftp://ftp.opencall.org/pub/spandsp
The latest spandsp-0.0.1f seems to working for quite a lot of people. I
guess there will still be plenty more compatibility issues to deal with,
though. If you try this software and find reliability problems try
checking for frame slips. A single frame slip in the audio stream will
kill a fax transfer. This is true for any fax modem, and is not a
spandsp issue.
Regards,
Steve
_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20040322/79ee7ffb/attachment.htm
On Sunday 21 March 2004 07:10, Steve Underwood wrote:> I have received more excellent problem report information, and I > have resolved a number of issues affecting my soft FAX machine when > working with various models of real FAX machine. The code now seems > to be working with a much greater range of fax machines. A problem > affecting the reliability of multi-page fax receive has also been > corrected.You may want to add to the notes that libaudiofile is also apparently required to compile spandsp. I did not see any such note either in the README, INSTALL, or on the website. -Tilghman
Tilghman Lesher wrote:>On Sunday 21 March 2004 07:10, Steve Underwood wrote: > > >>I have received more excellent problem report information, and I >>have resolved a number of issues affecting my soft FAX machine when >>working with various models of real FAX machine. The code now seems >>to be working with a much greater range of fax machines. A problem >>affecting the reliability of multi-page fax receive has also been >>corrected. >> >> > >You may want to add to the notes that libaudiofile is also apparently >required to compile spandsp. I did not see any such note either in >the README, INSTALL, or on the website. > >That should only be required when building the tests. It should not be needed for normal users of the library. Regards, Steve
Hi Steve, We've got VFX/40ESC and VFX/40ESC plus, tried both. Can send faxes from our platform to your system if it helps. After this problem is (hopefully) solved we are going to try FaxLab http://www.qualitylogic.com/genoa_test_tools/fax/faxlab.html Do you know of newer/better tools? Thank you. Alex Zarubin Webley Systems -----Original Message----- From: Steve Underwood [mailto:steveu@coppice.org] Sent: Monday, March 22, 2004 6:29 PM To: asterisk-users@lists.digium.com Subject: Re: [Asterisk-Users] SoftFAX/spandsp Hi Alex, Which Dialogic hardware are you using? I have a VFX41/ESC, but I have not tried faxing to spandsp with it. I will try it. A lot of the problems I have had in the last week are with FAX machines that do not obey the spec properly. I expect this is one. Regards, Steve Alex Zarubin wrote:> Hi, > > With the latest release available (spandsp-0.0.1f) we still cannot > receive > faxes from Dialogic. There are no problems with several fax machines > we've tried and > it works fine with J2, so it shouldn't be slipping... > > -- Executing RxFAX("Zap/26-1", > "/usr/tmp/nativefax-from-8772308094-1079985146.tif") in new stack > Changed from phase 0 to 1 > Slow carrier up > [03/22/04 13:52:26.985] DEBUG[507930]: File chan_zap.c, Line 3332 > (zt_exception): Exception on 41, channel 26 > [03/22/04 13:52:26.985] DEBUG[507930]: File chan_zap.c, Line 2753 > (zt_handle_event): Got event No event(0) on channel 26 (index 0) > > [03/22/04 13:52:26.985] DEBUG[507930]: File chan_zap.c, Line 3234 > (zt_handle_event): Dunno what to do with event 0 on channel 26 > > Slow carrier down > Slow carrier up > Slow carrier down > Start receiving document > Changed from phase 1 to 4 > Sending ident > >>> CSI: 40 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 > DIS: > Preferred octets: 256 > Can receive fax > Supported data signalling rates: V.27ter and V.29 > R8x7.7lines/mm and/or 200x200pels/25.4mm OK > 2D coding OK > Scan line length: 215mm > Recording length: A4 (297mm) > Receiver's minimum scan line time: 0ms at 3.85 l/mm: T7.7 = T3.85 > R8x15.4lines/mm OK > Minimum scan line time for higher resolutions: T15.4 = T7.7 > >>> DIS: 80 00 ce f0 80 80 01 > HDLC underflow in state 9 > Changed from phase 4 to 3 > Slow carrier up > <<< TSI: 43 4e 49 42 55 52 41 5a 20 58 45 4c 41 20 20 20 20 20 20 20 20 > TSI without final frame tag > Remote fax gave TSI as: "ALEX ZARUBIN" > <<< DCS: 83 00 c6 70 > DCS with final frame tag > In state 9 > DCS: > Can receive fax > Selected data signalling rate: V.29, 9600bps > R8x7.7lines/mm and/or 200x200pels/25.4mm OK > 2D coding OK > Scan line length: 215mm > Recording length: A4 (297mm) > Minimum scan line time: 0ms > Get at 9600 > Changed from phase 3 to 5 > Fast carrier up > Fast carrier down > 0 bad bits in trainability test > >>> FTT: 44 > Fast carrier up > Coarse carrier frequency 1699.92 (56) > Training failed (only 120 1's) > Fast carrier training failed > Fast carrier down > 0 bad bits in trainability test > >>> FTT: 44 > Fast carrier up > Coarse carrier frequency 1700.14 (4834) > Fast carrier down > 0 bad bits in trainability test > >>> FTT: 44 > 0 bad bits in trainability test > >>> FTT: 44 > Fast carrier up > Coarse carrier frequency 1699.87 (56) > Fast carrier trained > Fast carrier down > 27 bad bits in trainability test > >>> FTT: 44 > Fast carrier up > Coarse carrier frequency 1700.01 (4848) > Fast carrier down > 27 bad bits in trainability test > >>> FTT: 44 > Fast carrier up > Coarse carrier frequency 1699.69 (56) > Training failed (only 114 1's) > Fast carrier training failed > Fast carrier down > 27 bad bits in trainability test > >>> FTT: 44 > Fast carrier up > Coarse carrier frequency 1699.84 (2904) > Fast carrier down > 27 bad bits in trainability test > >>> FTT: 44 > Fast carrier up > Fast carrier down > 27 bad bits in trainability test > >>> FTT: 44 > ^M -- Channel 2, span 2 got hangup > [03/22/04 13:52:57.848] DEBUG[507930]: File app_rxfax.c, Line 237 > (rxfax_exec): Got hangup > [03/22/04 13:52:57.848] DEBUG[507930]: File pbx.c, Line 1744 > (ast_pbx_run): Extension 8663222818, priority 1 returned normally even > though call was hung up > > Thank you. > > Alex Zarubin > Webley Systems > > > -----Original Message----- > From: Steve Underwood [mailto:steveu@coppice.org] > Sent: Monday, March 22, 2004 8:14 AM > To: asterisk-users@lists.digium.com > Subject: [Asterisk-Users] SoftFAX/spandsp > > > Hi all, > > If you have had trouble with multiple concurrent channels running > app_rxfax or ap_txfax, where was a silly bug. Updated versions are > available at ftp://ftp.opencall.org/pub/spandsp > > The latest spandsp-0.0.1f seems to working for quite a lot of people. I > guess there will still be plenty more compatibility issues to deal with, > though. If you try this software and find reliability problems try > checking for frame slips. A single frame slip in the audio stream will > kill a fax transfer. This is true for any fax modem, and is not a > spandsp issue. > > Regards, > Steve >_______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20040322/841de8f4/attachment.htm
Hi all, My SoftFAX is now up to spandsp-0.0.1h.tar.gz. This version has a number of changes in the way the V.29 modem works. It also has some missing functionality in the T.30 implementation filled in - it was not handling EOM messages. The previous version failed for several reasons with a Dialogic VFX/40ESC. This version succeeds, although it still seems to get a few bit errors, giving some flaws on the received image. I do not see these errors with the other FAX machines I have tried. It seems like a fairly big improvement though, and work will continue to make it better. app_rxfax.c and app_txfax.c have gained a new feature. Previously they always started in answering party mode. Now this is the default behaviour, but something like: exten => 5678,1,txfax(/tmp/testfax.tif|caller) will make them start in calling party mode. So far, these two apps have been little more that testbeds for spandsp. It seems some people are trying to use them for real work, so it seems like they should be gaining more features. The caller mode option was asked for. Regards, Steve
Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: 6018.txt.gz Type: application/octet-stream Size: 2136 bytes Desc: not available Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20040325/4cdc47b5/6018.txt.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: 6020.txt.gz Type: application/octet-stream Size: 1575 bytes Desc: not available Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20040325/4cdc47b5/6020.txt.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: J2-Fine.txt.gz Type: application/octet-stream Size: 1994 bytes Desc: not available Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20040325/4cdc47b5/J2-Fine.txt.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: J2-regular.txt.gz Type: application/octet-stream Size: 1620 bytes Desc: not available Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20040325/4cdc47b5/J2-regular.txt.obj
Excellent work Steve. -----Original Message----- From: asterisk-users-admin@lists.digium.com [mailto:asterisk-users-admin@lists.digium.com] On Behalf Of Steve Underwood Sent: Thursday, March 25, 2004 10:34 AM To: asterisk-users@lists.digium.com Subject: [Asterisk-Users] SoftFAX/spandsp Hi all, My SoftFAX is now up to spandsp-0.0.1h.tar.gz. This version has a number of changes in the way the V.29 modem works. It also has some missing functionality in the T.30 implementation filled in - it was not handling EOM messages. The previous version failed for several reasons with a Dialogic VFX/40ESC. This version succeeds, although it still seems to get a few bit errors, giving some flaws on the received image. I do not see these errors with the other FAX machines I have tried. It seems like a fairly big improvement though, and work will continue to make it better. app_rxfax.c and app_txfax.c have gained a new feature. Previously they always started in answering party mode. Now this is the default behaviour, but something like: exten => 5678,1,txfax(/tmp/testfax.tif|caller) will make them start in calling party mode. So far, these two apps have been little more that testbeds for spandsp. It seems some people are trying to use them for real work, so it seems like they should be gaining more features. The caller mode option was asked for. Regards, Steve _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Hi,
I've been testing the soft fax but I am getting this segmentation fault
whenever I receive a fax. Can somebody help me please?
I've loaded asterisk from CVS and running Redhat 9.0 and downloaded the
latest spandsp. I am sending a fax from Windows XP fax software thru a
ringmaster then to X100P.
WindowsXP --> modem ---> ringmaster (CO simulator) ---> X100P ---> *
== Spawn extension (prepaid, fax, 0) exited non-zero on 'Zap/1-1'
-- Executing RxFAX("Zap/1-1", "/root/test.tiff") in new
stack
Changed from phase 0 to 1
Slow carrier up
Slow carrier down
Slow carrier up
Slow carrier down
Slow carrier up
Slow carrier down
Slow carrier up
Slow carrier down
Slow carrier up
Slow carrier down
Slow carrier up
Slow carrier down
Slow carrier up
Slow carrier down
Start receiving document
Changed from phase 1 to 4
Sending ident>>> CSI: 40 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
DIS:
Preferred octets: 256
Can receive fax
Supported data signalling rates: V.27ter and V.29
R8x7.7lines/mm and/or 200x200pels/25.4mm OK
2D coding OK
Scan line length: 215mm
Recording length: A4 (297mm)
Receiver's minimum scan line time: 0ms at 3.85 l/mm: T7.7 = T3.85
R8x15.4lines/mm OK
Minimum scan line time for higher resolutions: T15.4 =
T7.7>>> DIS: 80 00 ce f0 80 80 01
HDLC underflow in state 9
Changed from phase 4 to 3
Slow carrier up
<<< TSI: 43 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 78 61 46
TSI without final frame tag
Remote fax gave TSI as: "Fax "
<<< DCS: 83 00 c6 70
DCS with final frame tag
In state 9
DCS:
Can receive fax
Selected data signalling rate: V.29, 9600bps
R8x7.7lines/mm and/or 200x200pels/25.4mm OK
2D coding OK
Scan line length: 215mm
Recording length: A4 (297mm)
Minimum scan line time: 0ms
Get at 9600
Changed from phase 3 to 5
Fast carrier up
Coarse carrier frequency 1683.64 (18)
Fast carrier down
Trainability test failed - longest run of zeros test was
0>>> FTT: 44
Fast carrier up
Coarse carrier frequency 1699.71 (64)
Training error 9.552597
Training succeeded (constellation mismatch 11.776280)
Fast carrier trained
Fast carrier down
Changed from phase 5 to 4
Start rx document - compression 2
Start rx page
Segmentation fault
----- Original Message -----
From: <asterisk-users-request@lists.digium.com>
To: <asterisk-users@lists.digium.com>
Sent: Friday, March 26, 2004 1:51 PM
Subject: Asterisk-Users digest, Vol 1 #3229 - 15 msgs
> Send Asterisk-Users mailing list submissions to
> asterisk-users@lists.digium.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.digium.com/mailman/listinfo/asterisk-users
> or, via email, send a message with subject or body 'help' to
> asterisk-users-request@lists.digium.com
>
> You can reach the person managing the list at
> asterisk-users-admin@lists.digium.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Asterisk-Users digest..."
>
>
> Today's Topics:
>
> 1. Re: IAX2 International Termination (Robert Sprockeels)
> 2. RE: SoftFAX/spandsp (Wade J. Weppler)
> 3. G.729 variants and Asterisk (Carlos Chavez)
> 4. Re: G.729 variants and Asterisk (Miguel Cavazos)
> 5. Re: G.729 variants and Asterisk (Adam Hart)
> 6. Re: ATA 182 and * (Leo Ann Boon)
> 7. Re: SoftFAX/spandsp (Eric Wieling)
> 8. Error on * startup (Simon Brown)
> 9. Asterisk (simprix)
> 10. Call & Drop / Call & Tranfer - tranfering a call to a
different
number. (johnc@cleburne.com)> 11. New minor release of Firefly (now with Speex) (Adam Hart)
> 12. Codec Voodoo (Hadar Pedhazur)
> 13. RE: New minor release of Firefly (now with Speex) (Simon Brown)
> 14. Re: SoftFAX/spandsp (Nicolas Gudino)
> 15. IAX drops calls exactly 5 secs into the call ( John Brown (CV))
>
> --__--__--
>
> Message: 1
> Subject: Re: [Asterisk-Users] IAX2 International Termination
> From: Robert Sprockeels <rsp+asterisk@boat.be>
> To: asterisk-users@lists.digium.com
> Date: Thu, 25 Mar 2004 23:42:20 +0100
> Reply-To: asterisk-users@lists.digium.com
>
> Tested from Belgium
>
> Very good quality, sometimes breaking up a little.
>
> The phone I used is a Snom200 behind *, gsm codec.
> Ping times are 110 - 115 ms.
> Did not try dtmf sending.
>
> Robert Sprockeels
>
>
> --__--__--
>
> Message: 2
> Subject: RE: [Asterisk-Users] SoftFAX/spandsp
> Date: Thu, 25 Mar 2004 17:51:31 -0500
> From: "Wade J. Weppler" <weppler@wwworks-inc.com>
> To: <asterisk-users@lists.digium.com>
> Reply-To: asterisk-users@lists.digium.com
>
> Excellent work Steve.
>
> -----Original Message-----
> From: asterisk-users-admin@lists.digium.com
> [mailto:asterisk-users-admin@lists.digium.com] On Behalf Of Steve
> Underwood
> Sent: Thursday, March 25, 2004 10:34 AM
> To: asterisk-users@lists.digium.com
> Subject: [Asterisk-Users] SoftFAX/spandsp
>
> Hi all,
>
> My SoftFAX is now up to spandsp-0.0.1h.tar.gz. This version has a number
>
> of changes in the way the V.29 modem works. It also has some missing=20
> functionality in the T.30 implementation filled in - it was not handling
>
> EOM messages.
>
> The previous version failed for several reasons with a Dialogic=20
> VFX/40ESC. This version succeeds, although it still seems to get a few=20
> bit errors, giving some flaws on the received image. I do not see these=20
> errors with the other FAX machines I have tried. It seems like a fairly=20
> big improvement though, and work will continue to make it better.
>
> app_rxfax.c and app_txfax.c have gained a new feature. Previously they=20
> always started in answering party mode. Now this is the default=20
> behaviour, but something like:
>
> exten =3D> 5678,1,txfax(/tmp/testfax.tif|caller)
>
> will make them start in calling party mode. So far, these two apps have=20
> been little more that testbeds for spandsp. It seems some people are=20
> trying to use them for real work, so it seems like they should be=20
> gaining more features. The caller mode option was asked for.
>
> Regards,
> Steve
>
>
>
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
>
>
>
> --__--__--
>
> Message: 3
> From: "Carlos Chavez" <cursor@corplacer.com>
> To: "Asterisk" <asterisk-users@lists.digium.com>
> Date: Thu, 25 Mar 2004 16:47:55 -0600
> Subject: [Asterisk-Users] G.729 variants and Asterisk
> Reply-To: asterisk-users@lists.digium.com
>
> I see that I can purchase G.729 licenses for my Asterisk server, but
I> have seen that many phones support a G.729 variant like A or B. Are these
> suppoted by the same G.729 codec in Asterisk?
>
> --
> Carlos Chavez
> Computer Engineer, CCNA
> Corporativo Lacer S.A. de C.V.
>
>
> --__--__--
>
> Message: 4
> Subject: Re: [Asterisk-Users] G.729 variants and Asterisk
> From: Miguel Cavazos <miguel@cavazos.com.mx>
> To: Asterisk <asterisk-users@lists.digium.com>
> Date: Thu, 25 Mar 2004 17:00:00 +0000
> Reply-To: asterisk-users@lists.digium.com
>
> si funciona con el A y B
>
> Miguel Cavazos
> On Thu, 2004-03-25 at 22:47, Carlos Chavez wrote:
> > I see that I can purchase G.729 licenses for my Asterisk server,
but I> > have seen that many phones support a G.729 variant like A or B. Are
these> > suppoted by the same G.729 codec in Asterisk?
> >
> > --
> > Carlos Chavez
> > Computer Engineer, CCNA
> > Corporativo Lacer S.A. de C.V.
> >
> > _______________________________________________
> > Asterisk-Users mailing list
> > Asterisk-Users@lists.digium.com
> > http://lists.digium.com/mailman/listinfo/asterisk-users
> > To UNSUBSCRIBE or update options visit:
> > http://lists.digium.com/mailman/listinfo/asterisk-users
>
> --__--__--
>
> Message: 5
> Date: Fri, 26 Mar 2004 10:05:29 +1100
> From: Adam Hart <adam@teragen.com.au>
> To: asterisk-users@lists.digium.com
> Subject: Re: [Asterisk-Users] G.729 variants and Asterisk
> Reply-To: asterisk-users@lists.digium.com
>
> Carlos Chavez wrote:
>
> > I see that I can purchase G.729 licenses for my Asterisk server,
but
I> >have seen that many phones support a G.729 variant like A or B. Are
these> >suppoted by the same G.729 codec in Asterisk?
> >
> >
> B is just the fixed point version of A (from memory) - so it works the
> same as A.
>
> A is a reduced complexity version of G.729 - although they both work
> with each other. A is just slack when looking for the best
> representation of your voice.
>
> FYI, Digium's codec is G.729A, although it makes little difference
>
> --__--__--
>
> Message: 6
> Date: Fri, 26 Mar 2004 07:15:08 +0800
> From: Leo Ann Boon <leo@innovax.com.sg>
> To: asterisk-users@lists.digium.com
> Subject: Re: [Asterisk-Users] ATA 182 and *
> Reply-To: asterisk-users@lists.digium.com
>
> No. The FXO on the 182 is only usable from the box itself. It's for
> calling local numbers.
>
> Erick Weber V. wrote:
>
> >Hi to everyone:
> >
> >Does someone know if the ATA 182 works OK with asterisk or should I get
a
> >HandyTone 486 instade or an ATA 186 and a FXS to FXO converter
> >
> >Thanks
> >
> >Erick
> >
> >
> >_______________________________________________
> >Asterisk-Users mailing list
> >Asterisk-Users@lists.digium.com
> >http://lists.digium.com/mailman/listinfo/asterisk-users
> >To UNSUBSCRIBE or update options visit:
> > http://lists.digium.com/mailman/listinfo/asterisk-users
> >
> >
> >
>
> --__--__--
>
> Message: 7
> Subject: Re: [Asterisk-Users] SoftFAX/spandsp
> From: Eric Wieling <eric@fnords.org>
> To: asterisk-users@lists.digium.com
> Organization: BTEL Consulting
> Date: Thu, 25 Mar 2004 18:19:10 -0600
> Reply-To: asterisk-users@lists.digium.com
>
> On Thu, 2004-03-25 at 09:33, Steve Underwood wrote:
> > exten => 5678,1,txfax(/tmp/testfax.tif|caller)
>
> There are a zillion fax and tiff formats. I'm trying to figure out
what
> output format I should tell GhostScript to use. Any suggestions on
> which format to try?
>
> These are the formats GhostScript can output:
>
> faxg3 faxg32d faxg4 tiff12nc tiff24nc tiffcrle tiffg3 tiffg32d tiffg4
> tifflzw tiffpack
>
> --
> Eric Wieling <eric@fnords.org>
> BTEL Consulting
>
>
> --__--__--
>
> Message: 8
> Date: Fri, 26 Mar 2004 11:19:25 +1100
> From: "Simon Brown" <Simon.Brown@otterson.com.au>
> To: <asterisk-users@lists.digium.com>
> Subject: [Asterisk-Users] Error on * startup
> Reply-To: asterisk-users@lists.digium.com
>
> When I start or reload * I always get this error (once).
> Can someone point me in the right direction to fix this.
>
> WARNING[1150495040]: chan_sip.c:495 retrans_pkt: Maximum retries >
exceeded on
> call 3c52718c594f43736b88cb4b5ec8af65@10.2.2.20 for seqno 102 (request)
>
> Simon
>
> -----
> This mail was content checked for malicious code and viruses
> by GFI MailSecurity.
>
>
> --__--__--
>
> Message: 9
> Date: Thu, 25 Mar 2004 19:29:12 -0500
> From: simprix <simprix@simprix.net>
> To: <asterisk-users@lists.digium.com>
> Subject: [Asterisk-Users] Asterisk
> Reply-To: asterisk-users@lists.digium.com
>
> What kind of specs do I need for a asterisk box that will have a pri for
> pstn and about 65 sip phones
>
> I was thinking a Xeon 3.05
>
>
>
> --__--__--
>
> Message: 10
> From: johnc@cleburne.com
> To: asterisk-users@lists.digium.com
> Date: Thu, 25 Mar 2004 18:38:47 -0600
> Subject: [Asterisk-Users] Call & Drop / Call & Tranfer - tranfering
a call
to a different number.> Reply-To: asterisk-users@lists.digium.com
>
> First, I am very new to this software. If I missed a searchable archive,
please point> me in the right direction.
>
> I am wishing to know if Asterisk can be used to do a Call & Drop
scenario.
>
> This is where someone calls, Asterisk answers, ask for the number that the
person> wishes to dial, gets the PIN, and then completes the call to the number
they desired.> Once the connection is completed, this software/service is no longer in
the call loop.>
> Typically this scenario is used to offer a wider calling area. Called
Metro or Extended> Metro in our area. There are many people in area that this feature is not
available> from their phone company, or they don't want to pay much for it, as
they
don't make> many calls.
>
> I am certainly willing to provide more information, but I wanted to find
out if Asterisk> was even something that could do it- or be modified to do so.
>
> Thanks,
>
> John Chapman
>
> --__--__--
>
> Message: 11
> Date: Fri, 26 Mar 2004 11:47:40 +1100
> From: Adam Hart <adam@teragen.com.au>
> To: "asterisk-users@lists.digium.com"
<asterisk-users@lists.digium.com>
> Subject: [Asterisk-Users] New minor release of Firefly (now with Speex)
> Reply-To: asterisk-users@lists.digium.com
>
> I've put up a new dev version of Firefly
> (http://www.virbiage.com/firefly/download/firefly-dev.exe)
>
> Notable Changes:
> DTMF now works with SIP
> Speex codec has been added
> 1 crash bug fixed - 2 more to go (if you can crash Firefly, send me the
> Hex address - probably stored in event viewer under control panel)
>
> Sorry for the delay but I've completely rewritten how contacts work
> internally (although it looks exactly the same as it did before). This
> now allows me to do some sexy things with contacts. Stay tuned
>
> I'm aiming for a stable release in two weeks so help me find the bugs.
> Many thanks to thoses who have
>
> -Adam
>
> --__--__--
>
> Message: 12
> Date: Thu, 25 Mar 2004 20:08:38 -0500
> From: Hadar Pedhazur <hadar@unorthodox.com>
> To: Asterisk-Users@lists.digium.com
> Subject: [Asterisk-Users] Codec Voodoo
> Reply-To: asterisk-users@lists.digium.com
>
> I have three * servers that all talk to each just fine, and
> all talk to other * servers (like NuFone, VoicePulse, etc.).
> I have hard-phones connected to Sipura SPA-2000s on two of
> the * servers via a local network connection. The third *
> server only gets connected to remotely, both with IAX and
> SIP softphones, and with a "roaming" Sipura with
> hard-phones.
>
> The setup works well. All of the * servers communicate
> exclusively with GSM between themselves (and also to NuFone
> and VoicePulse). The quality is pretty good. The "local"
> hard phones are using g711 uLaw (since I think that the X100P
> cards I believe use uLaw by default as well, but I could be
> way off on that assumption). Codec transcoding from uLaw to
> GSM seems to work just fine.
>
> From a couple of people who post regularly on this list, I
> have heard that they have great success with iLBC (and some
> with Speex as well). I think that NuFone prefers iLBC as
> well, though it works remarkably well for me with GSM.
>
> I did some experiments in forcing my * servers to
> communicate with each other only with iLBC. When I do that,
> and can see that they are indeed using iLBC, the quality is
> horrible. There is long stutter, like every sound is being
> "stretched" out.
>
> I purchased g729 licenses from Digium for all three servers
> as well. Using g729 on the Sipura devices yielded no better
> quality than the built-in g726. However, when I made two *
> servers communicate only with g729, the quality was
> marginally better than iLBC, and ridiculously worse than
> GSM. This was surprising to me.
>
> All of this is with a very recent cvs checkout of *, done
> this past Monday the 22nd I believe.
>
> Last point is that if I turn jitterbuffer on (with =yes),
> then I never hear _any sound_ whatsoever, but there are _no
> errors_ on either side of the channel. I can see on the CLI
> that voicemail prompts are being played (for example), but I
> can't hear anything on either side. Turning jitterbuffer=no
> immediately restores sound, but the quality only sounds good
> with GSM.
>
> What I don't understand is how some people have success with
> iLBC, and I don't. I also noticed one or two posts from
> people that claim that GSM isn't working for them, yet it
> works really well for me. Are there any settings that I am
> unaware of (other than the standard "allow/disallow"
> directives) that I should be tweaking to make these other
> codecs work as I understand they should?
>
> P.S. One last piece of voodoo, just if anyone knows the
> answer to this. On occasion, I use DIAX to connect to the
> remote * server. It works very well, and is the best of the
> IAX softphones (IMHO). Yesterday, it was working just fine.
> Today, from a different location (both yesterday and today
> behind NAT, just from different networks), it connects fine,
> but I have zero sounds and zero errors. There were _no_
> changes to the server or the software setup in between.
>
> In the past, I have had trouble using X-Lite to this
> particular * server. Today, when DIAX wasn't working
> (neither was iaxcomm, it's not a specific DIAX problem), I
> tried X-Lite again, and it worked flawlessly...
>
> The last bit of info on this is that one of the other *
> servers is on the same lan as the DIAX client, but on
> different machines. Both are coming from the same NAT
> router though. The * machine is in the DMZ, so all packets
> that are sent to the public side are routed directly to *,
> and that part works perfectly. I don't know if DIAX is
> clashing with * packets, but I know this has worked in the
> past (though it's been 2 weeks since I've tried, and I did
> cvs up the * server since it last worked...).
>
> Thanks in advance to any brave soul who tackles some or all
> of these questions/issues! :-)
>
>
>
> --__--__--
>
> Message: 13
> Subject: RE: [Asterisk-Users] New minor release of Firefly (now with
Speex)> Date: Fri, 26 Mar 2004 12:14:07 +1100
> From: "Simon Brown" <Simon.Brown@otterson.com.au>
> To: <asterisk-users@lists.digium.com>
> Reply-To: asterisk-users@lists.digium.com
>
> When you use firefly in SIP mode it does not un-register with * on >
exiting
> the software
>
> Simon
> =20
>
> -----Original Message-----
> From: asterisk-users-admin@lists.digium.com
> [mailto:asterisk-users-admin@lists.digium.com] On Behalf Of Adam Hart
> Sent: Friday, 26 March 2004 11:48
> To: asterisk-users@lists.digium.com
> Subject: [Asterisk-Users] New minor release of Firefly (now with Speex)
>
> I've put up a new dev version of Firefly
> (http://www.virbiage.com/firefly/download/firefly-dev.exe)
>
> Notable Changes:
> DTMF now works with SIP
> Speex codec has been added
> 1 crash bug fixed - 2 more to go (if you can crash Firefly, send me the
> Hex
> address - probably stored in event viewer under control panel)
>
> Sorry for the delay but I've completely rewritten how contacts work
> internally (although it looks exactly the same as it did before). This >
now
> allows me to do some sexy things with contacts. Stay tuned
>
> I'm aiming for a stable release in two weeks so help me find the
bugs.=20
> Many thanks to thoses who have
>
> -Adam
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
>
>
>
> -----
> This mail was content checked for malicious code and viruses
> by GFI MailSecurity.
>
>
> --__--__--
>
> Message: 14
> Subject: Re: [Asterisk-Users] SoftFAX/spandsp
> From: Nicolas Gudino <nicolas@house.com.ar>
> To: asterisk-users@lists.digium.com
> Organization: House Internet S.R.L.
> Date: Thu, 25 Mar 2004 22:14:39 -0300
> Reply-To: asterisk-users@lists.digium.com
>
> Hi Eric,
>
> I was all day trying and came up with this:
>
> gs -q -sDEVICE=tiffg3 -sPAPERSIZE=a4 -r204x196 \
> -dNOPAUSE -sOutputFile=$TIFFILE -- $PSFILE
>
> I'm using a modified version of "salsafax/sambafax" to enable
a
> print2fax option for windows/linux clients.
>
> You add a printer to cups and share it via Samba. Then, you append a
> line with the fax number in the file you want to be faxed "Fax-Nr
> 34333333" and print it to the network printer from any application.
>
> The scripts extracts the number and then generates a call file for
> asterisk.
>
> Some ps files cannot be extracted, so I used an OCR application (gocr)
> to extract the text, maybe its overkill, but it works most of the time
> (here we send less than ten faxes a day, so its no problem for us). I
> will clean up the scripts and post them for others to use.
>
> Good luck,
>
>
> On Thu, 2004-03-25 at 21:19, Eric Wieling wrote:
> > On Thu, 2004-03-25 at 09:33, Steve Underwood wrote:
> > > exten => 5678,1,txfax(/tmp/testfax.tif|caller)
> >
> > There are a zillion fax and tiff formats. I'm trying to figure
out what
> > output format I should tell GhostScript to use. Any suggestions on
> > which format to try?
> >
> > These are the formats GhostScript can output:
> >
> > faxg3 faxg32d faxg4 tiff12nc tiff24nc tiffcrle tiffg3 tiffg32d tiffg4
> > tifflzw tiffpack
> --
> Nicolas Gudino <nicolas@house.com.ar>
> House Internet S.R.L.
>
>
> --__--__--
>
> Message: 15
> Date: Thu, 25 Mar 2004 18:40:41 -0700
> From: " John Brown (CV)" <jmbrown@chagresventures.com>
> To: asterisk-users@lists.digium.com
> Subject: [Asterisk-Users] IAX drops calls exactly 5 secs into the call
> Reply-To: asterisk-users@lists.digium.com
>
> Hi List,
>
> Two boxes
>
> A has a PRI
>
> B terminates SIP devices
>
>
> A <--IAX--> B
>
> Both on the same switch, same IP network.
>
> Call from PSTN to A gets pushed via IAX to B -> Sip device
> with no problems.
>
> Call from Sip device -> B via IAX -> A -> PSTN
> will drop exactly 5 seconds after the call is answered.
>
> I've built with 0.7.2, 1_0_Stable devel etc
>
>
> Any clue / hints ??
>
> thanks
>
>
>
>
> --__--__--
>
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
>
>
> End of Asterisk-Users Digest
>
Hi all, spandsp-0.0.1h.tar.gz seemed to get a lot more FAX machines talking, but a number of people are getting rather high error rates on the images. spandsp-0.0.1i.tar.gz addresses this, and should give much better bit error rates for fax machines whose timing at the extremes the spec allows. It can be found at ftp://ftp.opencall.org/pub/spandsp/spandsp-0.0.1i.tar.gz Regards, Steve
Hi Steve,
You're right it is just the libtiff. I have uninstall 3.6 and 3.5 and
reinstall 3.5.7-11. Thanks, it is now receiving fax.
Although after receiving the fax, the zap channel is not disconnecting. ?
On the fax client it was successfully sent and the tif file is complete.
Here is my extensions.conf:
exten => s,1,Answer
exten => s,2,SetVar(FAXNAME=${TIMESTAMP}-${CALLERIDNUM})
exten => s,3,RxFax(/var/lib/asterisk/fax/new/${FAXNAME}.tif)
exten => s,4,Hangup
exten => i,1,Hangup
exten => h,1,Hangup
And here is the log file:
Page 1 of /var/lib/asterisk/fax/new/20040329-234801-0755965128.tif:
1116 rows received
0 total bad rows
0 max consecutive bad rows
Rx page end detected
Changed from phase 5 to 3
Slow carrier up
Slow carrier down
Slow carrier up
<<< EOP: 2f
EOP with final frame tag
In state 5
Changed from phase 3 to 4>>> MCF: 8c
HDLC underflow in state 8
Changed from phase 4 to 3
Slow carrier up
<<< DCN: fb
DCN with final frame tag
In state 8
Disconnecting
Changed from phase 3 to 7
*CLI> show channels
Channel (Context Extension Pri ) State Appl. Data
Zap/1-1 (faxserver s 3 ) Up RxFAX
/var/lib/asterisk/fax/new/20040329-234801-0755965128.tif
1 active channel(s)
Hi Steve and all ! Unable to send fax from * to a fax machine... File name is '/root/faxes/8400100-1081935748.808.tif' Changed from phase 0 to 2 Slow carrier up Slow carrier down Slow carrier up <<< NSF: 20 00 00 11 80 00 8a 49 10 43 53 43 20 54 45 4c 45 43 4f 4d 20 20 20 20 20 00 7b 00 80 80 80 06 01 01 01 01 NSF without final frame tag The remote is made by 'Canon' <<< CSI: 40 31 35 36 31 30 32 37 31 37 33 30 30 20 20 20 20 20 20 20 20 CSI without final frame tag Remote fax gave CSI as: "003717201651" <<< DIS: 80 00 ee a8 c4 80 10 DIS with final frame tag In state 10 DIS: Preferred octets: 256 Can receive fax Supported data signalling rates: V.27ter, V.29 and V.17 R8x7.7lines/mm and/or 200x200pels/25.4mm OK 2D coding OK Scan line length: 215mm Recording length: A4 (297mm) and B4 (364mm) Receiver's minimum scan line time: 10ms at 3.85 l/mm: T7.7 = T3.85 Error correction mode T.6 coding Metric-based resolution preferred Minimum scan line time for higher resolutions: T15.4 = T7.7 DCS: Selected data signalling rate: V.29, 9600bps 2D coding OK Scan line length: 215mm Recording length: A4 (297mm) Minimum scan line time: 10ms Start sending document Start tx document - compression 2 Fine mode Changed from phase 2 to 4 Sending ident>>> TSI: 43 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 >>> DCS: 83 00 c4 20HDLC underflow in state 3 Changed from phase 4 to 6 Changed from phase 6 to 3 Slow carrier up <<< XCN: fa XCN with final frame tag In state 4 Disconnecting Changed from phase 3 to 7 Changed from phase 7 to 8 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20040414/eb9a795b/attachment.htm