Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

WinFax Pro waking someone up over and over

Status
Not open for further replies.

jjwild

Programmer
Sep 7, 2001
115
US
We are sending faxes from VB 6 using WinFax Pro. This is done with no user interaction.

If a fax fails to be sent, we want to know why – particularly if it turns out that the telephone number is incorrect and a real live person answered the phone instead of a fax machine. I know someone whose system called somebody every 10 minutes all night long and I want to avoid that.

The problem is that the error codes we get by doing SendObj.GetMessageErrorCode seem to be imprecise and unreliable. It seems that error 11, “No Answer”, covers both a person answering the phone and the line ringing without being answered. Also, we sometimes are given an error 4, “Line busy”, instead of error 11, when a person answers the phone.

Anyone have any information on how we could get more exact and consistent error information from WinFax on why a fax was not sent?

Also, are there any standards on how often and how many times to retry to send a fax that could not go through? I would guess that there is little downside to retrying a busy phone number many times, just want to see if there are any gotcha’s I am not considering.

Thanks,

Aaron
 

Bitfax's default was 3 tries. You could set it to other values, but...

Good Luck

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top