Unable to add OBi202 to my account
QuintCom:
I'm new to OBi devices. I've been trying to add my newly purchased (and brand-new) OBi202 device to my OBi account so I can configure it for Google Voice service. Unfortunately, their system seemingly refuses to allow me to do so.
My situation is as follows (i.e., device/connection status and what I've tried)...
The power LED is solid green. DHCP is enabled. The ***1 command reports the device's assigned LAN IP as 192.168.1.5 and I can ping that IP from the other computers on my LAN. I've tried port forwarding for UDP port 10000 to 192.168.1.5:10000 and also placing IP 192.168.1.5 in my broadband router's DMZ area. But neither of those efforts made a bit of difference. I consistently always get a timeout with a "Failed to connect to your device" message after a displayed 120 second countdown. I have probably tried 30 or more times to add this OBi202 device to my account without success. I as well tried issuing the ***8 1 reset command. The OBi device rebooted... but it made no difference, either, as far as allowing me to add the device to my account.
After doing some research, I've discovered that this problem has plagued many users since at least 2017. Some of them who requested support from OBi said that OBi manually added their devices to their accounts which worked to activate their devices. I did fill out and submit the OBi/Polycom support form and I sent a separate email to support@obihai.com ... but since it's the weekend I'll have to wait a day of two to see if they reply. It will be nice if they are able to manually add my device so it can become enabled. In my communications with them I included the ID number of my OBi202.
Other than the steps I've already taken, does any one have any suggestions (or thoughts) concerning my situation?
Thank you in advance.
drgeoff:
Does dialling **9 222 222 222 successfully reach the echo test number?
QuintCom:
Quote from: drgeoff on March 24, 2019, 03:40:03 pm
Does dialling **9 222 222 222 successfully reach the echo test number?
I'm unsure whether the voice message I receive when I dial **9 222 222 222 is locally generated by the OBi202 device or whether it originates from the OBiHai network server. That voice message is: "There is no service available to complete your call."
BTW, thanks for your reply. Any assistance will certainly be appreciated.
drgeoff:
Quote from: QuintCom on March 24, 2019, 07:41:57 pm
Quote from: drgeoff on March 24, 2019, 03:40:03 pm
Does dialling **9 222 222 222 successfully reach the echo test number?
I'm unsure whether the voice message I receive when I dial **9 222 222 222 is locally generated by the OBi202 device or whether it originates from the OBiHai network server. That voice message is: "There is no service available to complete your call."
BTW, thanks for your reply. Any assistance will certainly be appreciated.
That message is locally generated. The call should be answered with a man's voice saying "Welcome to Obitalk ...". Until that works you are wasteing your time trying to add the device to the portal. Even if Obihai support manually add the device you will not be able to make calls.
It is very rarely necessary for a user with an ordinary home router and residential internet service to implement port forwarding, DMZ etc. Is there anything atypical about your internet service and LAN?
I would first suggest that you reset your router, wait a few minutes then reset the OBi and if possible try a different phone. Whatever phone, plug it directly into the OBi, not via any house wiring.
QuintCom:
Quote from: drgeoff on March 25, 2019, 12:57:07 am
That message is locally generated. The call should be answered with a man's voice saying "Welcome to Obitalk ...". Until that works you are wasteing your time trying to add the device to the portal. Even if Obihai support manually add the device you will not be able to make calls.
Understood. But... in that case, why doesn't my local OBi device produce a message indicating that a server handshake failed to occur? I believe OBi should have been able to achieve that functionality through an implementation of SYN/ACK packet flagging interpretation. But the device reports nothing about server connection/acknowledgement being awry. The response message I am consistently receiving is simply, "The number you have dialed, **5 ####, has been sent to the server." On its face, that message suggests that the server received the code I've sent to it without issue. If what you're saying is correct, clearly no ACK packets are able to be returned to my OBi device, OR it simply doesn't report the handshake failure. I don't quite understand why they might omit such an important indicator function.
The following thread from late 2018 seems consistent with my issue and, as you'll see, appears to have affected a significant number of users... http://www.obitalk.com/forum/index.php?topic=14947.0
You will notice in the thread that some of the users claim OBi/Polycom manually adding their device resolved the issue for them.
Quote from: drgeoff on March 25, 2019, 12:57:07 am
It is very rarely necessary for a user with an ordinary home router and residential internet service to implement port forwarding, DMZ etc. Is there anything atypical about your internet service and LAN?
The router is a Comtrend VR-3031u. I've had no issues with it in any regard as far as Internet connectivity or service access. In fact, I continue to use it for establishing and maintaining SSH terminal sessions with a number of remote dedicated servers that I manage. Moreover, other service devices requiring interaction with remote networks (e.g., Roku streaming sticks, VPN tunnels, etc.) continue connecting with their servers and continue rendering their respective services without issue through this router. And to be clear, I have not configured it for universal VPN connectivity - any VPN adapters/tunnels that I implement are configured on individual computing devices connected to the Internet through the router. My point being that the router facilitates those tunnel connections just fine. I've been using this same router since 2017 and have encountered no issues with it other than, perhaps, this OBi server connection problem.
Quote from: drgeoff on March 25, 2019, 12:57:07 am
I would first suggest that you reset your router, wait a few minutes then reset the OBi and if possible try a different phone. Whatever phone, plug it directly into the OBi, not via any house wiring.
Done. But it made no difference. One difference about my router that I failed to mention above is that it has a static IP address. And the PTR record (rDNS) for the static IP is one of my own domains. Both the PTR host name and the numerical IP resolve correctly to one another and the host name has never created an issue with any other connections or with DNS interaction.
By the way, I've enabled LAN access to my OBi202 device and I'm now receiving a login dialog when entering 192.168.5 into my browser address bar. Since I know of know login credentials that will work to access the device, I can't get beyond that login dialog? Is there a way around this without first adding the device to the server?
Navigation
[0] Message Index
[#] Next page