Call Failed - 901
TheWalkman:
Glad to see this isn't just me. I've reconfigured my phones (Obi200 and Obi1032) half a dozen times to no avail.
When these Obi phones work, they work but they can are certainly too complicated. (sigh)
Rick147:
I am now getting the Call Failed - 901 on all 3 GV numbers
What was the fix for this please? I have rebooted everything, Tried to reconfigure the GV numbers to no avail?
Rick
0biWanKenobi:
Quote from: Rick147 on June 12, 2021, 05:40:52 pm
I am now getting the Call Failed - 901 on all 3 GV numbers
What was the fix for this please? I have rebooted everything, Tried to reconfigure the GV numbers to no avail?
Rick
I saw the fix in another thread. Although you don't actually need to change the default gateway. Just update the DNSServer1 and DNSServer2.
Quote from: SamirLatif on June 12, 2021, 04:07:57 pm
Looked 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 router
DNSServer1 I set to: "1.1.1.1" and DNSServer2 I set to "8.8.8.8"
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!
drgeoff:
Read http://www.obitalk.com/forum/index.php?topic=18329.msg108740#msg108740 and take note of the words:
"no action on your part is necessary nor will fix it at this time."
SteveInWA:
Quote from: 0biWanKenobi on June 12, 2021, 05:42:58 pm
Quote from: Rick147 on June 12, 2021, 05:40:52 pm
I am now getting the Call Failed - 901 on all 3 GV numbers
What was the fix for this please? I have rebooted everything, Tried to reconfigure the GV numbers to no avail?
Rick
I saw the fix in another thread. Although you don't actually need to change the default gateway. Just update the DNSServer1 and DNSServer2.
Quote from: SamirLatif on June 12, 2021, 04:07:57 pm
Looked 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 router
DNSServer1 I set to: "1.1.1.1" and DNSServer2 I set to "8.8.8.8"
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!
That fix is BS. If it makes you feel better, like playing with a fidget spinner, fine, but it is unrelated to the actual problem. That problem has now been temporarily resolved, until Poly provides a longer-term fix.
Navigation
[0] Message Index
[*] Previous page