Well, it was worth trying. Of course, better handling for errors or stuck pages in a remote machine "should" be easier to work out if error handling were to send whatever is there instead of discarding it.
On Tue, Jul 19, 2011 at 6:45 AM, Joegen Baclor <[email protected]> wrote: > ** > Not familar with how fax works but I've been told FAX is handled by a java > ESL application and not via LUA. > > > On 07/18/2011 09:08 PM, Tony Graziano wrote: > > Are the lua commands for fax located somewhere they can be edited/tested > without a build environment or are they in a binary/jar? If there are user > editable, can someone tell me where they are? > > On Mon, Jul 18, 2011 at 7:40 AM, Tony Graziano < > [email protected]> wrote: > >> I am having a hard time getting folks to adopt this. Here's why: >> >> Any failure during a receive is not sent "as is" like a standalone fax >> machine. >> >> Whether the error occurred due to the sender or receiver, a failed fax to >> a standard fax machine will "print" until it's done, failure or not. Our >> current method is: >> >> <action application="set" data="execute_on_fax_success=lua >> process_fax.lua"/> >> >> when we should also have a method >> >> *<action application="set" data="execute_on_fax_failure=lua >> process_fax.lua"/> * >> >> This way if the sender had a paper jam 25 pages through a 26 page fax, >> they might simply resend the remaining pages and not send the entire fax >> "again". It would also resolve any carrier issues where the DCS or TCF was >> not being responded to. >> >> I think this might be easy to implement, and I think inbound faxes >> "should" behave like a generic fax machine. Whatever I receive, I should >> print (email) for the recipient. Throwing away received pages is somewhat >> wasteful, and makes people think the fax is not working properly, making it >> harder for organizations to adopt. >> >> Comments appreciated: Please see >> http://track.sipfoundry.org/browse/XX-9760 >> >> >> >> -- >> ====================== >> Tony Graziano, Manager >> Telephone: 434.984.8430 >> sip: [email protected] >> Fax: 434.326.5325 >> >> Email: [email protected] >> >> LAN/Telephony/Security and Control Systems Helpdesk: >> Telephone: 434.984.8426 >> sip: [email protected] >> >> Helpdesk Contract Customers: >> http://support.myitdepartment.net >> Blog: >> http://blog.myitdepartment.net >> >> Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 >> >> > > > -- > ====================== > Tony Graziano, Manager > Telephone: 434.984.8430 > sip: [email protected] > Fax: 434.326.5325 > > Email: [email protected] > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > sip: [email protected] > > Helpdesk Contract Customers: > http://support.myitdepartment.net > > Blog: > http://blog.myitdepartment.net > > Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 > > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > > > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.326.5325 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Contract Customers: http://support.myitdepartment.net <http://support.myitdepartment.net>Blog: http://blog.myitdepartment.net Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
