IssueTracker

Thank you for taking the time to improve libphonenumber!

We need more information to fix this. Please see our contribution guidelines: https://github.com/googlei18n/libphonenumber/blob/master/CONTRIBUTING.md

Note that the number you provided doesn't connect and the Wikipedia page you linked to also has a disclaimer at the top stating: This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.

Specifying a phone number that you can call to see that it works is problematic as I would have to know what carrier you are using.  That gets back to the idea of the numbers being "exclusive to the specific carrier”.

Here are some Vonage examples found on https://support.vonage.com/answerslist?topic=Other_Features:
* To obtain the current weather conditions or the 5-day forecast for any U.S. zip code, dial 1-700-WEATHER (1-700-932-8437) from your Vonage phone number.
* Use 1-700-Greetings to send greeting cards to friends and family in the U.S., Canada or Puerto Rico.

Keep in mind that these sample numbers are only likely to work if you are dialing from a Vonage line.

Hi Robert,

Libphonenumber do not support the phone numbers that work only for very limited users i.e only for subscribers of  particular company. Do you think these are VOIP numbers ?

See our [contribution guidelines](https://github.com/googlei18n/libphonenumber/blob/master/CONTRIBUTING.md)
to determine whether something is a real issue, and the details we need to be able to fix it.

I think some will be VOIP and some will not be VOIP.   That would be an implementation detail for the carrier.  It is true that any any given 700 number works only for a limited number of users.  However, 700 numbers in general work for many users.  Thus, it seems odd to me for Libphonenumber to call a 700 number invalid.  Thus I think Libphonenumber would be incrementally better if it allowed 700 numbers to be considered valid.  But 700 number are an odd wrinkle.  I think we'd both be happier if 700 didn't exist at all, but they do.

Due to these 700 numbers not being clearly in line with the rest of our phone number metadata, we need to take a step back and think of the right categorization, attributes and impact on existing APIs. Moreover, quantifying the impact would be immensely helpful since we have other quirky phone number types we don't support in the library yet such as M2M numbers: https://github.com/googlei18n/libphonenumber/blob/master/FAQ.md#what-about-m2m-machine-to-machine-numbers

Until we can reach consensus on all these potential factors, we won't be able to support these numbers, but we'll try to put these 700 numbers into our future planning. In the interim, we'll work on an FAQ to publish on this and collect data on similar numbers in other countries to broaden the scope, which will help us reach a decision and prioritization.

So thanks for reporting this!

Thanks for your help

You're welcome!

I've now added this issue to our FAQ with an explanation plus advice on how we could move forward with this sometime in the future: https://github.com/googlei18n/libphonenumber/blob/master/FAQ.md#what-about-numbers-that-are-only-valid-for-a-set-of-subscribers

So I'll close this in the meantime, but I've referenced this particular issue in the FAQ in order for folks to see what has already been shared before filing a new issue.