next log, AttraFax <-> spandsp is working: http://iax2gate.de/callweaver/AttraFax_spandsp_log Wireshark say something about Malformed for frame 160 and 161 from spandsp (again the t4-non-ecm-sig-end)
Kristijan @Gerald I tried also older spandsp down to 0.0.4pre15, but same result. On Fri, May 1, 2009 at 4:36 PM, Kristijan Vrban <[email protected]> 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 > > > On Fri, May 1, 2009 at 11:44 AM, Kristijan Vrban <[email protected]> wrote: >> to debug this, i wanted to look how a working T.38 transmission look >> like, so setup two cw with spandsp6_pre10 >> >> [faxout] ;cw 1 >> exten => s,1,TxFAX(${FAXFILE},debug) >> exten => s,n,Hangup >> >> [faxin] ;cw 2 >> exten => 123,1,RxFAX(/tmp/faxfile.tiff,debug) >> exten => 123,n,Hangup() >> >> But the transmission always fail. On cw1: >> Fax send not successful - result (14) Received bad response to DCS or >> training. >> Log: http://callweaver.pastebin.com/m10782863 >> >> and cw2: >> Fax receive not successful - result (13) Unexpected message received. >> Log: http://callweaver.pastebin.com/m3140c592 >> >> Is spandsp's T.38 not compatible with spandsp's T.38? >> >> Kristijan >> >> On Fri, May 1, 2009 at 11:37 AM, <[email protected]> >> wrote: >>> You are not allowed to post to this mailing list, and your message has >>> been automatically rejected. If you think that your messages are >>> being rejected in error, contact the mailing list owner at >>> [email protected]. >>> >>> >>> >>> ---------- Forwarded message ---------- >>> From: Kristijan Vrban <[email protected]> >>> To: [email protected] >>> Date: Fri, 1 May 2009 11:36:37 +0200 >>> Subject: Re: [Callweaver-users] T.38 fail with Grandstream HT502 >>> to debug this, i wanted to look how a working T.38 transmission look >>> like, so setup two cw with spandsp6_pre10 >>> >>> [faxout] ;cw 1 >>> exten => s,1,TxFAX(${FAXFILE},debug) >>> exten => s,n,Hangup >>> >>> [faxin] ;cw 2 >>> exten => 123,1,RxFAX(/tmp/faxfile.tiff,debug) >>> exten => 123,n,Hangup() >>> >>> But the transmission always fail. On cw1: >>> Fax send not successful - result (14) Received bad response to DCS or >>> training. >>> Log: http://callweaver.pastebin.com/m10782863 >>> >>> and cw2: >>> Fax receive not successful - result (13) Unexpected message received. >>> Log: http://callweaver.pastebin.com/m3140c592 >>> >>> Is spandsp's T.38 not compatible with spandsp's T.38? >>> >>> Kristijan >>> >>> On Fri, May 1, 2009 at 11:17 AM, Kristijan Vrban <[email protected]> wrote: >>>> Hello, i started to play with T.38 with a Grandstream HT502. (FW 1.0.1.35) >>>> the diaplan: >>>> >>>> exten => s,1,Set(LOCALSTATIONID=CallWeaver FAX) >>>> exten => s,n,Set(LOCALHEADERINFO=Callewaver fax termination) >>>> exten => s,n,Set(FAXFILE=/tmp/${UNIQUEID}.tif) >>>> exten => s,n,Set(FAXFILENOEXT=/tmp/${UNIQUEID}) >>>> exten => s,n,Wait(1) ;Without this wait, the HT502 beep a lot, but >>>> dont start to send >>>> exten => s,n,RxFAX(${FAXFILE},debug) >>>> exten => s,n,Hangup() >>>> exten => h,1,NoOp(RxFAX completed) >>>> exten => h,n,NoOp(RX: REMOTESTATIONID is ${REMOTESTATIONID}) >>>> exten => h,n,NoOp(RX: FAXPAGES is ${FAXPAGES}) >>>> exten => h,n,NoOp(RX: FAXRESOLUTION is ${FAXRESOLUTION}) >>>> exten => h,n,NoOp(RX: FAXBITRATE is ${FAXBITRATE}) >>>> exten => h,n,NoOp(RX: PHASEESTATUS is ${PHASEESTATUS}) >>>> exten => h,n,NoOp(RX: PHASESTRING is ${PHASEESTRING}) >>>> >>>> The HT502 start to communicate with T.38, but it suddenly stops when >>>> the analog fax machine start to move in the fax sheet. >>>> So i never get a fax with t.38. >>>> >>>> Fax over audio(ulaw) is no problem with the same setup. >>>> >>>> The complete log: >>>> http://callweaver.pastebin.com/m537ec206 >>>> _______________________________________________ >>>> Callweaver-users mailing list >>>> [email protected] >>>> http://lists.callweaver.org/mailman/listinfo/callweaver-users >>>> >>>> >>>> >>> >>> >> > _______________________________________________ Callweaver-users mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-users
