Caller ID Made Simple • Hacker News Board

Re: Caller ID Made Simple

#21

Post by drivebyacct2 » Mon, Apr 09, 2012, 4:14 AM UTC

mwally wrote: post #13

mikeknoop wrote: post #6

Earlier quoted context omitted.

My thoughts exactly! I easily get less than 60 calls per hour so this would be perfect. Interestingly, the caller ID for my number is tied to the first owner of my account before it was transferred to me (which happened many years ago).

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.

Re: Caller ID Made Simple

#22

Post by mwally » Mon, Apr 09, 2012, 4:15 AM UTC

andrewpi wrote: post #20

mwally wrote: post #13

Earlier 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.

It should still work while on Wi-Fi, correct? That would still be an improvement over the status quo (no caller ID).

Yes, the in-development Android app does work when the Android device is on wifi.

Re: Caller ID Made Simple

#23

Post by inghoff » Mon, Apr 09, 2012, 4:18 AM UTC

steveh73 wrote: post #10

Please make it more obvious that this only works for US phone numbers

I just tried it for some numbers around Montreal. Apart from the delayed results issue, it works.

Re: Caller ID Made Simple

#24

Post by mwally » Mon, Apr 09, 2012, 4:23 AM UTC

kcbanner wrote: post #15

mwally wrote: post #13

Earlier 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.

Even a lookup app would be handy for seeing missed calls, etc.

Give us a few more weeks of development for this, and it will be ready. The current working title of the Android app is "FreeCallerID," but we may change this before launch. Just look for the Round OpenCNAM logo to make sure you found the right app.

Re: Caller ID Made Simple

#25

Post by b14ck » Mon, Apr 09, 2012, 4:24 AM UTC

AdleyEskridge wrote: post #14

Randall, 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.

Re: Caller ID Made Simple

#26

Post by b14ck » Mon, Apr 09, 2012, 4:25 AM UTC

samirahmed wrote: post #19

b14ck wrote: post #9

Earlier quoted context omitted.

Hi there. So, I'm the author of this article. Anyhow, for our free-tier users we don't provide realtime lookups. Basically, we'll only return a result if we have a caller ID in our cache. So, if you get a 404 (no output), then try again a few seconds later after we've had time to do the lookup via our backend. Sorry about that! Realtime lookups are currently restricted to API key users only.

> you can't get something working within 5 minutes of vising our website, we've failed our mission. It took me five minutes on the website ... and I had to come back to HN and read the comments to get this working. Don't want to be discouraging, but maybe you should provide this information in the blog/website otherwise you have failed (for me atleast).

Hey samirahmed, thanks for the comment! I'll definitely be updating my blog post and improving the documentation on the website.

Appreciate the feedback.

Re: Caller ID Made Simple

#27

Post by b14ck » Mon, Apr 09, 2012, 4:26 AM UTC

ars wrote: post #12

b14ck wrote: post #9

Earlier quoted context omitted.

Hi there. So, I'm the author of this article. Anyhow, for our free-tier users we don't provide realtime lookups. Basically, we'll only return a result if we have a caller ID in our cache. So, if you get a 404 (no output), then try again a few seconds later after we've had time to do the lookup via our backend. Sorry about that! Realtime lookups are currently restricted to API key users only.

Is there any way to tell the difference between "try again" and "no data available"? And you should have made this MUCH more visible on your website. I initially tried your service, got zero results and dismissed it as a failure. Only after reading here did I realize your service actually does work, I just have to try each query twice.

Hey ars, thanks for the feedback! After reading the comments here on HN (which are incredibly valuable), I'll be making those changes ASAP.

Sorry for the confusion, but thanks again for the feedback. I greatly appreciate it.

Re: Caller ID Made Simple

#28

Post by krrose27 » Mon, Apr 09, 2012, 4:29 AM UTC

I definitely find it interesting.

As somehow it pulls up my (not) apparently unlisted home phone; also, it pulls up family members names for cellphones which are under my name on the contract.

So I am definitely interested in finding out where this data is being taken from?

Re: Caller ID Made Simple

#29

Post by b14ck » Mon, Apr 09, 2012, 4:32 AM UTC

krrose27 wrote: post #28

I definitely find it interesting. As somehow it pulls up my (not) apparently unlisted home phone; also, it pulls up family members names for cellphones which are under my name on the contract. So I am definitely interested in finding out where this data is being taken from?

Hey krrose27, we basically pull the information from a variety of sources, all publicly available. If we can get the caller ID name information, then it means any call made from those numbers to a caller ID capable phone (with caller ID service) will be able to see it also.

Re: Caller ID Made Simple

#30

Post by b14ck » Mon, Apr 09, 2012, 4:33 AM UTC

mikeknoop wrote: post #11

b14ck wrote: post #9

Earlier quoted context omitted.

Hi there. So, I'm the author of this article. Anyhow, for our free-tier users we don't provide realtime lookups. Basically, we'll only return a result if we have a caller ID in our cache. So, if you get a 404 (no output), then try again a few seconds later after we've had time to do the lookup via our backend. Sorry about that! Realtime lookups are currently restricted to API key users only.

You might make this more obvious. Also, you might state how to distinguish between "sorry we need more time to look this up" and an actual 404 or error. HTTP code 202 Accepted seems appropriate for this ( http://en.wikipedia.org/wiki/List_of_HTTP_status_codes )

Hey mike, thanks for the feedback. I'll be working on this tomorrow to get a fix out.

After all the feedback here, I realize how crazy it is to be returning a 404.

Thanks for checking us out, and thanks for the feedback!