- Line 31: First digit is removed accidentally (the is already removed in line 21) - Line 50: phone_country_code_convert isn't really implemented.
Our solutions will help you: Our phone standardization/validation solution tests your phone numbers against international phone datasets that we license.
By utilizing these datasets we are able to append geographic, carrier and additional information to your international phone numbers.
(and not giving the country code is the only way I can get the phone number validated) My client wants to output the phone numbers like this: 32 (0) 12345678 .
I'm not sure the brackets are even possible using this module.
(Maybe a good regular expression will do it)I'm also looking into this. Aside from the comments in #1 there is also a typo on line 130. However, I don't like the current approach in int, which depends on phone.to check the number format for each individual country (line 50: module_load_include('inc', 'phone', 'phone.'. The main reason to use the international standard is just to avoid the problems with formatting for individual countries and use a generic solution.
If the module maintainer agrees with that, I propose to make a patch to have a basic check for the phone format (like in #1) an remove the dependencies on other country-specific include files.
You can also use a short answer field instead of a phone number field, but the phone number will not auto-format or be validated.
I have to say that the validation function 'valid_int_phone_number($phonenumber)' in inc has many issues and doesn't work as proposed.
With Global-Z’s Phone Number Validation solution you can validate and standardize your phone numbers internationally.