I’ve used spandsp-0.0.5pre4 (17/06/2008),
so I’m sure anything after that will be easy to integrate with. I can
take care of that.
I seems like socket2me terminates the
server socket once a fax is coming and I’m not clear of when this socket
is re-established. Needless to say I don’t understand socket2me, but I’ll
appreciate if someone that does can assist.
Having socket2me multithreaded sounds like
the way to go. A mod_socket2me would be even better. A mod_fax2email would be
ideal… but so can mod_MakeCoffee…
From:
freeswitch-dev-bounces@lists.freeswitch.org
[mailto:freeswitch-dev-bounces@lists.freeswitch.org] On Behalf Of Michael Jerris
Sent: Tuesday, July 29, 2008 1:59
AM
To:
freeswitch-dev@lists.freeswitch.org
Subject: Re: [Freeswitch-dev]
WIN32 fax2email
in unix it is forking to handle additional connections.. we will either
need to make this threaded or if possible just spawn a new process for each
fax. In regards to spandsp, we should be using the latest snapshot
from http://www.soft-switch.org/downloads/snapshots/spandsp/
. 99% of that is ported except we need to add a couple projects for code
generators.
Mike
On Jul 28, 2008, at 11:52 AM, UV wrote:
I’ve got 99% of the entire fax2email
package ported to Win32 including:
zlib 1.2.3
jpeg-6b
libtiff (tiff-3.8.2)
libport (tiff-3.8.2 port)
tiff2pdf (tiff-3.8.2 tools)
spandsp-0.0.5
However, although I got socket2me to
compile and run under win32, I’m don’t think it was done properly,
primarily due to my misunderstanding of the fork() purpose.
I’d appreciate if anyone can give me
help with this last step (which, obviously, will be shared).
I think a Win32 port of the fax2email
capability would make a nice addition.