Forum Replies Created
-
Posts
-
Have signed up for caller ID. So my thought is I can block certain numbers that are using commas. I have reproduced the error by faxing faxes to my office with and without commas. These faxes come through fine on the host, but the ones with commas crash the client machines. Any way to modify the program to use a different deliminator such as a carrot? Did symantic open source the program when the sundowned it? Or am I stuck looking into a new fax program? And if so, what would you recommend? Thanks for your time!
You are correct. Each name field matches the CSID. These senders are not in our phone book. I haven’t tried sending a fax myself with a comma in it, will try this weekend when the business is closed. Have checked on signing up for caller ID. Doubt that will help, but I can block calls from businesses using a comma in there CSID. Will check back this weekend. Thanks.
The name field must be something sent with the fax. Sometimes it is a number, sometimes blank, and sometimes a name. It matches the Remote CSID in all the faxes. The caller ID would be under the “Phone Number/Caller ID” field. And this is blank for all the faxes.
You should be able to reproduce the problem by filling in the Remote CSID with a comma character. I am thinking it is a software deliminator problem on the client machine as I can reproduce it on both clients. I look forward to your thoughts. Thanks.
I have a Zoom V90 PCI Faxmodem, when I go under properties COM3 is not a choice (and this is where the modem is). This modem is not a WinModem, so I had to enable it under the BIOS. The reason I stayed away from a WinModem is when a fax comes in the system freezes for several seconds. With the Zoom you can’t tell because it has its own processor. Anyways, I don’t think this will fix the problem because I don’t have caller ID service at the office. Let me know when you replicate the problem and if there is anything different I can do. Maybe it might be as simple as signing up for Caller ID. Thanks for your time.
Here are some examples:
Aetna, Inc
Hall, CM
Goodroad, BillThe Phone Number/CallerID field is empty in all faxes.
The Name filed and Remote CSID contain the same information as in the above examples.
I isolated the problem faxes out of several hundred ones, and soon realized the ones with commas were causing the problem.
These faxes can be viewed on the host just fine, but never get the chance on the client machine because when you click on “show all messages” in the “WinFax Pro Receive” window the program crashes on the client machine. The only way to reset the “WinFax Pro Receive” window is to reboot the client computer. This is the box that pops up on the client machine when you click on the “Receive” and then “Manual Receive Now” on the menu bar.
The client windows work perfectly fine as long as there are no faxes with a comma on the host machine. It seems to be a software problem listing the faxes in the “WinFax Pro Receive” window. So if there is a problem fax with a comma, you never have the chance to veiw any of the faxes on the client machine because the program window “WinFax Pro Receive” causes the crash.
I have no idea if the default button “Show unread messages only” would also cause the same problem when one of these comma faxes are received and unread prior to the client logging on. I do know, however, you can have read messages with a comma in it on the host machine and the “WinFax PRO Receive” window will pop up and you can read and download new messages. The trouble starts as soon as you click on the “Show all Messages” button AND you have a fax with a comma in the Name and/or CSID on the host machine.
Is there a workaround? Thanks for your time.
I sorted through all the faxes, and found the ones causing problems have a name with a comma in it. I think it is a software issue on the client to crash when a comma is seen. Maybe the comma was used as a deliminator or something. Is there anything that can be done to solve the problem?
