[Home]

Summary:ASTERISK-16765: app_fax.c: Transmission error for successfully transmitted faxes
Reporter:Jan Klepal (kenny)Labels:
Date Opened:2010-10-04 13:17:08Date Closed:2015-02-26 09:34:31.000-0600
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Applications/app_fax
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Sometimes application SendFAX indicates "app_fax.c:817 transmit: Transmission error" even the transmission of FAX was successful "app_fax.c: Fax transmitted successfully". I figured out it happens because res value in loop is set to 4 (probably because remote party hangs first?).

I am not sure if the problem is bug or just not expected behavior of SendFAX application. Because in following scenario external application will not be notified:

{noformat}
exten => s,1,Noop()
exten => s,n,SendFax(${FAXFILE})
exten => s,n,System(/opt/fax/notify.py "${FAXID}" "${FAXSTATUS}" "${FAXERROR}")
{noformat}

Workaround is to use "h" extension to catch transmitted faxes with any result.

{noformat}
exten => s,1,Noop()
exten => s,n,SendFax(${FAXFILE})
exten => h,n,System(/opt/fax/notify.py "${FAXID}" "${FAXSTATUS}" "${FAXERROR}")
{noformat}

Maybe similar option like "g" in Dial application would be nice in SendFAX application... or at least note in documentation :-)

*ADDITIONAL INFORMATION*

{noformat}
[2010-10-04 18:48:40.256] DEBUG[3903] app_fax.c: FLOW T.30 Send complete in phase T30_PHASE_D_TX, state 3
[2010-10-04 18:48:40.256] DEBUG[3903] app_fax.c: FLOW T.30 Disconnecting
[2010-10-04 18:48:40.256] DEBUG[3903] app_fax.c: FLOW T.30 Changing from phase T30_PHASE_D_TX to T30_PHASE_E
[2010-10-04 18:48:40.256] DEBUG[3903] app_fax.c: FLOW T.38T Set rx type 0
[2010-10-04 18:48:40.256] DEBUG[3903] app_fax.c: FLOW T.38T Set tx type 1
[2010-10-04 18:48:40.256] DEBUG[3903] app_fax.c: FLOW T.30 Changing from state 3 to 2
[2010-10-04 18:48:40.800] DEBUG[3903] app_fax.c: T38 down, finishing
[2010-10-04 18:48:40.800] DEBUG[3903] app_fax.c: Loop finished, res=4
[2010-10-04 18:48:40.800] DEBUG[3903] app_fax.c: Fax phase E handler. result=0
[2010-10-04 18:48:40.804] DEBUG[3903] app_fax.c: Fax transmitted successfully.
[2010-10-04 18:48:40.804] DEBUG[3903] app_fax.c:   Remote station ID: 123456789
[2010-10-04 18:48:40.805] DEBUG[3903] app_fax.c:   Pages transferred: 1
[2010-10-04 18:48:40.805] DEBUG[3903] app_fax.c:   Image resolution:  8031 x 7700
[2010-10-04 18:48:40.805] DEBUG[3903] app_fax.c:   Transfer Rate:     14400
[2010-10-04 18:48:40.806] DEBUG[3903] app_fax.c: FLOW T.30 Changing from state 2 to 32
[2010-10-04 18:48:40.806] DEBUG[3903] app_fax.c: FLOW T.30 Changing from phase T30_PHASE_E to T30_PHASE_CALL_FINISHED
[2010-10-04 18:48:40.806] DEBUG[3903] app_fax.c: FLOW T.38T Set rx type 13
[2010-10-04 18:48:40.806] DEBUG[3903] app_fax.c: FLOW T.38T Set tx type 13
[2010-10-04 18:48:40.806] DEBUG[3903] app_fax.c: FLOW T.38T FAX exchange complete
[2010-10-04 18:48:40.806] WARNING[3903] app_fax.c: Transmission error
[2010-10-04 18:48:40.807] DEBUG[3903] pbx.c: Spawn extension (outgoing,s,2) exited non-zero on 'SIP/sipy_246035404-00000010'
{noformat}
Comments:By: Matt Jordan (mjordan) 2015-02-26 09:34:24.027-0600

Per the Asterisk versions page [1], the maintenance (bug fix) support for the Asterisk branch you are using has ended. For continued maintenance support please move to a supported branch of Asterisk. After testing with a supported branch, if you find this problem has not been resolved, please open a new issue against the latest version of that Asterisk branch.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions

Additionally, {{app_fax}} has been supplanted by {{res_fax}}, which provides the same dialplan applications as well as a better facade over {{res_fax_spandsp}}. As such, {{app_fax}} is an extended support module, and may not receive much attention. If you find this is still a problem in a supported branch with {{app_fax}}, you may want to consider migrating to {{res_fax}}, which is unlikely to exhibit the same issues.