G
Guest
I've been monitoring the "faxes going to the wrong recipient" thread .
I have just implemented a helpline that takes calls through ASP.net and
stores data in SQL 2000. A windows service picks up the new calls (jobs) and
performs a mail merge, then sends documents to the local "fax" service - Fax
service manager windows 2003.
We have had the same problem, faxes going to the wrong fax machine - a
machine we've sent to recently, in completely random way. Some Faxes get
through, others go "astray"
The Fax header has the correct phone number on it. We found out there was a
problem once the incorrect recipient sends us the fax back!
Our hardware of choice is the MT5634ZBA-USB "Multitech" USB modem. We've
set up four, two for outgoing, two for incoming. These modems have certified
MS Windows 2003 drivers.
We send at times up to 900 faxes per day, with the fax queue building up to
10 or 60 in length depending on call volumes.
(How may objects do you recommend to set in the queue?)
Another bug. On using the copy tiff method to copy the tiff back to the file
system (to a place where we can reference to show in a web app later), we
iterate through the sent queue collection and call the copy TIFF method of
each object in the queue to a designated file name made up from the original
document name property of the fax job object. (each document has a unique
name based on the call ID) Most of the time we get the right image. Some
times (don't know the percentages) we get given the wrong image. We can see
this by the fact that we rename the Tiff to the original document name, yet
on viewing the image, the wrong document is presented. Since our code works
in most cases, I can only assume that the fax object is "sometimes" passing
back the wrong image. Could this be related to the other issue?
I know you cannot comment on our software development, but rest assured in
95 % of cases this does not happen. We know out code works. So this would
point to a problem with the fax job objects we pull from the server sent
queue. If that can happen, then maybe the recipient phone number could get
mixed up too?
We are in a difficult situation now and have had to resort to printing our
mail merges and faxing manually as we are running a government national
helpline for the UK. Can you shed some light on this first issue?
I have just implemented a helpline that takes calls through ASP.net and
stores data in SQL 2000. A windows service picks up the new calls (jobs) and
performs a mail merge, then sends documents to the local "fax" service - Fax
service manager windows 2003.
We have had the same problem, faxes going to the wrong fax machine - a
machine we've sent to recently, in completely random way. Some Faxes get
through, others go "astray"
The Fax header has the correct phone number on it. We found out there was a
problem once the incorrect recipient sends us the fax back!
Our hardware of choice is the MT5634ZBA-USB "Multitech" USB modem. We've
set up four, two for outgoing, two for incoming. These modems have certified
MS Windows 2003 drivers.
We send at times up to 900 faxes per day, with the fax queue building up to
10 or 60 in length depending on call volumes.
(How may objects do you recommend to set in the queue?)
Another bug. On using the copy tiff method to copy the tiff back to the file
system (to a place where we can reference to show in a web app later), we
iterate through the sent queue collection and call the copy TIFF method of
each object in the queue to a designated file name made up from the original
document name property of the fax job object. (each document has a unique
name based on the call ID) Most of the time we get the right image. Some
times (don't know the percentages) we get given the wrong image. We can see
this by the fact that we rename the Tiff to the original document name, yet
on viewing the image, the wrong document is presented. Since our code works
in most cases, I can only assume that the fax object is "sometimes" passing
back the wrong image. Could this be related to the other issue?
I know you cannot comment on our software development, but rest assured in
95 % of cases this does not happen. We know out code works. So this would
point to a problem with the fax job objects we pull from the server sent
queue. If that can happen, then maybe the recipient phone number could get
mixed up too?
We are in a difficult situation now and have had to resort to printing our
mail merges and faxing manually as we are running a government national
helpline for the UK. Can you shed some light on this first issue?