NANPA (US+Canada) only :(
Caller ID Made Simple
41–50 of 66 posts
Re: Caller ID Made Simple
#42Earlier quoted context omitted.
504 Gateway Timeout would be the obvious one, since if I'm reading this correctly it's essentially a timeout of zero; 5xx status codes are indicative of retriability later on. But I think that sort of performance would make the free tier essentially worthless. “All you have to do is hit our API endpoint, and BAM, you get results back.” Except you really don't. Analogy: a caching DNS resolver that returned an instant…
> But I think that sort of performance would make the free tier essentially worthless. Not at all. It lets you try out the API, figure out if it works for you, and get back "best effort" results. That seems perfect for a free tier.
Re: Caller ID Made Simple
#43Earlier quoted context omitted.
An Android app is currently in development, and will be released free of charge. We are having an issue, however, because non-GSM carriers rarely allow data transmissions during a voice call, including the ringing state of incoming calls.
Without Voice-over-LTE, I'm not sure how you're going to get around it. It's not a carrier limitation, it's a limitation of CDMA radios and implementations.
Also, there are many applications in the market that does exactly this. I haven't installed any of them since I basically don't trust anyone with "read/write contacts" and "full internet access" at the same time (perfectly valid permissions for apps like this, but that doesn't mean I trust them).
A search for "vemringde" gives you four apps that targets Sweden specifically (so they are probably quite useless outside of Sweden), one of them mentions that it only works while having a 3G connection.
Re: Caller ID Made Simple
#44Earlier quoted context omitted.
Without Voice-over-LTE, I'm not sure how you're going to get around it. It's not a carrier limitation, it's a limitation of CDMA radios and implementations.
Well, I've often used my mobile internet at the same time as talking in the phone (although it fails sometimes (and I don't have LTE)). Also, there are many applications in the market that does exactly this. I haven't installed any of them since I basically don't trust anyone with "read/write contacts" and "full internet access" at the same time (perfectly valid permissions for apps like this, but that doesn't mean I…
Re: Caller ID Made Simple
#45Earlier quoted context omitted.
Without Voice-over-LTE, I'm not sure how you're going to get around it. It's not a carrier limitation, it's a limitation of CDMA radios and implementations.
Well, I've often used my mobile internet at the same time as talking in the phone (although it fails sometimes (and I don't have LTE)). Also, there are many applications in the market that does exactly this. I haven't installed any of them since I basically don't trust anyone with "read/write contacts" and "full internet access" at the same time (perfectly valid permissions for apps like this, but that doesn't mean I…
Re: Caller ID Made Simple
#46Randall, This looks remarkably easy to use. Just a small tip: On opencname's home page, you suggest users try the following API call: $ curl https://api.opencnam.com/v1/phone/2024561111 US GOVERNMENT I tried it and received a different result: $ curl https://api.opencnam.com/v1/phone/2024561111 DIST OF COLUMBI Perhaps you should update your home page to reflect this?
Hey Adley, thanks for the comment! I'll update the page shortly.
"Sorry, not implemented yet. Please append "?format=json" to your URL."
When I did that it worked.
Re: Caller ID Made Simple
#47This is the first API that I've encountered that works with cellphone numbers. I can see this being integrated into Android for incoming calls from unknown cellphone numbers.
Re: Caller ID Made Simple
#48Re: Caller ID Made Simple
#49Earlier quoted context omitted.
Hey Adley, thanks for the comment! I'll update the page shortly.
When I tried it I got this: "Sorry, not implemented yet. Please append "?format=json" to your URL." When I did that it worked.