Obi100 -> Obi200 Issues
tazmo8448:
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.... ???
GPz1100:
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.
GPz1100:
Look at post #5, https://www.obitalk.com/forum/index.php?topic=6045.0 .
tazmo8448:
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.
tazmo8448:
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
Navigation
[0] Message Index
[#] Next page
[*] Previous page