When I changed over from the 100 to the 200 (and we all know why) and using GV I noticed now that all my incoming calls are now showing UNKNOWN CALLER no matter if they are listed in my directory or not they're all UNKNOWN. BTW the numbers are showing but not WHO it is....grrr ..Importing in ObiExtras does nothing either.
What I did is hook up the new modem go to the Obi/GV setup basically all it was was swapping modems.
What causes all incoming calls to now be UNKNOWN CALLER?
So far what I've done is go into my IP address (dial***1) and 'submit' the caller configuration that lists Physical Interfaces (Phone Port 1) we'll see if that is what was causing all calls to be UNKNOWN.
Just tried to call myself from the cell phone that I use to set up GV & Obi200 and it shows ME as an UNKNOWN CALLER....for cryin' out loud
One more thing concerning this....Google Voice DOES show the correct caller name & number in it's history...it just showed me calling myself (plus other incoming calls today are correctly labeled).
Going to the IP address associated with the phone an Obi checking all the boxes that deal with incoming ID an all that and SUBMITTING them for configuration did nothing...just sayin`
Tried importing my GV contacts to Obi that didn't work either.....grrr.
Does it show the number, but name is unknown or just unknown and nothing else?
It DOES show the number and all names no matter if they're in the phones directory or known to GV ALL show UNKNOWN CALLER
The thing that gets me is none of this happened with the Obi100 it was flawless....but swapping out with the Obi200
I'm seeing issues, plus, seeing issues all over the net with this model....Obihan remains quiet on responses. Looks like the money grab is biting them in the rear. Then again they've sold the product an maybe could care less now. I'm thinking it's a firmware setting as my phone has stored numbers...GV shows all the calls as to who it is...but something in the firmware is interfering.
I don't understand what you typed above, but be advised, gv does not provide caller id names, just the number. It's up to your device to match the number to a stored name. If you want true cnam caller id either use simonics gateway, or forward your calls to a free call centric DID. We use call centric because it offers further inbound call enhancement such as spam blocking (better than gv), ivr, and call treatments.
https://simonics.com/gw/
http://www.callcentric.com
Edit: Nothing wrong the obi200. Been using one for over a year with no issues. Obi's hardware is great. The issue is software and documentation. It's a rather complex device with lots of capability. Making it easy to use for non tech people is challenging.
All I know at this point is Obi200 does not show names like Obi100 did...we HAD to buy the thing to continue service with GV as you know.
My phone connected to Obi has a Directory with all the saved names an numbers an somehow they're not being triggered.
GV shows all the names (and numbers of course) that I have associated and they show when I miss calls an also show in history.....just sayin'
I'm glad to hear you're happy and don't doubt that but telling me all is well doesn't cut any ice at this point. I do appreciate that you've taken an interest and are posting but you'd think the default settings would at least work as well as the previous Obi100 version did...it was just plug-n-play as far as that goes.
This is really a head scratcher to me.... ???
I never owned an obi1xx so no clue how it handled CID. Call log in the obi200 indicates a leading 1 then 10 digits for the caller id. If your phone's directory only has the 10 digits without the leading 1 this would explain the mismatch. I don't believe there is a way to strip off the leading 1. Maybe your phone can be configured to ignore it.
You will need to put in some effort to get this sorted unless you go with a system such as ooma or magic jack where both the hardware and software is a matched set designed to work as a system.
Look at post #5, https://www.obitalk.com/forum/index.php?topic=6045.0 .
I think you're on to something there....the 1-xxx-xxx-xxxx thing
Guess the thing is set up for international calls these days which knocks the bottom out of local calls...my phone won't even store the 1 before the area code & number...that truly is something that needs to be addressed as the majority of people only use phones for local or in-state calls...with the occasional 1-800 numbers.
the link:
Look at post #5, https://www.obitalk.com/forum/index.php?topic=6045.0 .
deals with Obi100 settings..but someone found a code that scrubs the 1 off (or eliminates it)
THAT I believe is the answer....scrubbing that darned 1 off so it only lists area code & number.
Looking at the code used in Obi200
{pli:(xx.)},{sp1:(<**1>xx.)},{sp2:(<**2>xx.)},{sp3:(<**3>xx.)},{sp4:(<**4>xx.)},{bt:(<**8>xx.)},{bt2:(<**82>xx.)},{pp:(<**9>xx.)}
this looks to be associated with the star code dialing.
The Obi100 CID Format looks like this an is explained from the link above........
Voice Services > SP1 Service > X_InboundCallRoute:
{(<1:>@@.):ph},{ph}
An incoming call with CallerID of 12345678912 will have the leading "1" removed before the CallerID is sent to the phone by the rule {(<1:>@@.):ph}.
An incoming call with CallerID of 2345678912 or any other CallerID not starting with "1" will be sent to the phone unchanged by the rule {ph}.
I believe that this is the key to the problem finding a way to remove the 1
I've tried all the resets an reboots (wishing against hope) BUT
incoming calls on Obi200 are still showing UNKNOWN even though I've changed them to show a 1 in front of the Area Code....
Incoming calls on Obi200 are going to have to have the 1 removed I'm afraid...to work correctly
looking at the caller ID Method listed it shows the default as
FSK(Bell202) with a drop down list for FSK(V.23) and several other countries.
don't see a code there to be able to insert scrubbing the 1 off.
the CidNoNameFormat lists three types
Show Code O
Show BLANK
Show Caller Number
none of which show a way to be 'tweaked'
The only other reference to CID is a check box (under Calling Features)to enable which is enabled by default (no codes to tweak)
I think this is something the Obi Firmware will have to address
I'm really starting to think that it all boils down to Obi now wanting people to have the Obi Extras deal so they can charge monthly fees to do the things that use to be included. #1 was having CID now it seems it's listed as an EXTRA
way to go Obi....squeeze that dollar.
What was your outcome after you added to the respective SPx slot?
Voice Services > SP1 Service > X_InboundCallRoute:
{(<1:>@@.):ph},{ph}
Well I spent several hours looking in Voice Services seeing nothing that even resembles a code that can be 'tweaked'
there really isn't anything relating to that except check boxes and those don't have drop downs to look at or change.
...then looking at the advertising for Obi200 see that CID is offered as a paid service under 'Obi Extras'
of course none of this was said when they announced the end of Obi100 and that the new Obi200 would be a replacement because of the new Google Chrome update (that changed the code used) when and if the ticket I sent on the subject is answered I will report those findings....have a friend that just got the Obi200 also and his calls all show UNKOWN CALLER so I'm sure it's a PAID service now. Will check with dslreports an see what they have to say.
You're looking for X_InboundCallRoute in the path specified above. That's the parameter name. You modify its parameter to "{(<1:>@@.):ph},{ph}" (without the quotes).
Are you saying your obi1xx does not have this parameter?
You still haven't confirmed what called id number your phone actually shows, and if you have your stored numbers with or without the 1. Can't help you further until these are clarified.
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.
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
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.
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'
Put down the crack pipe.
Google Voice has never supported CNAM. If you disagree, please show me a web page supporting your contention. I double-dog dare ya.
Try changing the following setting from the default and see if it makes any difference:
Physical Interfaces-->Phone 1-->Port Settings-->CidNoNameFormat
That's real cute SteveInWA ...
and that may earn you some brownie points from whoever it is you're trying to impress.
Sorry to see something that is a genuine issue being tossed off by a shill.
@ Taoman
as a matter of fact I did try that setting... tried all three listed in the drop down:
Show Code O (default)
Show Blank
Show Caller Number
I would change each setting>submit then call the Obi/GV phone using my cell, during the course of the day I would get calls from friends and businesses randomly and no matter the settings all would report unknown caller
My main thrust about this whole thing is changing from the 100 series to the 200 series I've somehow lost caller names being generated or triggered.
As stated I had the 100 series up an running for at least 4 an a half yrs and never had an issue with it showing who was calling but changing over to the 200 it has lost that function.
If you're getting a number on the phone's display then the obi box is doing what it's supposed to - passing on the CID information to the connected device. The only [potentially useful] thing that obiextras does is match up the number to your contacts. If there's a match it displays the contact name for CNAM.
If your phone is not showing the correct information then something is wrong with the phone device.
What happens if you try adding one of these unknown numbers as a new contact with some bogus name... say test_contact. Call your gv number again, what does the phone show?
I suppose you can also factory reset the obi box and try setting it up from scratch.
Personally, with respect to CNAM CID, we proxy it through call centric's free DID which provide CNAM lookup so we get caller id information for any caller.
Edit: Maybe the obi100 did provide the cnam obiextras feature for free. The 200 does not.
thanks GPz100...I kinda came to that conclusion too... that the 200 just doesn't offer the same functions... although on it's web page it does specifically say +CID Name & Number (wanted to make sure before I said anything)
here is that link https://www.obitalk.com/info/products/obi200 it shows about half way down the page...
Key Features of the OBi200 VoIP Telephone Adapter
Robust Telephony Features:
Caller ID – Name & Number
Call Waiting
Message Waiting Indication - Visual and Tone Based
Speed Dialing of 99 OBi Endpoints or Numbers
Three Way Conference Calling with Local Mixing
Hook Flash Event Signaling
Call Forward - Unconditional
Call Forward on Busy
Call Forward on No Answer
Call Transfer
Anonymous Call
Block Anonymous Call
Do Not Disturb
Call Return
Repeat Dialing
Caller ID Pass-Thru
I see where you say you use Centric's free DID.. could you be kind enough to post a link so I can look at it? it looks like in order to see who's calling I will have to use another parties service.
Don't think CallCentric would work...looking at their site it seems to be used for CallCentric to CallCentric clients only.
BTW I see where Polycom as of Jan 8th (i believe) has purchased Obihan so who knows what lies ahead.
I've read a lot of posts here starting in Nov thru Dec dealing with former Obi100 users feeling like they're getting hosed because of dropped support for a product that they bought in good faith; and the waters being further roiled by now requiring a monthly/yearly paid subscription to get those same services. If it's not a money grab then I don't know what is I guess. Plus the same forum trolls putting everyone down for even bringing it up or discussing it...like it hurts their feelings..(you'd think they have a vested interest)..not to mention touting buying the 200 that clearly has false advertising...all explained away by the pearls of wisdom that 'obi didn't intend for that to happen' or 'it's not obi's fault'...'it's your phone' my advice is If You Don't Know The Answer Then Stay Out Of It.
I feel that I've been led on.
If you have any other ideas I'm all ears.
Callcentric works just fine. We're using it for inbound calls for the reason I mentioned above and on the previous page.
The only other idea I have for you is to flash the modded firmware to your 1xx unit. It's on the dslreports site in the voip subforum.
GPz1100 again thanks for taking your time
Quote from: tazmo8448 on January 13, 2018, 10:20:33 PM
I kinda came to that conclusion too... that the 200 just doesn't offer the same functions... although on it's web page it does specifically say +CID Name & Number (wanted to make sure before I said anything)
here is that link https://www.obitalk.com/info/products/obi200 it shows about half way down the page...
Key Features of the OBi200 VoIP Telephone Adapter
Robust Telephony Features:
Caller ID – Name & Number
The Obi200 DOES forward Caller ID Number and Name to the phone IF AND ONLY IF they are provided by the VoIP service provider. As explained by SteveInWA, Google Voice does not provide the Name, only the Number.
One more time folks....I want to know if Obi200 supports CNAM like Obi100
ITS NOT ABOUT NUMBERS .... it's about NAMES...
OBVIOUSLY the 200 does not do this...seems the reading comprehension is off here...the guys that 'patrol' this site seem to read into questions what they want then answer.
Obi100 does...it shows each NAME as they come in Obi200 shows UNKNOWN CALLER each time....period.
Thanks to all for the 'suggestions' an a shout out to GPz1100 for his input as it dwelt on the subject.
Quote from: tazmo8448 on January 14, 2018, 02:59:26 PM
One more time folks....I want to know if Obi200 supports CNAM like Obi100
One more time... yes, the OBi 200 supports CNAM exactly, precisely, like the OBi 100. The comment by GPz to the contrary is completely wrong.
As Taoman, DrGeoff and I have repeatedly pointed out, this is functioning properly, and exactly as expected.
Quote from: tazmo8448 on January 13, 2018, 04:08:34 PM
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
Looks like you have not understood the sticky post. http://www.obitalk.com/forum/index.php?topic=61.0
Quote from: SteveInWA on January 14, 2018, 03:36:34 PM
One more time... yes, the OBi 200 supports CNAM exactly, precisely, like the OBi 100. The comment by GPz to the contrary is completely wrong.
Which comment is this exactly??
Quote from: GPz1100 on January 14, 2018, 04:34:54 PM
Quote from: SteveInWA on January 14, 2018, 03:36:34 PM
One more time... yes, the OBi 200 supports CNAM exactly, precisely, like the OBi 100. The comment by GPz to the contrary is completely wrong.
Which comment is this exactly??
This:
Quote
Edit: Maybe the obi100 did provide the cnam obiextras feature for free. The 200 does not.
Quote from: SteveInWA on January 14, 2018, 05:00:16 PM
Quote from: GPz1100 on January 14, 2018, 04:34:54 PM
Quote from: SteveInWA on January 14, 2018, 03:36:34 PM
One more time... yes, the OBi 200 supports CNAM exactly, precisely, like the OBi 100. The comment by GPz to the contrary is completely wrong.
Which comment is this exactly??
This:
Quote
Edit: Maybe the obi100 did provide the cnam obiextras feature for free. The 200 does not.
If my comment is completely wrong, how else do you explain cnam cid on the obi1xx the OP was receiving at no charge?
Quote from: GPz1100 on January 14, 2018, 05:04:47 PM
Quote from: SteveInWA on January 14, 2018, 05:00:16 PM
Quote from: GPz1100 on January 14, 2018, 04:34:54 PM
Quote from: SteveInWA on January 14, 2018, 03:36:34 PM
One more time... yes, the OBi 200 supports CNAM exactly, precisely, like the OBi 100. The comment by GPz to the contrary is completely wrong.
Which comment is this exactly??
This:
Quote
Edit: Maybe the obi100 did provide the cnam obiextras feature for free. The 200 does not.
If my comment is completely wrong, how else do you explain cnam cid on the obi1xx the OP was receiving at no charge?
Drugs. Lots and lots of drugs.
'' Drugs. Lots and lots of drugs.''
Totally irresponsible answer.
Obi200.... call comes in no matter whom it is...it reads
UNKNOWN CALLER
1-222-333-4444
Obi100... call comes in...it reads (the same way the phone number & name is stored on the phone)
Jr Jay
333-4444
went to Simon Services paid the one time fee hooked the Obi100 back up....bingo all back to normal.
Anybody wanna buy a cheap Obi200?
One last thing on this subject....I got a response to an email to Obi and this is straight from the horses mouth.....
Hi,
You are using Google Voice service (account xxxxxx@gmail.com) and so no Caller ID Name (CNAM). Only Caller ID Number.
Best Regards,
Obihai Technology