sean darcy
2009-May-05 02:52 UTC
[asterisk-users] 1.6.1 app_fax: WARNING T.30 ECM carrier not found ??
Receiving a fax with 1.6.1: == Spawn extension (incoming-pstn-line, fax, 1) exited non-zero on 'DAHDI/4-1' -- Executing [fax at incoming-pstn-line:1] NoOp("DAHDI/4-1", "Fax Detected") in new stack -- Executing [fax at incoming-pstn-line:2] Goto("DAHDI/4-1", "incoming-fax,s,1") in new stack -- Goto (incoming-fax,s,1) -- Executing [s at incoming-fax:1] Set("DAHDI/4-1", "FAXFILE=/var/spool/asterisk/fax/20090504_1602-0") in new stack -- Executing [s at incoming-fax:2] ReceiveFAX("DAHDI/4-1", "/var/spool/asterisk/fax/20090504_1602-0.tif") in new stack -- Starting simple switch on 'DAHDI/1-1' -- Remote UNIX connection -- Hungup 'DAHDI/1-1' [2009-05-04 16:02:39] WARNING[12989]: app_fax.c:128 span_message: WARNING T.30 ECM carrier not found [2009-05-04 16:02:40] WARNING[12989]: app_fax.c:128 span_message: WARNING T.30 ECM carrier not found [2009-05-04 16:02:40] WARNING[12989]: app_fax.c:128 span_message: WARNING T.30 ECM carrier not found [2009-05-04 16:02:46] WARNING[12989]: app_fax.c:128 span_message: WARNING T.30 ECM carrier not found [2009-05-04 16:02:46] WARNING[12989]: app_fax.c:128 span_message: WARNING T.30 ECM carrier not found -- Executing [s at incoming-fax:3] Hangup("DAHDI/4-1", "") in new stack ECM - error correction mode ( right?) - but the fax is received OK. Any reason to worry? Anything to do? sean
David Backeberg
2009-May-08 16:48 UTC
[asterisk-users] 1.6.1 app_fax: WARNING T.30 ECM carrier not found ??
On Mon, May 4, 2009 at 10:52 PM, sean darcy <seandarcy2 at gmail.com> wrote:> Receiving a fax with 1.6.1: > > ? == Spawn extension (incoming-pstn-line, fax, 1) exited non-zero on > 'DAHDI/4-1' > ? ? -- Executing [fax at incoming-pstn-line:1] NoOp("DAHDI/4-1", "Fax > Detected") in new stack > ? ? -- Executing [fax at incoming-pstn-line:2] Goto("DAHDI/4-1", > "incoming-fax,s,1") in new stack > ? ? -- Goto (incoming-fax,s,1) > ? ? -- Executing [s at incoming-fax:1] Set("DAHDI/4-1", > "FAXFILE=/var/spool/asterisk/fax/20090504_1602-0") in new stack > ? ? -- Executing [s at incoming-fax:2] ReceiveFAX("DAHDI/4-1", > "/var/spool/asterisk/fax/20090504_1602-0.tif") in new stack > ? ? -- Starting simple switch on 'DAHDI/1-1' > ? ? -- Remote UNIX connection > ? ? -- Hungup 'DAHDI/1-1' > [2009-05-04 16:02:39] WARNING[12989]: app_fax.c:128 span_message: > WARNING T.30 ECM carrier not found > [2009-05-04 16:02:40] WARNING[12989]: app_fax.c:128 span_message: > WARNING T.30 ECM carrier not found > [2009-05-04 16:02:40] WARNING[12989]: app_fax.c:128 span_message: > WARNING T.30 ECM carrier not found > [2009-05-04 16:02:46] WARNING[12989]: app_fax.c:128 span_message: > WARNING T.30 ECM carrier not found > [2009-05-04 16:02:46] WARNING[12989]: app_fax.c:128 span_message: > WARNING T.30 ECM carrier not found > ? ? -- Executing [s at incoming-fax:3] Hangup("DAHDI/4-1", "") in new stack > > ECM - error correction mode ( right?) - but the fax is received OK. Any > reason to worry? Anything to do?Since you are receiving a fax over an analog line, you can set up MixMonitor() or Monitor() to record the fax, play it back, listen for line noise or static or something else that may be happening that's throwing those warnings from SpanDSP. Obviously if you're getting a fax you're not as worried as if this caused the fax to drop. Once you have a recording of the transmission and the logs of what happens you can submit it to the SpanDSP project to see what they think. Incidentally, how verbose do you have to set your CLI to get output that lists the warnings?
Martin
2009-May-10 23:51 UTC
[asterisk-users] 1.6.1 app_fax: WARNING T.30 ECM carrier not found ??
On Mon, May 4, 2009 at 9:52 PM, sean darcy <seandarcy2 at gmail.com> wrote:> Receiving a fax with 1.6.1: >[cut]> ? ? -- Hungup 'DAHDI/1-1' > [2009-05-04 16:02:39] WARNING[12989]: app_fax.c:128 span_message: > WARNING T.30 ECM carrier not found[cut]> > ECM - error correction mode ( right?) - but the fax is received OK. Any > reason to worry? Anything to do?your WARNING prints after the DAHDI channel hanged up. It's possible the receivefax app would want to do a hangup itself instead of being hanged up. It might be a normal behavior since the app is disconnected from the audio stream. Martin