The problem that we was encountered is the following that some fax
have to be retransmitted due to some connection/transmission errors.
As I understand, on transmission the Spandsp/Callweaver returns the
value of PHASE into PHASEESTATUS variable with code of error described
in the header file "spandsp/t30.h".
There are about 62 types of errors divided in 7 groups. Until now
everything is perfectly clear.
Now the question is

Is possible to define the groups of PHASE values which should generate
the retransmission of fax?

[...]
Is possible to define the groups of PHASE values which should generate
the retransmission of fax?

"Far end is not...", "Far end cannot...", "Far end... not acceptable"
and all the TIFF file errors are things that indicate a simple retry is
surely not going to get any further.

All other errors are basically "something went wrong" to anyone who
just wants to send a fax. It may be a disagreement between the end
points as to what the spec says, it may just be a noisy line. Pages may
have been received and printed at the remote or they may simply have
been discarded with no indication that an attempt was ever received. So
_limited_ retries are probably worth attempting but don't go overboard
(it's really annoying to keep getting all but the last page of a fax
over and over and over... )

means that the fax transmission failed during the current session and
MUST be retransmitted. So the second question is

Is there any expanded manual/list of PHASE errors description which
explains the meaning of every error in more profound way, not just "17
- Received a DCN while waiting for a DIS"???

If you read all the standards . They all amount to "fail" anyway. The
precise reasons why a timer expired or the two devices got out of step
tend to be unimportant unless you're trying to debug the protocol stack
on one of them. Just do the <n> retries at an exponentially increasing
intervals thing. If it still fails get a human to ask, "Is there a
problem with your phone lines?", "Do you have a different model of fax
machine we could try?", "Have you heard of email?", "Please login to our
website and download...".

Ironically enough, last time I needed to send a fax I was able to send
it via the remote party's email-to-fax gateway so they faxed it
internally to themselves. Apparently just printing it out wasn't good
enough?!?

Thank again Mike.I just selected all the errors that happened until now (it's about 30% of the whole list) and selected manually which error generated the resend with a default policy NO resend!! Hope that it will work for me.

Quote:

Ironically enough, last time I needed to send a fax I was able to send
it via the remote party's email-to-fax gateway so they faxed it
internally to themselves. Apparently just printing it out wasn't good
enough?!?

[...]
Is possible to define the groups of PHASE values which should generate
the retransmission of fax?

"Far end is not...", "Far end cannot...", "Far end... not acceptable"
and all the TIFF file errors are things that indicate a simple retry is
surely not going to get any further.

All other errors are basically "something went wrong" to anyone who
just wants to send a fax. It may be a disagreement between the end
points as to what the spec says, it may just be a noisy line. Pages may
have been received and printed at the remote or they may simply have
been discarded with no indication that an attempt was ever received. So
_limited_ retries are probably worth attempting but don't go overboard
(it's really annoying to keep getting all but the last page of a fax
over and over and over... )

means that the fax transmission failed during the current session and
MUST be retransmitted. So the second question is

Is there any expanded manual/list of PHASE errors description which
explains the meaning of every error in more profound way, not just "17
- Received a DCN while waiting for a DIS"???

If you read all the standards . They all amount to "fail" anyway. The
precise reasons why a timer expired or the two devices got out of step
tend to be unimportant unless you're trying to debug the protocol stack
on one of them. Just do the <n> retries at an exponentially increasing
intervals thing. If it still fails get a human to ask, "Is there a
problem with your phone lines?", "Do you have a different model of fax
machine we could try?", "Have you heard of email?", "Please login to our
website and download...".

Ironically enough, last time I needed to send a fax I was able to send
it via the remote party's email-to-fax gateway so they faxed it
internally to themselves. Apparently just printing it out wasn't good
enough?!?

Thank again Mike.I just selected all the errors that happened until now (it's about 30% of the whole list) and selected manually which error generated the resend with a default policy NO resend!! Hope that it will work for me.

Quote:

Ironically enough, last time I needed to send a fax I was able to send
it via the remote party's email-to-fax gateway so they faxed it
internally to themselves. Apparently just printing it out wasn't good
enough?!?