Max CtRiX wrote: >Hi, > >I have tried to use the latest snapshots of SpanDSP to make T38 >termination work. > >I managed to compile everything. The whole thing requires some >modifications to configure.ac, codec_g.726 (conflicts with new spandsp) >and of course, app_txfax and app_rxfax. > >I have managed to get some results. In particular: >No fax received. >Only 1 fax transmitted (great result!) > >I have collected some logs here: http://projects.navynet.it/t38/1/ > >File tx2-ok is the log of the only one which worked well. > >Now, I do not have the background to understand what is going wrong, but >it seems to me that udptl OR spandsp does not manage very well sequence >numbers. > >Do you have any hints ? > >Thanks, > Max > > I just committed a few changes to trunk related to this.
The logging in udptl.c isn't that useful for analysing detailed problems. There were sequence numbers, and packet type fields, but these contained no actual information. That information isn't knowm at the transport level. I have tidied that up now. I have also added the ability to send specified packets multiple times. T.38 terminals and gateways do this as part of their redundancy practices - its not part of the the spec, but it is something many implementations of T.38 do. My latest spandsp code can make use of this feature. I modified app_rxfax.c and app_txfax.c to work with the latest APIs in the spandsp snapshots. You need to comment out the first line in each file, or you will get the old API. The logs from your tests do not have the debug logging for app_txfax switched on. That makes them of very little value for analysis. Try the latest code, and enable txfax debug logging. Then we should be able to see what is really going on. Steve _______________________________________________ Openpbx-dev mailing list [email protected] http://lists.openpbx.org/mailman/listinfo/openpbx-dev
