I disagree in regards to VOIP companies own the number so they controll all the CID... My experience with the message NO DATA (and yes I am well aware of the pay to play, why else do you thing we are all here lol), just simply indicates that the caller ID is obviously not being sent correctly from the telco switch whatever the back end configuration is needed.southsound wrote:amoney wrote:I dont entirely know the back end of how Ooma has its arrangments with other vendors
And when there is a issue, the 3rd party reseller ultimately contacts the Telco that actually controlls the number etc. This is a over simplification. The telco infrastructure is very complex, think of it as alot of middle men.
NO VoIP company currently owns theie own phone numbers.
The delay that was mentioned earlier is the configuration of the caller id to work correctly (the party controlling the number has to configure this, and may take a day or two etc) nothing to do with your equipment.
True for OUTGOING CID.
I remember before I got Caller ID on my landline, it said NO DATA also.
Also true becaues most landline telcos will not send CID unless you pay for it. CID is a great revenue source.
Now the call logs in MYOOMA I can not explain.
What is obvious is that ooma DOES have the CID information and something is preventing the OP's phone from receiving and decoding it. What exactly the problem is would be what the OP is trying to find out.
Ooma is simply a 3rd party reseller. Just as with other 3rd party telecom reseller even if they "own" the number, if something goes wrong, guess whos truck rolls up to check the line... ATT.
Same goes for internet, when I see hops getting timeouts etc, someone on the the back end needs to reboot a switch etc, not necessarily comcast.
There are alot of middle men to all of this. Ooma does not have complete control over all the lines.
Actually the call log is not that surprising, as a telco has access to log data in general, but if the CID is not configured then the user obviously wont see that displayed, the point is what we see in the Ooma telephone logs may not be CID but just from telco logs.
Bottom line OP needs to call Ooma support.
I have read other Ooma users referrence similar issue where Ooma needs to contact a partner whomever to strieghten out somehting... even though Ooma "owns" the number.