<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hallo there!<br>
I had my own experience get RxFax/TxFax successful running with spandsp.<br>
I only got spandsp-0.0.4 running, because on newer package, there
aren't created some needed libraries (don't remember the right one this
moment)<br>
<b>find /usr -iname \*spandsp\*</b> shows me following output:<br>
/usr/lib/libspandsp.so<br>
/usr/lib/pkgconfig/spandsp.pc<br>
/usr/lib/libspandsp.so.0.0.2<br>
/usr/lib/libspandsp.a<br>
/usr/lib/libspandsp.so.2<br>
/usr/lib/libspandsp.so.0<br>
/usr/lib/libspandsp.so.2.0.0<br>
/usr/lib/libspandsp.la<br>
<br>
and <br>
<br>
debian-server*CLI> <b>core show application RxFAX</b><br>
debian-server*CLI><br>
-= Info about application 'RxFAX' =-<br>
<br>
[Synopsis]<br>
Receive a FAX to a file<br>
<br>
[Description]<br>
RxFAX(filename[|caller][|debug]): Receives a FAX from the channel
into the<br>
given filename. If the file exists it will be overwritten. The file<br>
should be in TIFF/F format.<br>
The "caller" option makes the application behave as a calling machine,<br>
rather than the answering machine. The default behaviour is to behave as<br>
an answering machine.<br>
Uses LOCALSTATIONID to identify itself to the remote end.<br>
LOCALHEADERINFO to generate a header line on each page.<br>
Sets REMOTESTATIONID to the sender CSID.<br>
FAXPAGES to the number of pages received.<br>
FAXBITRATE to the transmition rate.<br>
FAXRESOLUTION to the resolution.<br>
Returns -1 when the user hangs up.<br>
Returns 0 otherwise.<br>
<br>
debian-server*CLI> <b>core show application TxFAX</b><br>
debian-server*CLI><br>
-= Info about application 'TxFAX' =-<br>
<br>
[Synopsis]<br>
Send a FAX file<br>
<br>
[Description]<br>
TxFAX(filename[|caller][|debug]): Send a given TIFF file to the
channel as a FAX.<br>
The "caller" option makes the application behave as a calling machine,<br>
rather than the answering machine. The default behaviour is to behave as<br>
an answering machine.<br>
Uses LOCALSTATIONID to identify itself to the remote end.<br>
LOCALHEADERINFO to generate a header line on each page.<br>
Sets REMOTESTATIONID to the receiver CSID.<br>
Returns -1 when the user hangs up, or if the file does not exist.<br>
Returns 0 otherwise.<br>
<br>
<br>
Regards<br>
<br>
Am 17.01.2010 09:11, schrieb Doug:
<blockquote cite="mid:948406621-225129280@mail1.natel.net" type="cite">
<pre wrap="">At 23:04 1/16/2010, Tilghman Lesher wrote:
>That's incorrect. "module show" shows only those modules which are currently
>loaded. BTW, there is also the command "module show like fax", which is much
>easier than typing out the whole module name, may show you more modules than
>you were aware of, and might be extremely helpful by showing you other
>related modules that are already loaded.
Thanks, guys.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CLI> module show like fax
Module Description
Use Count
0 modules loaded
CLI> module show like zt
Module Description
Use Count
0 modules loaded
CLI> module show like zap
Module Description
Use Count
app_zapateller.so Block Telemarketers with Special Informa 0
1 modules loaded
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
No joy.
Read this and recompiled Asterisk:
<a class="moz-txt-link-rfc2396E" href="http://ibot.rikers.org/%23asterisk/20090618.html.gz"><http://ibot.rikers.org/%23asterisk/20090618.html.gz></a>
Got these messages:
WARNING WARNING WARNING
Your Asterisk modules directory, located at
/usr/lib/asterisk/modules
contains modules that were not installed by this
version of Asterisk. Please ensure that these
modules are compatible with this version before
attempting to run Asterisk.
app_fax.so
app_saycountpl.so
chan_ooh323.so
format_mp3.so
Read something else and found this in:
/var/log/asterisk/messages
[Jan 17 01:28:16] NOTICE[2479] loader.c: 145 modules will be loaded.
[Jan 17 01:28:16] WARNING[2479] loader.c: Error loading module
'app_fax.so': libspandsp.so.2: cannot open shared object file: No
such file or directory
[Jan 17 01:28:17] WARNING[2479] res_smdi.c: No SMDI interfaces are
available to listen on, not starting SMDI listener.
[Jan 17 01:28:19] WARNING[2479] loader.c: Error loading module
'app_fax.so': libspandsp.so.2: cannot open shared object file: No
such file or directory
[Jan 17 01:28:19] WARNING[2479] loader.c: Module 'app_fax.so' could
not be loaded.
[Jan 17 01:28:19] ERROR[2479] chan_dahdi.c: Unable to load zapata.conf
[Jan 17 01:28:20] NOTICE[2479] chan_ooh323.c:
---------------------------------------------------------------------------------
--- ******* IMPORTANT NOTE ***********
---
--- This module is currently unsupported. Use it at your own risk.
---
---------------------------------------------------------------------------------
Does libspandsp.so.2 need to be copied to someplace
else?
# find / -name "libspandsp.so.2*"
/usr/src/asterisk/spandsp/spandsp-0.0.6/src/.libs/libspandsp.so.2.0.0
/usr/src/asterisk/spandsp/spandsp-0.0.6/src/.libs/libspandsp.so.2
/usr/local/lib/libspandsp.so.2.0.0
/usr/local/lib/libspandsp.so.2
Do I need a zapata.conf if I am using ztdummy?
# find / -name "zapata.conf"
#
Any other ideas?
</pre>
</blockquote>
<br>
</body>
</html>