July 24, 2021, 12:53:55 am *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1]
  Print  
Author Topic: SOLVED: callerid from obi110 to my USR modem  (Read 20202 times)
sundansx
Newbie
*
Posts: 14


« on: March 07, 2011, 06:33:05 pm »

I have a phone line splitter hooked up to my phone port on my obi110 with one port hooked up to my phone and the other to a USRobotics 5685 V92 modem.  I use it to extract callerid to my PC.  This worked great on my Vonage Motorola adapter.  Using the same setup and config hooked to the obi110, the caller id is not coming through entirely.  here is what I get hooked to the OBI:
at#CID=1
OK
RING
DATE = 0307
TIME = 1825
Notice there is no Name/Number field.  Oddly the number is displayed on my phone, but it has an unknown character at the beginning.

As another line of though, any one know how to extract callerid from an obi110 via the web or ethernet interface?
« Last Edit: March 09, 2011, 02:29:11 pm by OBi-Guru » Logged
QBZappy
Hero Member & Beta Tester
*****
Posts: 2316



« Reply #1 on: March 07, 2011, 07:08:53 pm »

Hi,

Look here: General Support > Feature Requests > Support for notification popups on computers

You will find an open source project which captures CID from info contained in SIP. Uses packet sniffing approach. There are a couple of links if you are interested. Clever use of packet analysis. To date it seems the only method anyone has suggested that might work which is ready made.

Logged

Owner of the 1st OBi110/100 units in service in Canada & South America. 1st OBi202 on my street. 1st OBi1032 in Montreal.
sundansx
Newbie
*
Posts: 14


« Reply #2 on: March 07, 2011, 11:01:32 pm »

I noticed there was a firmware upgrade that I missed.  installed it and all features including this one are working good.
Logged
QBZappy
Hero Member & Beta Tester
*****
Posts: 2316



« Reply #3 on: April 08, 2011, 08:36:20 pm »

sundansx,

Hi,

What are you using to extract the CID, and how to you use the call info. Are you passing it over the network as a screen pop?
Logged

Owner of the 1st OBi110/100 units in service in Canada & South America. 1st OBi202 on my street. 1st OBi1032 in Montreal.
sundansx
Newbie
*
Posts: 14


« Reply #4 on: May 09, 2011, 10:57:44 pm »

qzippy,
sorry for the late reply, but I am using a usr modem with callerid hooked to my active phone port on the obihai.  Yak is running on a pc attache dto the modem.  Yak can send caller id notifications to other computers running yak in client mode.  Yak provides a pop-up on both machines.
Logged
QBZappy
Hero Member & Beta Tester
*****
Posts: 2316



« Reply #5 on: May 09, 2011, 11:40:16 pm »

sundansx,

Cool. Thanks for the reply. You should mention it in this thread:
Alternate uses for the Line Port for people who don't need it for POTS line

http://www.obitalk.com/forum/index.php?topic=85.0
Logged

Owner of the 1st OBi110/100 units in service in Canada & South America. 1st OBi202 on my street. 1st OBi1032 in Montreal.
MichiganTelephone
OBi110 Beta Testers
***
Posts: 484


« Reply #6 on: May 10, 2011, 10:08:05 am »

Hi,

Look here: General Support > Feature Requests > Support for notification popups on computers

You will find an open source project which captures CID from info contained in SIP. Uses packet sniffing approach. There are a couple of links if you are interested. Clever use of packet analysis. To date it seems the only method anyone has suggested that might work which is ready made.

Not to be a nitpicker, but some of us don't care for the packet sniffing approach.  At the end of the thread you mentioned, both AndroidsOfTara and I separately posted Perl scripts that would extract the Caller ID and allow one to create a popup notification.

I'm not sure why the OP would need to or want to run a separate modem to perform this function, unless perhaps it's just a case of being extremely familiar with that method and not really wanting to dip your toe into the uncharted waters of a different method.  Been there, done that.
Logged

Inactive, no longer posting or responding to messages.  Goodbye and good luck.  Some of my old Obihai-related blog posts have been moved to http://tech.iprock.com - note this in NOT my blog; I have simply given the owner permission to repost some of my old stuff.
QBZappy
Hero Member & Beta Tester
*****
Posts: 2316



« Reply #7 on: May 10, 2011, 10:59:36 am »

MichiganTelephone,

Huh

What is this all about? Why are quoting a post from another thread into this one? No one in this thread is mentioning anything about packet sniffing. That was another discussion unrelated to this thread. As far as I'm concerned I wont be talking about that anymore for fear of anyone accusing me of hijacking that thread. Congrats on the Perl script,  FWIW it still is too tecky for  some. I think that YAK+CID modem is another clever way of getting the same results if all you want is CID over the lan. Keep an open mind about other ways of achieving results. It may or may not be the most elegant/efficient way of accomplishing network CID, but there is no way of denying that it is a proven solution that works with little effort.

I think you are misunderstanding this thread. There is no packet sniffing involved with this solution.

No need to bring this up anymore. I agree with you that you are coming off as a nitpicker.
Logged

Owner of the 1st OBi110/100 units in service in Canada & South America. 1st OBi202 on my street. 1st OBi1032 in Montreal.
MichiganTelephone
OBi110 Beta Testers
***
Posts: 484


« Reply #8 on: May 10, 2011, 11:04:50 am »

MichiganTelephone,

Huh

What is this all about? Why are quoting a post from another thread into this one? .....

Excuse me? Who is quoting a post from another thread?  Read the second message in this thread - that is the one I quoted.  Is that or is that not your message?

I'll admit that I sometimes screw up in online forums and accidentally misquote someone, but this was not one of those times.

Could it be that you originally intended to post your message in a different thread?  Because it does seem a bit out of place here.
« Last Edit: May 10, 2011, 11:06:40 am by MichiganTelephone » Logged

Inactive, no longer posting or responding to messages.  Goodbye and good luck.  Some of my old Obihai-related blog posts have been moved to http://tech.iprock.com - note this in NOT my blog; I have simply given the owner permission to repost some of my old stuff.
QBZappy
Hero Member & Beta Tester
*****
Posts: 2316



« Reply #9 on: May 10, 2011, 11:17:21 am »

MichiganTelephone,

I'm not sure why the OP would need to or want to run a separate modem to perform this function, unless perhaps it's just a case of being extremely familiar with that method and not really wanting to dip your toe into the uncharted waters of a different method.  Been there, done that.

Hi, I was addressing this part of your reply. His solution does not require packet sniffing. I got the impression that you were thinking "packet sniffing" when you saw the words modem+CID in the same sentence. We should stop this now as this is serioulsy off topic.

Peace.
Logged

Owner of the 1st OBi110/100 units in service in Canada & South America. 1st OBi202 on my street. 1st OBi1032 in Montreal.
MichiganTelephone
OBi110 Beta Testers
***
Posts: 484


« Reply #10 on: May 10, 2011, 11:37:06 am »

Hoo boy.  Roll Eyes My second paragraph was only a comment on the fact that in both his original post, and in the fifth post from the top of the page, he mentions that he is "using a usr modem with callerid hooked to my active phone port on the obihai" (quoting from the fifth message from the top of this thread) and I was just trying to make the observation that there are other ways to accomplish the same thing without using a separate piece of hardware (but if that's the way he prefers to do it, that's fine). So I believe that my response was on topic, but that you jumped on me perhaps without fully understanding what I was replying to.  I'm not holding it against you (I occasionally screw up in online posts too) and as this thread is now drifting into pointlessness, I agree it's probably time to bring it to a merciful end.
Logged

Inactive, no longer posting or responding to messages.  Goodbye and good luck.  Some of my old Obihai-related blog posts have been moved to http://tech.iprock.com - note this in NOT my blog; I have simply given the owner permission to repost some of my old stuff.
sundansx
Newbie
*
Posts: 14


« Reply #11 on: May 24, 2011, 09:51:41 pm »

Caller ID problem is back again with the latest firmware update.  I put a support request in again.
Anyone else experience this?  
Does syslog contain caller-id info yet?

Edit:  call is shown in the web interface with full data (minus name lookup, of course).  shows on my uniden phone, just not on the usr modem, same as last time.  Just ran kiwi syslog and answered my own question - no callerid.  they really need to add this..seems like it would be simple.
« Last Edit: May 24, 2011, 10:22:31 pm by sundansx » Logged
freetalk
OBi110 Beta Testers
***
Posts: 11


« Reply #12 on: May 25, 2011, 10:06:35 am »

Hi sundansx,

  There has been a change on GV caller id in the latest firmeware: Since there was no caller id name field from GV, the caller id name field was left empty in the latest release (instead of being duplicated from number field as in earlier firmwares). 

  It seems your modem (or PC app) might have problem with caller ids that didn't have name field.
Logged
sundansx
Newbie
*
Posts: 14


« Reply #13 on: May 27, 2011, 10:42:59 pm »

that could be the problem.
Obihai:  Please add a option to add this back in the next firmware.
Logged
jimates
OBi110 Beta Testers
***
Posts: 1610


« Reply #14 on: May 28, 2011, 10:07:29 am »

I've glanced at this thread several times in the past. I still can't figure out what I must be missing.

I thought the problem before was that the Obi delivered the caller id number with the + in front. That is no longer happening.

Edit:  call is shown in the web interface with full data (minus name lookup, of course).  shows on my uniden phone, just not on the usr modem, same as last time.

If the Obi delivers the caller id number to the phone port (verified as showing on phone), anything more would be a problem at the modem. Not controllable by the Obi.
Logged
QBZappy
Hero Member & Beta Tester
*****
Posts: 2316



« Reply #15 on: May 28, 2011, 10:27:00 am »

jimates,

Although not directly an OBi related problem, as freetalk mentions above, the OBi can duplicate from number field as in earlier firmwares if name field is not present in GV. This little tweak should work. This would make the OBi more compatible with the USR modem. 
Logged

Owner of the 1st OBi110/100 units in service in Canada & South America. 1st OBi202 on my street. 1st OBi1032 in Montreal.
sundansx
Newbie
*
Posts: 14


« Reply #16 on: June 10, 2011, 12:51:30 am »

Well got fed up with whole modem thing with obi, so I decided to write a C++ tray app that scrapes Obihai device webpage for status, does reverse lookup at Whitepages page (needs dev account), and then posts a Yak callerid message to specified clients.  Will put this up on google code or sourceforge in the near future if anyone is interested.

NOW:  If Obihai is listening, please add callerid to syslog output.  That way I can change "scrapes Obi webpage" to "listens to syslog and filters callerid messages".  I dont like polled IO, me want interrupt driven IO.
thanks.
« Last Edit: June 10, 2011, 09:37:21 pm by sundansx » Logged
QBZappy
Hero Member & Beta Tester
*****
Posts: 2316



« Reply #17 on: June 10, 2011, 06:48:07 am »

sundansx

I will certainly be using it. Thanks for sharing.
Logged

Owner of the 1st OBi110/100 units in service in Canada & South America. 1st OBi202 on my street. 1st OBi1032 in Montreal.
QBZappy
Hero Member & Beta Tester
*****
Posts: 2316



« Reply #18 on: June 29, 2011, 03:36:27 pm »

sundansx,

Hi, any update on your offer of the C++ tray app?
Logged

Owner of the 1st OBi110/100 units in service in Canada & South America. 1st OBi202 on my street. 1st OBi1032 in Montreal.
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC

Advertisement
Advertisement