Kristijan Vrban wrote: > ok, next option to see a working T.38 transmission was to use *1.4 > with attrafax: > see tcpdump: http://iax2gate.de/callweaver/AttraFax_t38_log > and with attrafax it's working fine. > > and again the same setup with spandsp and cw: > http://iax2gate.de/callweaver/spandsp_t38_log > > There are some differences between the spandsp and attrafax T.38 > conversation with the Grandstream > T.38. But if you compare the part right after the v29-9600-training, > wireshark say that with the > field-type: hdlc-fcs-OK-sig-end spandsp send something is not ok. > Perhaps thats a reason why > the Grandstream does not answer any more after that? > > iam accessible for any hints how to debug spandsp's t.38 in a deeper > way at this point. > > Kristijan > Having worked with Kristijan on IRC it seems the Grandstream is very sensitive to changeover timing, and spandsp was not allowing as much time as it should. An updated spandsp seems to be working OK with this Grandstream box, and I have made this spandsp-0.0.6pre11.tgz
Regards, Steve _______________________________________________ Callweaver-users mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-users
