Firmware update for 20x series
SteveInWA:
Two possibilities:
You are looking at the wrong Google/Gmail/GV account in your screenshot of the new GV UI, or your browser has some stale cache, history or cookie data.
Try signing off of ALL Googly things in your browser, including Gmail. Clear the browser's cache, cookies and history. Close and reopen the browser.
Now, open an "Incognito" browsing session in Google Chrome Browser by pressing Ctrl-Shft-N, or open a "Private" browsing window in Firefox by pressing Ctrl-Shift-P.
In that incognito or private window, try signing into the same Google account that holds the GV inbound phone number you are trying to use, and go here: https://voice.google.com/settings
Look at the Google Voice number displayed at the top of the page, and make sure it is the same GV number you are trying to use with your OBi. If not, sign out and sign in with your other account(s) until you find it.
Once on the correct page, you should see the new settings.
SteveInWA:
Ok, thanks. The reason I wanted you to go through that is: it is actually possible to be logged into several different Google accounts at the same time, on the same browser. Google keeps track of it with cookies. The problem is, some Googly things are compatible with this, and some are not. The chronic offender is the page used to unlock GV numbers for porting out. If the user is logged into more than one Google account, it may only "see" one of the two accounts and thus, there will be no number to unlock.
Since you are/were working on your own account and on somebody else's, that was a potential issue.
The URL you posted, https://www.google.com/voice/b/0#phones proves that this browser is signed into more than one account. The "/b/0" portion shows that it is the first of the multiple accounts signed in. If it was the second account, it would say "/b/1", and so on.
I don't know why that account isn't working. In theory, when a new device is added, it downloads the new firmware, which is what you are seeing. It should also convert that Google Voice number over to the new platform upon adding it to the OBiTALK portal. Perhaps this one just got stuck in some sort of "early adopter" limbo.
dircom:
Here are the urls the second time around
https://www.google.com/voice/b/0?gsessionid=9vLCxcPMQtfNU2-4ERyjjOEk0wnj7mXJ&pli=1#phones
and
https://voice.google.com/settings
The main difference I see is, forward to chat on the older devices
vs fwd to OBITALK Device using https://www.google.com/voice on the newly connected OBi
I guess I could try a separate account and dashboard and see what that does
also I don't know why my choice is fwd to phone 3, there never was a phone one or two
SteveInWA:
If the old, "Legacy" UI shows Google Chat, then the account has not yet been converted to use VoIP. If an account has been converted, then the Legacy settings page will no longer display Chat, but instead, it will have an entry for each VoIP connection (one for each OBiTALK device, one for the web client, and one for each Android client).
SteveInWA:
Pardon my laziness to re-read the thread, but I think you mentioned that calls using other ITSPs work?
In other words, if both your device and his device take turns calling each other via OBiTALK (**9 nnn nnn nnn), do you each hear the other party? What if you provision his device with a SIP ITSP; do you get two-way audio on calls?
Also, is this user in the USA?
Navigation
[0] Message Index
[#] Next page
[*] Previous page