Can't add to dashboard
Redbeard:
I couldn't sleep so tried mine at 2am. Here's what worked for me. I waited for each device to fully boot before I did the next step.
Unplug my wifi router from my cable modemreboot my cable modemHook the Obi202 directly to the cable modemHook my PC to the LAN port of the Obi202Tried again, making sure to not check the option for Google Voicesecond time dialing the **5 code workedconfigured Google Voicepowered everything offBooted cable modemplugged in WiFi router and powered it onplugged PC back into WiFi routerPlugged Obi202 into WiFi router on the WAN portMade a few test calls and my Google Voice account was working
volkswagner:
Obihai never had good support prior to Polycom purchasing.
They don't even support ITSP accounts which help sell
their product line.
They use extortion methods to get firmware updates (like other vendors so not alone here)!
Well enough rant and on to the topic.
The adoption of devices is totally broken. I've had
regular trouble getting devices added to my ITSP (obitalk)
account. Normally I can just disable a common firewall
rule to allow adding the device.
Code:
add action=drop chain=input comment="defconf: drop all from WAN - need to disable this for obitalk adoption" in-interface=ether1
The above is the last input rule to block all bad stuff not specifically allowed.
I recently tried activating at a customer location with a bone-stock Netgear consumer router.
It failed to connect. The echo test worked (of course). I then spent another 15-20 min dancing
around with router reboots, adding obi200 to DMZ and even direct connection to the Modem.
Um, no go... so either Comcast is blocking or Polycom is doing some really bad stuff.
Has anyone run Wireshark to see what is actually happening (what type of
connection the Obitalk portal is expecting from the Obixxx device)? Does Polycom
document what ports need to WFO for this to work?
Yes, let's blow up Poly's Twitter @PolyCompany how about some support?!!
drgeoff:
The problem is almost certainly at the Obihai/Poly infrastructure/server end. Not the end user's device nor access to the internet including ports. As many posters here attest, after multiple, maybe tens of, attempts without making any local changes they do succeed.
gginsberg:
I just got these notifications in quick succession. So what are the chances one of these maintenance events will resolve (or put a band aid) on the issue ::) :
Start: MAR 18, 02:00 UTC (1hr)
Systems affected: Device Management Servers (Server 10, Server 11, Server 12, Domain Management Service).
Start: Mar 20, 16:00 UTC (4hrs)
Systems affected: Rest API Service, Portal Service and Device Management Servers (Server 1, Server 2, Server 3, Server 4, Server 5, Server 6, Server 7, Server 8, Server 9, Server 10, Server 11, Server 12, Domain Management Service).
Start: Mar 25, 02:00 UTC (1hr)
Rest API Service and Portal Service.
Start: Mar 27, 16:00 UTC (1hr)
Rest API Service and Portal Service.
Start: Apr 1, 02:00 UTC (1hr)
Rest API Service and Portal Service.
Start: Apr 3, 16:00 UTC (1hr)
Rest API Service and Portal Service.
Start: Apr 8, 02:00 UTC (1hr)
Rest API Service and Portal Service.
Start: Apr 10, 16:00 UTC (1hr)
Rest API Service and Portal Service.
Start: Apr 15, 02:00 UTC (1hr)
Rest API Service and Portal Service.
drgeoff:
Quote from: gginsberg on March 17, 2021, 12:44:49 pm
I just got these notifications in quick succession. So what are the chances one of these maintenance events will resolve (or put a band aid) on the issue ::) :
Start: MAR 18, 02:00 UTC (1hr)
Systems affected: Device Management Servers (Server 10, Server 11, Server 12, Domain Management Service).
Start: Mar 20, 16:00 UTC (4hrs)
Systems affected: Rest API Service, Portal Service and Device Management Servers (Server 1, Server 2, Server 3, Server 4, Server 5, Server 6, Server 7, Server 8, Server 9, Server 10, Server 11, Server 12, Domain Management Service).
Start: Mar 25, 02:00 UTC (1hr)
Rest API Service and Portal Service.
Start: Mar 27, 16:00 UTC (1hr)
Rest API Service and Portal Service.
Start: Apr 1, 02:00 UTC (1hr)
Rest API Service and Portal Service.
Start: Apr 3, 16:00 UTC (1hr)
Rest API Service and Portal Service.
Start: Apr 8, 02:00 UTC (1hr)
Rest API Service and Portal Service.
Start: Apr 10, 16:00 UTC (1hr)
Rest API Service and Portal Service.
Start: Apr 15, 02:00 UTC (1hr)
Rest API Service and Portal Service.
Well one can always hope but there have been quite a few scheduled maintenance events in the last couple of months which have not provided any noticeable improvement.
Navigation
[0] Message Index
[#] Next page
[*] Previous page