I have obitalk account with 2 Obi202 devices already registered.
Now I purchased Obi2182 phone and am trying to add it to obi talk dashboard.
I dial requested numbers of the form **5 NNNN
but it always fails to add phone to dashboard after timeout.
Otherwise the phone is connected to ethernet (both to WiFi and to ethernet) and I'm able to successfully connect to echo test **9222222222
Any ideas how to add it to obi talk dashboard.
Or is this phone not supported by dashboard?
Hi:
Yes, you should be able to add a 2182 to the OBiTALK dashboard. What country are you in right now? Where did you purchase the 2182? Is it brand new from an authorized retailer, or did you get it from eBay, Craigslist, or some other third party?
> What country are you in right now?
US. no VPN, just plain Comcast cable connection via Asus router.
> Where did you purchase the 2182? Is it brand new from an authorized retailer, or did you get it from eBay, Craigslist, or some other third party?
I bought it from Amazon https://www.amazon.com/gp/product/B076JKV5CL/
brand new.
It was shipped directly by Polycom according to shipping label.
That's odd. Perhaps the portal is having one of its occasional problems today. I happen to have a brand new 2182 that I will try to add to my portal account tomorrow and let you know how it goes.
OK, I took some time just now, to unbox and set up a new 2182. It behaves just like yours -- I can call the echo test number and other OBi phones, but the **5 xxxx procedure isn't working. So, there's nothing wrong with your hardware or network connection; there's something wrong at Polycom.
Given that it's Thanksgiving weekend, I don't know when they'll fix it, but I will let them know. Thanks for reporting this.
same issue but with a obi200.
Probably an issue with obi server.
Let me know when it will be fixed on your side,
thanks
:( same issue .can't add to dashboard ! hopefully issue fixed soon b4 i return
Same deal. Wish I hadn't spent hours trying to fix the damn thing before stumbling upon this thread. Terrible customer experience to have a provisioning server down with no customer-facing messaging. WTF.
As an aside, I think its an SSL cert expiration. Which is lame. I guess they're not on top of their stuff.
Nov 23 03:18:34 192.168.16.140 BASESSL: Can not find custom CA file 0 80
...
Nov 23 03:19:26 192.168.16.140 OBHSN_SIGNUP:user event??
Nov 23 03:19:26 192.168.16.140 BASE:resolving root.pnn.obihai.com
Nov 23 03:19:26 192.168.16.140 [DSP]: set FXS(0) DTMF detection level to (3)
Nov 23 03:19:26 192.168.16.140 [CPT] --- FXS h/w tone generator (ringback)---
Nov 23 03:19:26 192.168.16.140 [DSP]: set FXS(0) DTMF detection level to (3)
Nov 23 03:19:26 192.168.16.140 OBHSN_SIGNUP:server tcp connected
Nov 23 03:19:28 192.168.16.140 BASESSL:connect error:0:5[4640]
Nov 23 03:19:38 192.168.16.140 [SLIC]:Slic#0 ONHOOK
+1 - trying to re-connect (debug) my Google Voice and tried to remove/re-add - cannot add my obi202...just times out
Mine still can't be added either. I hope they get this fixed soon.
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!
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.
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.
So does that imply the problem is only affecting new registration of devices? I do have to say that not having 7x24 support doesn't seem very good. If users are relying on the OBi products for phone services it would seem to me that good support is important.
It only impacts adding a new device to the OBiTALK portal.
First device here (OBi202). It's at least good to know that I wasn't messing up somewhere. I'll subscribe to this thread hoping to get an update when it's all fixed.
Same problem :'(
same thing here - annoyed, just got out my OBI202 which has been unused for a long time, reset it and now can't add it... :-[
New customer and I get the same issue.
Given all the problems we've had with Polycom at work, let me count the ways I'm not surprised they f'd this up too.
Quote from: paplefree on November 23, 2018, 07:58:30 PM
Given all the problems we've had with Polycom at work, let me count the ways I'm not surprised they f'd this up too.
Well that's a bunch of B.S.
Quote from: SteveInWA on November 23, 2018, 08:01:25 PM
Well that's a bunch of B.S.
So is not being able to register any new devices for going on two days now, but per typical Polycom fashion they'll pull logs, find nothing wrong, reboot, and go about their business.
Just tried again and still failed. Any hint from Obi/Polycom as to when this will be fixed?
Quote from: paplefree on November 23, 2018, 08:14:28 PM
Quote from: SteveInWA on November 23, 2018, 08:01:25 PM
Well that's a bunch of B.S.
So is not being able to register any new devices for going on two days now, but per typical Polycom fashion they'll pull logs, find nothing wrong, reboot, and go about their business.
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.
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.
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.
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.
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.
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.
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 ?
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=14943.0)
https://www.obitalk.com/forum/index.php?topic=14947.msg94440 (https://www.obitalk.com/forum/index.php?topic=14947.msg94440)
Quote from: isaac_unixapp on November 24, 2018, 10:01:52 AM
btw - here's what I have tried, to no avail:
There's no point in trying anything. This is a server side issue and won't be fixed until at least Monday. Lately, this has been happening nearly every weekend.
Quote from: isaac_unixappUpon completion of it, though, here's what I see on my device:
HardwareVersion 1.4 help
SoftwareVersion 3.2.1 (Build: 5757EX)
Latest version is 3.2.2 (Build: 5921EX) which you can download and update with manually if desired.
http://fw.obihai.com/OBi202-3-2-2-5921EX-332148940.fw (http://fw.obihai.com/OBi202-3-2-2-5921EX-332148940.fw)
I am not able to add obi 200 just bought from Amazon. Echo test is OK and when we dial the number **5 XXXX it says number sent to server and after that nothing happen and the message is it failed. please advise what need to be done I am new to this unit and system.
Thanks.
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.
well, arguably adding device to dashboard is a one-time action, and most of normal operations (e.g. calling via SIP provider) do not require connection to obihai/polycom servers.
Quote from: dilmah on November 24, 2018, 11:36:53 AM
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.
well, arguably adding device to dashboard is a one-time action, and most of normal operations (e.g. calling via SIP provider) do not require connection to obihai/polycom servers.
I think the point, at least to me, is an indication of the level of support one can expect for other aspects of the OBi products. This seems to be a recurring issue and, though adding a device should be a one time event, what will happen if/when other functions fail? Will Polycom react more quickly? I now understand that support isn't 24/7 but this seems to be an unnecessarily long outage, not inconsistent with previous ones.
One further thought is that to have this occur during the "Black Friday - Cyber Monday" time frame may not be a good thing.
Quote from: stef on November 22, 2018, 06:22:21 AM
same issue but with a obi200.
Probably an issue with obi server.
Let me know when it will be fixed on your side,
thanks
Same here with an Obi 200. Power green, connnection green, all tests pass, DNS confirmed, rebooted modem and router. Still unable to add the device. I tried to call on Friday but there was no one there during regular office hours so I am assuming the staff took the long weekend. I'll update if fixed.
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.
What is rubbish exactly? The three day outage? The lack of any official notice or communication? Or me saying Polycom's support sucks and has always sucked?
I've been working with Polycom and their products for 18 years. This is exactly the kind of support I've come to know and love. Hell, even paying for the premier support or whatever it was called at the time never really amounted to much. They're all very nice people, but at the end of the day still broken. Just like my phone is right now.
Tell you what, I'll go away as soon as Polycom fixes their server since you're apparently the only way to get an update out of them.
Quote from: Taoman on November 24, 2018, 10:36:49 AM
......
Latest version is 3.2.2 (Build: 5921EX) which you can download and update with manually if desired.
http://fw.obihai.com/OBi202-3-2-2-5921EX-332148940.fw (http://fw.obihai.com/OBi202-3-2-2-5921EX-332148940.fw)
Many thanks for this tidbit, updated.
The copyright now reflects:
Copyright© 2018 Polycom, Inc.
I also see the font/image branding has changed from Obihai technology, inc, to Polycom.
AND, I am beside myself -- I am able to register the device now! @taoman -- that pointer to the firmware update seems to have done it for moi -- many MANY thanks!!
able to register new obi200 few minutes ago
Quote from: haiml on November 24, 2018, 08:31:31 PM
able to register new obi200 few minutes ago
Works for me as well with Obi2182
Any statement from Polycom as to the cause and fix for all this?
Quote from: WildBillPDX on November 25, 2018, 09:39:46 AM
Any statement from Polycom as to the cause and fix for all this?
No, and aparently won't be until someone get back into the office the coming week. Everyone is just going to have to be patient, I suppose.
Had the same issue. I was having some connection issues so I deleted my OBI202 from the portal and factory reset the firmware. I was unable to add the OBI202 back to the portal. I updated the firmware to 3.2.2 (Build: 5921EX) downloaded from the link listed several posts above. Afterward I added my OBI to the portal without a problem. The registration worked immediately.
Quote from: finbar127 on November 25, 2018, 05:15:49 PM
Had the same issue. I was having some connection issues so I deleted my OBI202 from the portal and factory reset the firmware. I was unable to add the OBI202 back to the portal. I updated the firmware to 3.2.2 (Build: 5921EX) downloaded from the link listed several posts above. Afterward I added my OBI to the portal without a problem. The registration worked immediately.
http://www.obitalk.com/forum/index.php?topic=15418.msg96218#msg96218
Quote from: drgeoff on November 26, 2018, 03:29:32 AM
Quote from: finbar127 on November 25, 2018, 05:15:49 PM
Had the same issue. I was having some connection issues so I deleted my OBI202 from the portal and factory reset the firmware. I was unable to add the OBI202 back to the portal. I updated the firmware to 3.2.2 (Build: 5921EX) downloaded from the link listed several posts above. Afterward I added my OBI to the portal without a problem. The registration worked immediately.
http://www.obitalk.com/forum/index.php?topic=15418.msg96218#msg96218
Interesting. I tried several hours after the post about updating the firmware and my device would not register. After I updated, it worked immediately. Perfect timing I guess ::)
OK! I tried again this morning and everything worked great. It seems Polycom has fixed the issue.
So 2 1/2 years later it's still down? Bought a new one off of Amazon and it's failed for a day now
Quote from: GrandMstrBud on February 11, 2021, 05:38:35 PM
So 2 1/2 years later it's still down? Bought a new one off of Amazon and it's failed for a day now
Similar situation as I'm working to set up an Obi200 (bought from Amazon) and configuration portal is not working for me. I updated the firmware to 3.2.2 (Build: 5921EX) but no change in portal response (still times out without adding the device).
I'm having the same issue. Got a brand new OBi200 from Amazon. The echo test works just fine. When I put in the **5XXXX code, it says, the "code as been sent to the server", but nothing ever happens. I did this a few minutes ago and during the timeout countdown, I entered the code about 12 times, got the same reply every time, but the device never go added. If I've just wasted my money on this device, everyone needs to be warned. Based on what I'm reading on this forum, this device is a SCAM, unless someone can convince me otherwise.
Quote from: JamminJohn on February 12, 2021, 10:58:16 AM
I'm having the same issue. Got a brand new OBi200 from Amazon. The echo test works just fine. When I put in the **5XXXX code, it says, the "code as been sent to the server", but nothing ever happens. I did this a few minutes ago and during the timeout countdown, I entered the code about 12 times, got the same reply every time, but the device never go added. If I've just wasted my money on this device, everyone needs to be warned. Based on what I'm reading on this forum, this device is a SCAM, unless someone can convince me otherwise.
No need to post the same thing more than once.
ETA: Just kept trying and it finally worked. Adding GV worked flawlessly thereafter.
I just got a new OBi212. I also cannot add it to OBiTalk. I set an ip reservation in my router and I can get the 212's web page and login. I can do the echo test. I configured it for remote syslog and I see the following when I **5 NNNN and hear the sent to server message:
Feb 23 15:56:16 10.141.21.11 OBHSN_SIGNUP:server tcp connected
Feb 23 15:56:16 10.141.21.11 BASESSL:connect error:-1:5[4625]
but it just times out after many many attempts over several days. I just upgraded the firmware to 3.2.2 5921EX and same thing. I have had a 110 for almost 10 years that remains activated and working (not with GV of course) and got a 200 3 or so years ago and it is activated and works fine with GV (also on 5921EX) and I have configured them together so my cordless phone is attached to the 110 as well as FiOS Digital Voice on LINE and I can call out and receive calls on GV as well as FDV including with a SIP app (Zoiper) on my Galaxy S10. I got a good price for the new 212 on Ebay $44.80 + tax, free delivery so thought I would consolidate into a single device from the 110+200.
I submitted a report to Poly a few days ago with the above details and got a stock reply to check power, echo test etc but no reference to the BASESSL error at all. I did not know if I could upgrade to the 3.2.2 5921EX on the 212 since it is not listed so replied to support response asking that and only got told that question got escalated. Went ahead and upgraded anyway and it appears to at least boot and show the web interface with the new version number.
I thought maybe the newer version might fix the BASESSL error but no.
I don't know what else to do but keep trying to add hoping it is a problem at Poly and their servers. And keep asking support for help.
Spoke with a Poly rep and the basically said its been down for 4 months and they don't when it will be back up. What is that? This company is a joke, ever since Polycom took over it has taken a jump off a cliff.