41–50 of 78 posts
Earlier quoted context omitted.
Hey Jon - Rob from Twilio here. Good feedback - appreciate you sharing. We do have geographic information with each webhook sharing city, state and zip - agree it would be useful to have this in the Lookup resources as well.
Thank Rob, If you did add geographic info, what would it be base on? area code/NXX? How relevant would it be considering LNP?
Really neat! Any plans on open sourcing the formatting library? It's a good functionality, but (at least for me) would mainly be useful for view-layer on-the-fly formatting, and we wouldn't use an remote API request for that. Sort of like Strip's jQuery.payment[1], it would be a simple and clever marketing trick. People searching for a phone number formatting library are just the people you want to sell your services…
Am I missing something or this is just a REST front-end for Google´s libphonenumber[1] ? [1] https://github.com/googlei18n/libphonenumber
It seems to be more than that. For example, I typed in my mobile phone number, and it correctly identified the operator as "Hutchison 3G UK" (i.e. 3), which it now is - but it's a number that was originally Virgin and which has been ported a couple of times since then.
+18005551212
{
"country_code": "US",
"phone_number": "+18005551212",
"national_format": "(800) 555-1212",
"url": "https://lookups.twilio.com/v1/PhoneNumber/+18005551212",
"carrier": {
"type": "mobile",
"error_code": null,
"mobile_network_code": null,
"mobile_country_code": "310",
"name": "ICE Wireless"
}
}
+18005551111
{
"country_code": "US",
"phone_number": "+18005551111",
"national_format": "(800) 555-1111",
"url": "https://lookups.twilio.com/v1/PhoneNumber/+18005551111",
"carrier": {
"type": "mobile",
"error_code": null,
"mobile_network_code": null,
"mobile_country_code": "310",
"name": "Zipwhip"
}
}
Pretty solid! Only minor issues I could spot were: 1. Wrong carrier for my mobile - number started out life with a UK MVNO (sainsbury's mobile), I have since ported it to Virgin UK (another MVNO) but Twillio lists the carrier as being EE (which is sort of correct in so much as that's who Virgin resell capacity from). 2. No carrier type info for UK voip numbers - tried two numbers, one from Telappliant and one from An…
Re: 2, the data is available from Ofcom - maybe if you ask Twilio nicely they'll load it :)
My telco was charging $8/month for visual voicemail, so I opted to buy a Twilio number for $1/month, and set my phone to forward no answer/busy/unavailable to a simple Twilio app I wrote that handles voicemail. When someone leaves me a message, I get an SMS with the message and caller details. I've been using OpenCNAM ( https://www.opencnam.com ) for the caller ID look-up. I implemented something similar for our offi…
Baller hack. fistbump
Earlier quoted context omitted.
Thank Rob, If you did add geographic info, what would it be base on? area code/NXX? How relevant would it be considering LNP?
It would be based on the number itself. Obviously with local number portability this is not super accurate, but we do have some customers that find the data useful nevertheless.
That used to be the curse of Google Voice. They'd only send SMS to a mobile number, but their database for recognizing mobile numbers was terrible.
It does recognize a Twilo number properly, though.
Pretty solid! Only minor issues I could spot were: 1. Wrong carrier for my mobile - number started out life with a UK MVNO (sainsbury's mobile), I have since ported it to Virgin UK (another MVNO) but Twillio lists the carrier as being EE (which is sort of correct in so much as that's who Virgin resell capacity from). 2. No carrier type info for UK voip numbers - tried two numbers, one from Telappliant and one from An…
Re: 1, Sainsbury's Mobile is an MVNO on Vodafone, and Virgin is an MVNO on EE, so strictly speaking that's correct (see my previous answer here about how it's probably getting this info: https://news.ycombinator.com/item?id=9300690 ) Re: 2, the data is available from Ofcom - maybe if you ask Twilio nicely they'll load it :)