On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT
Started by B0b., August 14, 2018, 09:48:59 PM
Quote from: B0b. on August 15, 2018, 08:30:07 PMQuote from: A_Friend on August 15, 2018, 07:32:21 AMAll I can offer you is s xender discord omegleome speculation and maybe a couple of things to try -- a shot in the dark, so to speak.Thanks for the help!I'll look at the ICE/Keep-alive/times on the OBi. Do you know where these are or what to try when setting them?The only thing I quickly found when looking at the Internet settings on the configuration page is PPPoEKeepAlive set to 60.I'm getting a Wi-Fi adapter in the mail tomorrow to try to connect the OBi directly to the hotspot and bypass the router.I already have the same GV account set up on my laptop and spare cell phone that is connected to Wi-Fi and these always ring and can make outgoing calls.I'll look into getting a SIP account from another provider, but I'm hoping to stick with GV. A cellphone is available to use 911, but it has a limited amount of minutes for other calls, and I would prefer to use the landline handset to make calls at the house.
Quote from: A_Friend on August 15, 2018, 07:32:21 AMAll I can offer you is s xender discord omegleome speculation and maybe a couple of things to try -- a shot in the dark, so to speak.
Quote from: JM51 on October 21, 2019, 04:07:53 PMIs there any update to this?Having issues with Google Voice and Obi suddenly. The phone number works fine in Google itself.I followed the above instructions and changed the Google credentials, making sure everything was updated. It worked for a minute. And then right after, any outgoing call reverts to "The number you dialed..." FMWhatsApp ApkCalling the echo line **9222222222# works, and all the 3 lights on the device are green and static (though the middle one, internet, occasionally blinks really quickly, not flashing, but a quick blink, as if indicating in use).What else can I check? I updated the firmware as well.
Quote from: Summest on March 19, 2020, 12:45:55 AMThis post was largely a waste of time, but I think whoever said to reset the password could have been onto something.Instead of doing that I added GV to SP3 and updated the configuration to match. Voila.I can call in and out once again and I am hardwired and have been the whole time. Let us see how long this lasts.
Quote from: buddywiser on May 26, 2020, 09:37:44 AMI think I am getting this message because of something I'm doing. I am a Obi newbie only using it for a few days. Everything worked fine with my GV number until this morning when I tried my first conference call using this setup. Out of habit, first thing I do it dial *70. This disabled call waiting on my previous provider. So now I do this and get the error sound with a different message. Hang up and try to call the number without *70 and get the message in the subject. Try to make a few more calls with same error message. Then after reconnecting to GV in the Obi settings, all is well. I can replicate this scenario and as soon as I hit *70, I can no longer make calls.
Quote from: dsm1212 on January 12, 2021, 08:33:11 AM.. my internet connection is 100Gbps.
Quote from: drgeoff on January 12, 2021, 10:47:20 AMQuote from: dsm1212 on January 12, 2021, 08:33:11 AM.. my internet connection is 100Gbps.Really?
Quote from: SamirLatif on June 12, 2021, 04:07:57 PMLooked around other website and this instructions worked for me. Copy and pasting it here for the rest. Hope this will resolve the same issue that I have:Here's what I managed to do to get both my Obihai devices (200 & 202) "connected" and working again. (Yes, I suffered from the "registration not required", as well as the "token", issues).In the Obitalk home page, select the desired device ... and then click "OBi Expert Configuration". Confirm that you actually want to go to that screen.Then click "Enter OBi Expert"On the left panel, under "Production Information" select:SYSTEM MANAGEMENT » WAN Settings → or ←ROUTER CONFIGURATION » WAN SETTINGS (menu changes between 200 & 202)You then need to unclick the check marks under "OBiTALK Settings" for:"DefaultGateway""DNSServer1""DNSServer2"The check mark of the above 3 items will switch to "Device Default"; unclick those as well.Default gateway is the IP of your home/business routerDNSServer1 I set to: "220.127.116.11" and DNSServer2 I set to "18.104.22.168"Save the settings and then reboot your device.Changing the Default Gateways ... and indicating the proper DNS servers to utilize brought me back to up-and-running; hope it does the same for you!
Quoteou then need to unclick the check marks under "OBiTALK Settings" for:"DefaultGateway""DNSServer1""DNSServer2"The check mark of the above 3 items will switch to "Device Default"; unclick those as well.Default gateway is the IP of your home/business routerDNSServer1 I set to: "22.214.171.124" and DNSServer2 I set to "126.96.36.199"
Quote from: AlexForaza on June 13, 2021, 02:25:46 AMWhen I am getting to SYSTEM MANAGEMENT » WAN Settings, there are no "DefaultGateway""DNSServer1""DNSServer2"What am I doing wrong?