Google Voice (GV) and Caller ID Name Display - Custom Caller ID

<< < (4/8) > >>

bhasden:
Quote from: BobTeatow on February 21, 2012, 02:05:40 pm

Oh!  Well that's better than watching every packet... But it's still polling, which means a lot of wasted cycles, and a worst case delay that is 1/polling_rate.  You're welcome to implement my suggestion, which is much more efficient, responsive and selective!

Linphone is an open source SIP Phone, there are probably others.

If you look into the OBI configuration doc, you will see how to fork calls to any sip provider - which could be one that runs on your own LAN.  Can't be too hard to hack something together.

However, this still doesn't get us the caller name on my telephone set - which is where I want it.  (Unless I only use an Android phone on which I also run something like GrowlID?)   And without the OBI knowing what is going on we don't quite get there...  Of course I could have OBI NOT ring my phone, but pass the call to my own server and then have that server pass the call back to the OBI... but then I may as well toss the OBI!  We really want the function integrated into the OBI.

Agreed that the polling is less than ideal, but right now I have it configured at home to poll once every 5 seconds and it works well. At that rate, checking the OBi device 12 times a minute seems to be worth the tradeoff for simplicity.

It would be great if the OBi device had some sort of API where you could subscribe to be notified of incoming calls and the make modifications to the caller id information during that or some other event.

When I started the GrowlerID project, I was looking at a couple of different ways to accomplish the goal of notifying me of who was calling. One of the approaches I looked at was a device that would be put inline between the OBi and the phone. The device would decode the caller id information when an incoming call was detected and then run code to look up the caller and write out the appropriate caller id information to the line when it was retrieved. While that would be a fantastically interesting and fun project, unfortunately the electronics part is a bit out of my league. I prefer to be as productive as I can be with my limited free time and designing circuits would not allow me to work at maximum efficiency. If someone here has some electronics experience I would be more than happy to work with them on getting such a device working, but I can't be the lead for such a project. The initial research I did on the topic led me to a few project that were built on the Arduino platform that were able to decode the incoming caller id. From there, you'd need to write code to negate the original incoming caller id signal so that the original caller id information is not displayed on the phone. Then, you'd have to look up the caller information and then write the new information out to the line.

A simple diagram of the physical setup:

Code:

                              [ethernet jack]
                                    |
                                    |
[OBi phone jack]----------[caller id lookup device]----------[phone]


QBZappy:
Brian,

If you go that route, the info contained here might be interesting. Technical aspects of CID formatting.
http://www.talkingcallerid.com/ModemDriver.htm

Wouldn't a voice modem do the trick?

bhasden:
Quote from: QBZappy on February 22, 2012, 03:46:30 pm

Brian,

If you go that route, the info contained here might be interesting. Technical aspects of CID formatting.
http://www.talkingcallerid.com/ModemDriver.htm

Wouldn't a voice modem do the trick?


I don't believe a voice modem would work because it would have no way to ring the connected OBi device. If I'm understanding what you're suggesting (I initially thought the same thing), you mean to say that the OBi would connect up to the voice modem which would then connect up to the phone. In that scenario, you have no way to ring the phone.

I actually asked this question to the smart folks over on StackOverflow (limited it's scope to stuff they'd be familiar with). Feel free to check out the answer: http://stackoverflow.com/questions/7988592/make-phone-connected-to-modem-ring

w84no1:
Quote from: bhasden on February 21, 2012, 01:28:57 pm

Quote from: BobTeatow on February 21, 2012, 01:23:17 pm

How does GrowlerID "spy" on my OBI device(s) and/or incoming calls?

(I haven't tried to reverse engineer it.)  One way would be to "promiscuously" read all traffic on the LAN, looking for packets going to the OBI ...  Hmmm...

A much smarter way would be fork every call to a hacked soft-Sipphone and have that sipphone do the CID/name lookup....  For example I have my OBI configured to fork most calls to extension 103 of my VOIP.ms account, which is handled by a SIPURA and a phone in my spare room.... 
Hmmm... I could also fork calls to the hacked-soft Sipphone...


It's really simple actually. It just polls the status page on the device every couple of seconds to see if there is an incoming call. That portion of code was derived from the work of MichiganTelephone (michigantelephone.WordPress.com). It's a very low tech approach but it has been working well for me at home for the past 4 or 5 months.


I use a perl script to monitior the syslog for incoming calls and it works pretty well.  http://www.obitalk.com/forum/index.php?topic=1723.msg17103#msg17103

dcampbe1:
Count my vote too please.  CallerID is so inherently necessary in managing phone traffic AND history.  Incorporating it in any format would be wonderful.  Having a local speed dial directory without it seem a bit moot otherwise.

Thanks for even considering the idea!

Navigation

[0] Message Index

[#] Next page

[*] Previous page