Hello Steve (Fax god)!Thanks for your explanation.
4 days ago I installed FS (git version) on my test server. Yesterday I've received my new SS7 connection. so I was testing & able to receive faxes (SIP-alaw to SIP-T.38) and I couldn't test send faxes because my Telco didn't activate outbound calling. my test was success at 30 concurrent calls/faxes.
Today my telco activate outbound calling and I've updated FS to today's git version. I did update (git pull && make current) without keeping a backup of old FS sources. While I was updating I had a same problem like "Update fail on mod_spandsp" finally I've updated the system. the problem is now I can't receive or send a fax with today's git version.
My sip log indicates I was using "User-Agent: FreeSWITCH-mod_sofia/1.0.head-git-28eb6e0 2010-07-21 00-22-24 +0800" and this version support receive faxes.
Now I'm using "User-Agent: FreeSWITCH-mod_sofia/1.0.head-git-e704f02 2010-07-25 10-10-06 +0200" and this version doesn't allow me to send and receive faxes.
Please let me know how can I download "2010-07-21" version again. then I can continue my testing.
Thanks a lot.
Weera Suriya
On Tue, Jul 20, 2010 at 11:45 PM, Steve Underwood
<steveu@coppice.org> wrote:
On 07/20/2010 11:16 PM, Weera Suriya wrote:
> Hello list,
> I have a question about t.38 fax gateway feature in FS(mod_spandsp).
> here is my setup.
> PSTN <----SS7--->YATE(doesn't support T.38 fax
> gateway)<----IAX2--alaw---->CallWeaver-Faxgateway<------SIP--T.38------->OpenSIPs<------->ATAs(T.38)<---->fax
> machines
> I've 16 E1s connected with my Yate server and Yate server send faxes
> to Callweaver servers (6 servers for CallWeaver) via IAX2(alaw) . then
> CallWeaver servers send faxes to OpenSIPs server via SIP T.38 and
> OpenSIPs server send SIP calls to ATAs
>
> Now I want to expand this setup by adding 16 more E1 connections and I
> want to replace these 6 CallWeaver servers with one or two FreeSwitch
> :) I would like to know one thing. does FS able to convert SIP alaw
> fax (or IAX2 alaw fax) into SIP T.38 fax (I know TDM to SIP t.38 works
> with FS)
>
it should be more robust than Callweaver in its call negotiation logic,
and the logic in the T.38 engine. However, it has not yet been pushed as
hard as Callweaver with concurrent channels. The design looks good, but
we still need to prove no processing spikes, or similar issues, prevent
the concurrent channels going right up to the limits of the processors.
If you want to try high volumes with FS we will be grateful for any
feedback, and I will consider addressing any performance issues you
might find a priority.
Steve