Obitalk cannot configure device
ktalk:
Obitalk suggestion was use win10 and chrome with lastest updates. I had that so just out of curiosity i tried using edge. Worked first time. I read some of the posts above. It does seem to have something to do with browser, pop-ups, gmail login
SteveInWA:
Quote from: ktalk on December 23, 2017, 09:18:48 am
Obitalk suggestion was use win10 and chrome with lastest updates. I had that so just out of curiosity i tried using edge. Worked first time. I read some of the posts above. It does seem to have something to do with browser, pop-ups, gmail login
That sounds like a coincidence to me, based on the symptom and the post from gjemb. But, as Archie Bunker used to say, "Don't slug a gift horse in the mouth!"
gjemb:
I used the same configuration: win10 and chrome with latest updates, both when it did not work, and when it did work. Just different times of the day. I would doubt it has anything to do with the operating system, or updates.
If I was to speculate......... likely google voice availability itself? Or something in the back end with obi?
Glad to be back up and running.
SteveInWA:
Quote from: gjemb on December 23, 2017, 11:34:54 am
I used the same configuration: win10 and chrome with latest updates, both when it did not work, and when it did work. Just different times of the day. I would doubt it has anything to do with the operating system, or updates.
If I was to speculate......... likely google voice availability itself? Or something in the back end with obi?
Glad to be back up and running.
That is my guess, too. Thanks.
Vova:
Had same issue when shifting from obi110 to obi200, I was using chrome with Win 7. Tried from IE - worked, it just asked for google password a couple of times. Should be an issue with chrome, at least in my case.
Navigation
[0] Message Index
[#] Next page
[*] Previous page