Did you try with ODBC? You should be able to connect to virtually any DB (I successfully tested MS SQL and MySQL when I was developing ODBC support into wphfr).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Wrong. It works. See attachments.
I suggest that you review:
- server firewall rules, if any
- my.cnf (did you comment out the line "bind-address = 127.0.0.1"?)
PS. No write capability, though.
For international contacts, a single fax number field is not enough. We should separate the fax number into:
country code;
area code;
local fax number;
so that Hylafax can handle local and international calls differently. International calls are expensive. They are important to enterprises.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Your request is not clear to me. How is the client supposed to handle these separate fields? Should it prepend the country / area prefix to the local number based on some client side rules, before submitting the number to HylaFAX?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm still confused. There's no point in splitting the number into its components, unless we provide the client with the logic to decide whether a certain component (e.g. the international prefix) is to be sent to the server or not, based on some client-side rule.
But this is the server's job: to normalize a number through dial rules, and then decide where to route the fax. Am I missing something?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Did you try with ODBC? You should be able to connect to virtually any DB (I successfully tested MS SQL and MySQL when I was developing ODBC support into wphfr).
I have checked the built-in ODBC feature. It seems that it cannot connect to a remote Linux MySQL server.
Wrong. It works. See attachments.
I suggest that you review:
- server firewall rules, if any
- my.cnf (did you comment out the line "bind-address = 127.0.0.1"?)
PS. No write capability, though.
Another screenshot
Yet another one.
The configuration in wphfr
I see! I see the trick!
For international contacts, a single fax number field is not enough. We should separate the fax number into:
country code;
area code;
local fax number;
so that Hylafax can handle local and international calls differently. International calls are expensive. They are important to enterprises.
Your request is not clear to me. How is the client supposed to handle these separate fields? Should it prepend the country / area prefix to the local number based on some client side rules, before submitting the number to HylaFAX?
So the address book or address book table structure of your software should be improved.
Here is an example of my other project:
When the user try to select a name from the data base or address book, the receiver's country code and area code will show up on your GUI.
When Winprint GUI user enter a record, he is also required to input country code, area code, fax number separately as different record fields.
I'm still confused. There's no point in splitting the number into its components, unless we provide the client with the logic to decide whether a certain component (e.g. the international prefix) is to be sent to the server or not, based on some client-side rule.
But this is the server's job: to normalize a number through dial rules, and then decide where to route the fax. Am I missing something?
The country list on this planet can vary from time to time. ^^
Also, every country/company handle local/long distance/international call differently.
For instance, the win7 fax simply cannot handle a long string fax number. I must teach it how to dial. ^^
Telling the software the corresponding code is more reliable.