Can't add obi2182 as new device to obi dashboard
WildBillPDX:
Quote from: ILLCOMM on November 24, 2018, 06:01:45 am
Quote from: SteveInWA on November 24, 2018, 02:18:35 am
This is absolute rubbish. Polycom already acknowledged this failure to me, and they are working on it. They know it's broken. Go away; you're not contributing anything useful.
As a "Hero Member & Beta Tester" you obviously have a bias. Step back for a second.
The unbiased reality is it is unacceptable for any service to have a multi-day registration/provisioning outage and produce no messaging, provide no communication with their customers, publish no ETA, furnish no dashboard reporting service health, or anything else that any other modern web service provider would do.
I am at my elderly parent's home for Thanksgiving trying to set this up for them as they moved and wanted to bring a 30-year old number with them to the new house (which I was able to port to GV). So, now, it appears I have to leave them behind without it working because of this BS.
It's OK to call it as it is, and in this case it's amateur hour at Poloycom Obihai or whatever company is behind the product.
I find the response from Polycom disappointing. I submitted a ticket via the website and an email to obi.support@polycom.com but haven’t received any response. An acknowledgment of some kind would be good.
isaac_unixapp:
Quote from: SteveInWA on November 23, 2018, 12:49:58 pm
Quote from: Batnumb on November 23, 2018, 11:31:47 am
This is unacceptable. I wasted a few hours yesterday troubleshooting everything, from the dash to all the cables, before I stumbled on this posting. Still can't believe that no one at Obitalk has fixed this - like, no one can't connect to their server!
It's the Thanksgiving weekend. Most people are off/out-of-the-office. There is no 7x24 support.
I've already reported this to Polycom, and they are investigating it today.
Thanks for reporting this @steveinWA (talk about bias for action :-) - can you share a ticket number with Polycom? I am experiencing the SAME issue with a new OBi202 I've been trying to add over the Thanksgiving weekend. I do have another OBi202 that has been working flawlessly; logic would dictate that it would be useful to put a sniffer on their end and see if they are receiving the registration attempts from the likes of us.
isaac_unixapp:
Quote from: RichR on November 24, 2018, 06:47:16 am
Just tried this morning and nothing's new. I gotta say, that was not a good introduction to the OBi202. I hope that I made the right choice.
stick it out - others are reporting the same issue. Its a great product, I've been using them for years.
isaac_unixapp:
btw - here's what I have tried, to no avail:
1) https://www.obitalk.com/info/faq/Troubleshooting-sec/ports-to-keep-open-on-my-router
2) the self-troubleshooting guide
https://www.obitalk.com/info/support/troubleshooting
There's a process that allows the device to "phone to the mothership" and check for new firmware.
Upon completion of it, though, here's what I see on my device:
HardwareVersion 1.4 help
SoftwareVersion 3.2.1 (Build: 5757EX)
"Copyright (c) 2013" - not sure whether they're updating the year bit ?
WinRG:
Chiming in, same issue. Spent a few hours trying to wrap my head around what I was doing wrong on port forwards, initially I had the issue with NAT ALG but got that disabled, then the echo call was working but not Obitalk reg. Finally went nuclear and hooked the Obi200 directly into a fiber ONT completely skipping the router and LAN all together and accessing the website with a cellphone, still does not register. Port settings when behind the NAT must be right because the echo call is working.
Found other threads mentioning the same issue months ago too, so it's also a recurring issue. They really broke the registration system if it needs reset every few weeks.
https://www.obitalk.com/forum/index.php?topic=14943.0
https://www.obitalk.com/forum/index.php?topic=14947.msg94440
Navigation
[0] Message Index
[#] Next page
[*] Previous page