Re: [Opalvoip-user] T.30 error 49 - spandsp
Brought to you by:
csoutheren,
rjongbloed
Menu
▾
▴
Re: [Opalvoip-user] T.30 error 49 - spandsp
|
From: Mahudeswaran <mah...@ac...> - 2011-06-16 06:49:16
|
Hi Robert, Thank you for the reply. >> Does this occur all the time or only sometimes? You had previously indicated in a mail that it was working, correct? Only sometimes. Last week i used faxopal to send fax and those 3 or 4 attempts succeeded. My work place and fax device are located on different floors. So after each fax test call i have to call and confirm with the person who is sitting near to the fax device for the fax status where i can get only limited observation points. Last week i sent 10 faxes from faxopal. Out of 10, 8 succeeded and 2 failed. Observation point-1: After the 2 rings the fax device will be answered. In fax device the status change from 'connecting...' to 'receiving...' will take an avg of 15-20 seconds. If the papers were not fetched correctly then the call will disconnect and fax device status will be idle. That time the spandsp get on T.39 error 49 (call ended prematurely). Observation point-2: In fax device the print 'Auto caller list' is enabled so after 4 or 5 fax received the fax device will start the printing. If any fax incoming call received then the status will be ?? . In one instance i saw the incoming fax call and after the fax call answered the '..caller list.. - report' printed instead of .tif file from faxopal. After these observation i retested the fax where the faxopal-->spandsp received T.30 response code but actually the fax was sent successfully. >> Can you determine if it related to a specific fax machine? At present we have only one analog fax device model Panasonic - kxfm386cx I will proceed with the latest revision. There are various factors which can determine the status of fax apart from opal/-spandsp. Regards mahudeswaran From: Robert Jongbloed [mailto:ro...@vo...] Sent: Thursday, June 16, 2011 5:48 AM To: opa...@li... Subject: Re: [Opalvoip-user] T.30 error 49 - spandsp Dmitry has a "thing" about revision 24174 and steadfastly refuses to move on to the latest version. There may be issues with the latest version, and the way to move forward is to try and fix any issues, not continuously say "use revision 24174". But, that is his decision. I would not recommend that course of action, there are many, many stability issue in the several hundred revisions since then. We are up revision 26026 after all! Unlike all Dimity's issues of the past, your particular problem does not appear to be anything to do with the initial switching to T.38. The attached Wireshark graph analyser shows that all the initial negotiations occur correctly. However we get a negative acknowledgement from the remote about the receipt of the page. |36.249 | t4-non-ecm-data:v29-9600 |t38:t4-non-ecm-data:v29-9600 Duration: 41.72s No packet lost | |(5000) ------------------> (8092) | |78.046 | no-signal | |t38:t30 Ind:no-signal | |(5000) ------------------> (8092) | |78.126 | v21-preamble |t38:t30 Ind:v21-preamble | |(5000) ------------------> (8092) | |79.207 | EOP | |t38:v21:HDLC:End Of Procedure | |(5000) ------------------> (8092) | |79.426 | no-signal | |t38:t30 Ind:no-signal | |(5000) ------------------> (8092) | |81.889 | v21-preamble |t38:t30 Ind:v21-preamble | |(5000) <------------------ (8092) | |83.009 | RTN | |t38:v21:HDLC:Retrain Negative | |(5000) <------------------ (8092) | The first message shows the Wireshark saw all of the outgoing page data packets, but the last message which is from the remote to OPAL is a T.30 RTN command, this means that the remote fax did not like something about the page data it received. All of the T.30 is in span DSP. It is not part of OPAL. So, questions: Does this occur all the time or only sometimes? You had previously indicated in a mail that it was working, correct? Can you determine if it related to a specific fax machine? You may wish to consider contacting the author of SpanDSP, st...@co.... He might be able to give insights into why the remote is sending an RTN. Robert Jongbloed OPAL/OpenH323/PTLib Architect and Co-founder. From: Mahudeswaran [mailto:mah...@ac...] Sent: Wednesday, 15 June 2011 9:53 PM To: Dmitry; Aron Wieck Cc: opa...@li... Subject: Re: [Opalvoip-user] T.30 error 49 - spandsp Hi, Last time I downloaded from branch for opal, ptlib, plugins from branch as below etc.. and build it. http://opalvoip.svn.sourceforge.net/svnroot/opalvoip/opal/branches/v3_10 http://opalvoip.svn.sourceforge.net/svnroot/opalvoip/ptlib/branches/v2_1 0 http://opalvoip.svn.sourceforge.net/svnroot/opalvoip/opal/branches/v3_10 /plugins Are you suggesting, to use only opal from trunk between 24174-24192? What about the ptlib. Will the branch ptlib work with trunk opal? |