Is there a known issue with Obitalk servers right now?
fuzion:
Quote from: drgeoff on February 07, 2021, 02:32:41 pm
https://www.poly.com/us/en/support/knowledge-base/kb-article-page?type=Troubleshooting__kav&lang=en_US&urlName=KB24053&t=All&k=
Support responded to me to try everything I already tried, I advised I did, so they said to keep trying due to intermittent issues.
However, perhaps something is being done of it per https://status.obitalk.com/ :
Hi PDMS-SP Users,
PDMS-SP services will be upgraded to improve performance. During this time, the service may be slightly interrupted. Thank you for your patience.
Team PDMS-SP
Posted on Feb 10, 01:54 UTC
Fingers crossed. I'll try registering again tomorrow.
fuzion:
Maintenance concluded not long ago. I attempted to add it, and was successful the second time around!
LoneStarState:
I've been trying for weeks to Add Device which is a Obi202. Literally over 2000 times attempts on ObiTALK Add Device **5 xxxx at differing times of day and night and days of the week. I am able to dial ***1 for the Obi's address. Checked for Device Update. I pass the echo test, changed DNSServer1 to 4.2.2.2, have opened all the recommended ports and tried many other settings on my router. My ISP, AT&T U-verse, has verified the ports Obi recommends are open. I have sent 2 inquires to support via email, one general inquiry and last one with a carefully crafted email detailing every step I have taken and the exact equipment I have as well who is my ISP. They did not even bother to read it and just sent a off topic form response of the same garbage on first step recommended fix's and what to do to fix google voice that does not apply when you can't add device. I've called two support people, one could only say to keep trying and the other was not familiar with a BGW210-700 router provided by AT&T U-verse which is pathetic since problems like this is why I chose to go with a router/modem that was widely used by a ISP widely used in order for support/tech to be familiar with such equipment. Support person did not know how to forward/open ports because apparently BGW210 uses NAT/Gaming and not DMZ. I don't understand any of this crud to be honest and never wanted to! I was under the impression from Obi/Poly advertisement and public info Obi/Poly produced that the Obi202 was basically a plug and play device. I have spent well over 40 plus hours trying to figure this crud out and dialing and redialing **5 xxxx. I'm so sick of dialing, researching and reading technical junk, never knowing if my efforts are in vain and if I will ever be able to use this device I was led to believe was a solid ready to go established operating device/service. I made decisions and changes I cant reverse based on this device working and working with Google Voice. I now know that this Add Device issue with Obi/Poly Servers go back years and years. In my research I have found the Add Device issue goes back over a decade. Obi have repeatedly claimed they know of the intermittent problem, know why and are working it with the same answer to Obi Owners to just keep trying. Just keep trying as a solution from a self admitted product/service defect is not what I expect from a corporation much less one that is affiliated with Google. Something just does not add up? There has to be a better answer for Obi owners than to keep trying and not even knowing if their systems settings are correct for the apparently finicky Obi/Poly servers or if they will ever be able to use their device they paid for do to no fault of their own and their wasted personal time lost forever trying to use equipment and services that they were sold as functioning properly.
rbowles:
Dear Poly/ObiHAI support team:
**5 is broken right now because the HTTPS (TCP port 443) that the phone connects to apparently in response to dialing **5 is DOWN.
Down in this case is easily seen with a simple packet capture. Down in this case could be a firewall/access-list just dropping the connection attempt. The SERVER is up, it is pingable and Obitalk protocol is flowing.
The server is not responding at all on port 443. See attached PCAP.
rbowles:
Aaaaannnnd, that port just started responding so I rushed over to the phone and dial **5 and it worked.
Navigation
[0] Message Index
[#] Next page
[*] Previous page