Using syslog to get caller id name and number from the OBi110
QBZappy:
etc6849
Not every voip DID will show up in a serach because DID numbers are usually not automatically listed on a CID CNAM database. In order for a DID number to get listed for it to be pickedup by services which search for this info, such as http://freecnam.org/, you need to make the effort to get it listed. In my case I have an account with voipms. They offered to list my voipms number for me. There are other ways to get your DID number listed that you can do yourself. I just did a lookup of my GV tel number on http://freecnam.org, it was not listed. The only numbers I am almost certain you will find are numbers that are listed with PSTN service, and those that have listed their own voip DID numbers.
You can have a look here as reference info.
http://www.locallytype.com/pages/submit.htm#IYPUS
infin8loop:
Good information to know QBZappy.
While probably not anymore reliable for the reasons you mentioned, there is also:
http://cidlookup.com/lookup/2146301210/
The response is a complete webpage. The actual data is html "encoded" (view source on the page and look at the data between the @@@@ comment blocks to see what I mean. You can copy and paste that block into:
http://www.opinionatedgeek.com/dotnet/tools/htmlencode/decode.aspx to see the decoded information. I know this "decode" can be duplicated in vbscript or whatever. I guess they are just trying to slow down trying to screen scrape the page. But then you'd still have to parse it. The page mentions an API, but I'm guessing they want money to use that.
My dad's number comes back as simply "TEXAS" as the callerid name when using this site. It's an AT&T PSTN number he's had for over 30 years. He's actually older than I am, believe it or not. Incoming calls on my AT&T PSTN show his actual name (Lastname Firstname) and no, it's not the phone directory showing it, it shows on a standalone callerid box (remember those?) that's not programmable.
Sorry if this is more information that anyone cares to know. It's already more information than I need to know (grin).
QBZappy, you said "They offered to list my voipms number for me. "... They made me the same offer... for a $10 fee. Did I just not know the secret Canadian handshake or something? Just because I say, "house" and not "hooose" and I say "bus" and not "booose". When I made my initial deposit to voip.ms it triggered a fraud alert text message from my credit card company. At first I didn't put 2 and 2 together and thought the text message was a scam because it had no specific details. So I looked up the fraud number on the bank's website and it wasn't the same as in the text message. I called that number instead. Anyway the alert was actually real. Didn't fit my charging profile I guess. Then I get my statement and there's a 75 cent "foreign transaction fee". I never really thought of Canada as a "foreign" country. I should have used PayPal to avoid the transaction fee.
MRTT:
Obi110. I have Google Voice setup and working on sp1, nothing on sp2. Nothing on line.
Caller ID number appears fine on my phones.
I would like to have it go to my syslog too...
I have my obi setup to send syslog info to my syslogger...
I have 'X_SipDebugOption' parameter set to 'Log All Messages.'
I have tried all the various syslog levels available. I infer level 7 should work. However when calls come in, there is no corresponding syslog info arriving.
I do see some debug info when the OBI110 reboots, like:
SLIC & DAA is initialized
Start Main Service Now
PROV:Auto Update invalid server name()
So what am I missing?
QBZappy:
Quote from: MRTT on October 21, 2011, 08:40:06 pm
Obi110. I have Google Voice setup and working on sp1, nothing on sp2. Nothing on line.
Caller ID number appears fine on my phones.
I would like to have it go to my syslog too...
So what am I missing?
It's been requested a few times before. Obihai has not made the syslog more verbose for some reason. You would expect this to be a relatively easy feature request to provide. What you see in the syslog is what you get. A lot of 3rd party apps/utilities could feed off the syslog output.
infin8loop:
Ok, now I'm confused. This isn't the first time I've seen mention in different threads about not seing callerid number in the syslog. Scroll back in this thread to message http://www.obitalk.com/forum/index.php?topic=1723.msg11147#msg11147 and download it's attached file named obisyslogd-commented.txt. I added comments to this syslog starting with ****COMMENT to document each incoming call type. Look for
[2011.10.19 01:54:07] [192.123.1.12] <7> [SLIC] CID to deliver: '' 11231234567 This is a message level 7 from an incoming call over Google Voice. The message data is "raw" straight from the OBi beginning with the <7>. The [date time] and [obi ip iddress] prefix is added by the syslog script. The 11231234567 is a masked callerid number in North America format with a "1" followed by 10 digit phone number (The actual number was correct before I manually masked it). The empty '' denotes that no callerid name was present. I consistently see this message on incoming Google Voice calls. 'X_SipDebugOption' does not have to be enabled but it could be. This syslog was obtained from my OBi110 with X_SipDebugOption=Disable. I get the same basic results no matter if I run my perl syslog script which created this syslog file or the standard syslogd package I installed in Ubuntu linux. The OBi110 is configured with the default Syslog Level 7 (default check box checked). Firmware 1.3.0 (Build: 2586), but it's been working this way for the last couple or so versions at least. I currently have google voice on SP1 and voip.ms on SP2. But it worked the same way with just google voice on SP1 and nothing on SP2. What am I missing??! I doubt it's my mystical programming powers that are making the difference (heh).
Navigation
[0] Message Index
[#] Next page
[*] Previous page