Ooma False Caller ID Being Sensed Via NetCallerID Device

[BraveSirRobbin]

I've been using Ooma for a few weeks now and am starting to really like it.  One thing I have noticed happening over the last few days is I've been getting false readings into my NetCallerID device, which then triggers HomeSeer to announce 'Call from Unknown' (the phone hasn't even rung).
 
To explain my setup, I have an Ooma Telo device connected to an internet connection in my family room and an Ooma Linx (remote) unit plugged into a Den outlet.  The Telo will 'talk' with the remote Linx unit (sort of like having a second Telo device).
 
I have the NetCallerID box plugged into the phone output of the Linx and HomeSeer then talks with the NetCallerID device via a serial connection (just like it did with my previous land line).
 
I also have my cell phone linked to the Telo via BlueTooth using THIS adapter. Basically this lets the caller ID information from a call I receive onmy cell go to the Telo, which goes to the Linx, which gos to the
NetCallerID unit, which then gets announced via HomeSeer (really cool actually!).
 
The false caller ID logs showing up in HomeSeer have the following text:
 

Date://2013  Name:  -msg Off- Number:

The phone never rings and nothing is shown in the Ooma logs showing that a call has been received.
 
It seems like the Ooma Telo unit is broadcasting some sort of status of 'something' somehow (other than a received phone call).  I tried disabling the BlueTooth from my cell (un-linking it from the Telo device) to eliminate that as a source and it still continued).
 
Has anyone else experienced this?

 

[pete_c]

I utilize an Ooma Telo with a netCID and Homeseer but I do not utilize an Ooma Linx.  NetCID has been working fine. 
 
Wondering if you tested with the NetCID plugged into the Ooma Telo?
 
I did have some CID issues initially with installation for a couple of weeks. 
 
Opened a ticket with Ooma, waited a couple of days with no resolution the I escalated issue and it was resolved the next day.
 
I do have a generic DECT phone connected to it and no CID shows up on the phone.  But its not an Ooma DECT phone.
 
Looks like they may have been updating or in the process of updating the firmware a couple of weeks back and that might be why you are having issues?
 
http://www.ooma.com/forums/viewtopic.php?f=9&t=15262
 
I am at firmware version: 66221 if that helps any.

 

[BraveSirRobbin]

Thanks for the reply Pete.  I'll check my firmware version and power down the device, wait a bit and power it back up (that should update it to latest firmware).
 
I really can't conveniently connect the NetCallerID to the Telo, but I guess I could 'rig it' if needed.
 
I do have a newer phone connected to the Linx with the NetCallerID device (via a "Y" adapter) and interestingly, it does not show any callerID info.
 
I did notice the NetCallerID would display "message waiting" if there indeed was a message waiting on the Telo machine, so I know the Linx is somehow getting some type of status info from the Telo.

 

[BraveSirRobbin]

Hmmm, interesting...I rebooted the telo device and when it rebooted it caused the exact same error as I described in my first post (with the exact same 'false' callerID info).  Power has not fluctuated at all in this house btw.
 
So, this is definitely some sort of 'status' broadcast that is being picked up by the NetCallerID box.

 

[pete_c]

Here I have my Ooma Telo in the basement adjacent to the incoming telco stuff. 
 
It is inside of the network behind the firewall and does go thru a sip proxy on its way out to internetlandia.
 
Do you have the Ooma DECT phone set up with the Linx device?

 

[BraveSirRobbin]

No I just have a regular wireless phone connected to it with that NetCallerID unit.
 
How did you find the firmware revision for the Telo?

 

[pete_c]

Its on the main web page gui for the Telo; upper right hand corner.
 
 

 

[[email protected]]

It appears that the NetCallerID may not properly handle on hook message waiting indicator messages. The Telo will send these on reboot or when the message count changes in the VM mailbox so that the attached phone can put the message waiting light in the proper state if has one. It would be interesting to know if the NetCallerID works correctly with the Telo phone port vs the Linx. The FXS interface chip on each is different so there may be some issue there.
 
Mac

 

[BraveSirRobbin]

It appears that the NetCallerID may not properly handle on hook message waiting indicator messages. The Telo will send these on reboot or when the message count changes in the VM mailbox so that the attached phone can put the message waiting light in the proper state if has one. It would be interesting to know if the NetCallerID works correctly with the Telo phone port vs the Linx. The FXS interface chip on each is different so there may be some issue there.
 
Mac

Thanks for the reply Mac and welcome to CocoonTech!
 
Problem is, this hasn't happened in a while now and I think you are onto something with the "message waiting" translation.
 
I'll look at this closer, I just wish it would happen with more frequency as it's hard to troubleshoot.

 

[pete_c]

There is an option (mine is checked off) on a "Enhanced Inbound Caller-ID:"
 
I have no idea what this is.

 

[tmbrown97]

Problem is, this hasn't happened in a while now and I think you are onto something with the "message waiting" translation.
 
 
I'll look at this closer, I just wish it would happen with more frequency as it's hard to troubleshoot.

This is easy enough to test - call and leave yourself a voicemail from your cell phone while you're watching the CID device - then also check your voicemail and clear the message - maybe even via the computer or something so you know the phone isn't in use.

I just did some general web searching and there are code snippets where people are trying to handle the Message Waiting indicator code, and what you're seeing is what they're looking for to indicate status - so it looks like you're on the right track - but apparently the NetCallerID box handles the MWI just fine - look at the message - it's saying "-msg Off" to indicate that the MWI should be off; leave a VM and check and you'll see a "-msg On" too. It's your homeseer driver for the NetCallerID that doesn't know how to handle that message.

I don't know enough about homeseer but it looks like it's easy enough to write your own driver. On some handy Home Automation forum, I found one script that could be modified easily enough to add the MWI detection codes instead of handling them as unknown.  
 
Here's a code example I found for misterhouse specifically for detecting the MWI too.

 

[BraveSirRobbin]

Yea, I could write a condition if it is truly catching that string in the NetCallerID script to just ignore it.  Thanks.

 

[pete_c]

Here is the raw serial data from my NetCID box connected to the Ooma Telo direct "phone port".
 
I called myself from another telephone line.
 
Personally I would test the "phone port" CID connection with the NETCID box then try the Linx DECT connection to see the difference?
 
Note too that my generic DECT phone hook up doesn't get anything for a CID when a call comes in.
 
 

2013-03-16 11:03:32Z ... Raw data from COM port = [###DATE...NMBR...NAME   -MSG OFF-+++]
2013-03-16 11:03:32Z ... Name = |-MSG OFF-|, Number = ||
2013-03-16 11:04:10Z ... Raw data from COM port = [###DATE...NMBR...NAME   -MSG OFF-+++]
2013-03-16 11:04:10Z ... Name = |-MSG OFF-|, Number = ||
2013-03-16 11:04:25Z ... Raw data from COM port = [###DATE03161105...NMBR1235551212...NAMElastname,firstname+++]
2013-03-16 11:04:25Z ... Name = |lastname,firstname|, Number = |1235551212|