Obi100 -> Obi200 Issues
tazmo8448:
Again thanks GPz1100 for taking your time with this.
I am not using the Obi100 btw am using the Obi200
I went into the Obi200 Voice Services config files and found (two instances) of the X_InboundCallRoute;
added {(<1:>@@.):ph},{ph} both to the SP1 (GV?) AND the ObiTalk parameter to the FRONT of the list that is given.
SP1 Service was showing ph only (default with no other option)
ObiTalk Service was showing {(290062669)>(xx.):SP1},{(290062669):aa},{ph} (default)
noticed after submitting those changes, that it required a Reboot, but doing so reset both to default (even without the default box checked) so I just submitted them WITHOUT a Reboot
I found (on my phone) that whether I have a 1 in front of my area code or not that I still get UNKNOWN CALLER...tried it both ways.
Again I think the new (to me) Obi200 Does Not Support CID natively as the Obi100 did. Have some friends that have Obi200 and ALL their Incoming Calls show UNKNOWN CALLER.... and ALL have different make & model cordless phones, so to my thinking it isn't the phone it's Obi200 not supported non-paid CID services.
tazmo8448:
Incoming calls show
UNKNOWN CALLER
1-area code-xxx-xxxx
no matter if the phone itself has an 1 in front of all the numbers stored in the directory
or using those settings we discussed added to the X_InBoundCallRoute
SteveInWA:
There is nothing inherent in the OBi 200 product line that would/could cause this.
There is no "money grab" behind this.
There is no special subscription required to display the caller ID number on the phone plugged into the OBi
Obihai has nothing to do with this issue.
Some important things to understand about Google Voice:
When someone calls your inbound Google Voice phone number, Google Voice then forwards the call somewhere else. That "somewhere else" is typically a 10-digit, US telephone number, either a land line or mobile phone number. Google Voice can also forward inbound calls to the old "Google Chat". Although Google's own Chat service has been discontinued, it still maintains the servers for OBi customer use. OBi devices are Chat clients.
There are two different pieces to caller ID in the USA: the caller ID number (CID) and the caller ID name (CNAM). The CID is sent along with the call routing data, so that number can be easily displayed by the receiving party's telco (or, in this case, by Google Chat). The CNAM is not sent by the calling party's telco. Instead, the called party's telco has to look up the CID in a database of matching numbers and names, and then send that name to its subscriber's phone.
Google Voice neither feeds its own users' names into the CNAM databases (known as the LIDB), nor does it do CNAM lookups (reason: there is a cost to using the CNAM LIDB which wouldn't be viable for Google, given the free service).
When you receive an inbound phone call via Google Voice, GV will only send the CID to the phone. What your phone's caller ID display shows is dependent on your phone. Some will just display the CID, with a blank CNAM field. Some will display some other message.
If you use Google Voice's call screening feature, the automated voice will say "call from unknown caller" when that caller's number is not in your Google account's Contacts, or it will speak that contact's name if you have it in your Contacts list (call from "Bob Smith").
There is no difference whatsoever in this behavior between an OBi 100 product and an OBi 200 product.
If you doubt this, then look at your Google Voice call history on a laptop/desktop computer. You should see the phone number listed for all legitimate (not anonymous/fake/spoofed) inbound calls. If you have that number in your contacts, it will substitute the contact's name. Again, the name is not sent to the OBi.
tazmo8448:
First of all this post was not created to question the Caller ID NUMBER it was created to ask why ALL calls now show UNKNOWN CALLER
Let's put it this way.... all calls that came in (using GV) with the older, now defunct, Obi100; showed all incoming calls with a name ( CNAM ) or at least an occasional Out Of Area (seen seldom) only once in a blue moon did I ever see UNKNOWN CALLER.
Setting up and installing the replacement Obi200 (purchased because Obi dropped firmware updates) ALL my
incoming calls now show UNKNOWN CALLER along with phone numbers listed as 1-area code- number. i don't have a problem with it showing numbers this way, but I would like for the phone to somehow recognize the name of the number used, like it use to do with the older 100 series.
GV DOES show names in it's history; it shows names that I use regularly...the phone I use with GV always showed the names stored in the saved directory as the person or business calling...not now.
I have several friends that have the 200 and all of their incoming calls show Unknown Caller....each one are using different phone makes and models from brand new out of the box to several years old. It's not the phone.
My big question is (and will remain til answered) Why does this happen when it did not with the older version 100 series?
Why didn't Obihan just update the firmware used by Google so people could continue to use the 100?
After having to purchase another modem because of this why doesn't it work as well?
Why am I seeing CID touted as an 'Obi Extra' that requires a paid service for Obi200 users?
We all know the answer...to generate more cash flow... there's no money in just creating an releasing new firmware, to stay up to date. So make Obi100 users buy another modem, then offer paid services to do the same thing it use to do for free. It's a business model used globally....when you're not selling any more make it to where they have to buy the new an improved model...then charge for the service that use to come with it...and shame on Google for going along with it.
Back to the question....... Obi100->Obi200 why the differences....and please don't try an sell the idea that it's 'better'
SteveInWA:
Put down the crack pipe.
Navigation
[0] Message Index
[#] Next page
[*] Previous page