fix: add PT m2m

[mdmourao]

• Country: PT
• Example number(s) and/or range(s): +35149XXXXXXXXXX
• Number type ("fixed-line", "mobile", "short code", etc.): mobile (m2m)
• For short codes, cost and dialing restrictions: NA
• Where or whom did you get the number(s) from: ANACOM
• Authoritative evidence (e.g. national numbering plan, operator announcement): ANACOM
  pdf
  ANACOM 1
  ANACOM 2
• Link from demo (http://libphonenumber.appspot.com) showing error: DEMO

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[mdmourao]

https://issuetracker.google.com/issues/516844150

[mdmourao]

the pattern is: 49 XXX XXXX XXX

source: NOS

[mdmourao]

NEW Results for +351499300003676

Phone Number entered: +351499300003676

Default Country entered: PT

Language entered: en

Parsing Result (parseAndKeepRawInput())
country_code	351
national_number	499300003676
extension
country_code_source	FROM_NUMBER_WITH_PLUS_SIGN
italian_leading_zero	false
number_of_leading_zeros	1
raw_input	+351499300003676
preferred_domestic_carrier_code

Validation Results
Result from isPossibleNumber()	true
Result from isPossibleNumberWithReason()	IS_POSSIBLE
Result from isValidNumber()	true
Result from isValidNumberForRegion()	true
Phone Number region	PT
Result from getNumberType()	MOBILE

Formatting Results
E164 format	+351499300003676
Original format	+351 49 930 0003 676
National format	49 930 0003 676
International format	+351 49 930 0003 676
Out-of-country format from US	011 351 49 930 0003 676
Out-of-country format from CH	00 351 49 930 0003 676
Format for mobile dialing (calling from US)	+351 49 930 0003 676
Format for national dialing with preferred carrier code and empty fallback carrier code	49 930 0003 676

AsYouTypeFormatter Results
Char entered: '+' Output: "	+
Char entered: '3' Output: "	+3
Char entered: '5' Output: "	+35
Char entered: '1' Output: "	+351
Char entered: '4' Output: "	+351 4
Char entered: '9' Output: "	+351 49
Char entered: '9' Output: "	+351 49 9
Char entered: '3' Output: "	+351 49 93
Char entered: '0' Output: "	+351 49 930
Char entered: '0' Output: "	+351 49 930 0
Char entered: '0' Output: "	+351 49 930 00
Char entered: '0' Output: "	+351 49 930 000
Char entered: '3' Output: "	+351 49 930 0003
Char entered: '6' Output: "	+351 49 930 0003 6
Char entered: '7' Output: "	+351 49 930 0003 67
Char entered: '6' Output: "	+351 49 930 0003 676

PhoneNumberOfflineGeocoder Results
Location	Portugal

PhoneNumberToTimeZonesMapper Results
Time zone(s)	[Atlantic/Azores, Europe/Lisbon]

PhoneNumberToCarrierMapper Results
Carrier

[jdegger]

https://github.com/google/libphonenumber/blob/master/FAQ.md#what-about-m2m-machine-to-machine-numbers

I don't think they allow m2m

[kkeshava]

Hi,

Thanks for reporting this! This is actually addressed in our documentation:

https://github.com/google/libphonenumber/blob/master/FAQ.md#what-about-m2m-machine-to-machine-numbers

As a result, we'll close this issue, but let us know if we may clarify the answer and update documentation.