News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

Is ObiTalk Down?

Started by Jbyrne, November 15, 2020, 06:32:23 AM

Previous topic - Next topic

Jbyrne

I have my obi302 directly connected to my Azzis cable modem give to me by by spectrum cable.  There is no firewall between my obitalk and the internet.  I tested my connectivity to my router from a free VM located in the AWS cloud with the following command.

nc -z -v -u my-router-ip 10000
Connection to my-router-ip 10000 port [udp/ndmp] succeeded!

All ports going out the internet are wide open, again obi is conncted direct to cable modem, no firewall.

DNS is set to 8.8.8.8
I have tried dialing the echo test and it works fine.
registration using dial **5 xxxx never works, just times out

I have been trying to connect for two days now.  Is there a problem with the obitalk servers?




drgeoff

Quote from: Jbyrne on November 15, 2020, 06:32:23 AM
I have my obi302 directly connected to my Azzis cable modem give to me by by spectrum cable.  There is no firewall between my obitalk and the internet.  I tested my connectivity to my router from a free VM located in the AWS cloud with the following command.

nc -z -v -u my-router-ip 10000
Connection to my-router-ip 10000 port [udp/ndmp] succeeded!

All ports going out the internet are wide open, again obi is conncted direct to cable modem, no firewall.

DNS is set to 8.8.8.8
I have tried dialing the echo test and it works fine.
registration using dial **5 xxxx never works, just times out

I have been trying to connect for two days now.  Is there a problem with the obitalk servers?




Except for calls using the Obitalk network (those made by dialling **9 followed by a 9 digit OBi number) no facilities or infrastructure operated by or on behalf of Obihai/Poly are involved in making or receiving calls.

There is or has been an intermittent problem with the Obihai backend server(s) handling the **5 nnnn registration procedure.  Obihai/Poly are aware but AFAIK have offered no ETA for its resolution.  There have been many posts to the forum about it but most seem to have succeeded eventually.

Jbyrne

Thank you for the update.  I will keep trying and posting my results here so others know if the registration process is still problematic.

I just tried now and the registration process failed again, timed out.  I will try again tonight and post the results.

SteveInWA

It's been down on and off since Friday for maintenance.  Wait until tomorrow.

Jbyrne

Good advice,  I give an update Monday night after work.  I just tried one more time for kicks and the server is still down.

Jbyrne

I just got home from work and dialed **5 #### as instructed.  Timed out.  Servers must be still down.  will try again in a few hours.

Jbyrne

I tried the **5 register again and it timed out.  Will try again in the morning.  Hope this helps others who are having the same trouble. 

I know the problem is not on my end.  As noted at the top of the thread, my Obitalk is plugged in directly to my cable modem.  I also confirmed connection to port 10000 using as linux nc command from an external source.

Is there any way to use obitalk with google voice without registering?  Can I set this up manually?

Groutard

Thank you for posting that. Just setting up my obi200 and adding device on obitalk keeps timing out, it's been driving me crazy for the past couple hours. Now I know the cause. Will try again tomorrow.

Jbyrne

update - Tried again - timeout - servers still down... that is all.

drgeoff

Quote from: Jbyrne on November 16, 2020, 06:05:53 PM

Is there any way to use obitalk with google voice without registering?  Can I set this up manually?
No.

Jbyrne

i just tried to register again and I put the obitalk behind my Draytek firewall.  I see sessions talking to may obitalk as shown below.  My Obitalk has has NAT IP 192.168.2.107.  The other addresses are comming from the AWS cloud which is where Obitalk must reside.

-------------------------------------------------------------------------------
     Private IP :Port #Pseudo Port         Peer IP :Port  Interface
-------------------------------------------------------------------------------
192.168.2.107 10000        56464    54.241.160.4 10000    WAN2
192.168.2.107 10000        56464     52.9.223.41 10120    WAN2

The attempt to register to **5 #### just times out.  Obitalk registration process is still not working.  Will try again tommorrow morning. 

Taoman

I just added an OBi202 to the dashboard without issue so it is working..... at least to some degree. I unchecked the box to add Google Voice since I would never use it on this device.

If you haven't already tried, you might try adding your OBi to the dashboard but unchecking the box for Google Voice. You can always add Google Voice later after you successfully add your OBi to OBiTALK.


MSRobi

I have been trying unsuccessfully to register my new Obi202 since 5pm today.  On Oct 23, I successfully registered an Obi200, but it took several hours of trying.  In both cases, **9 works fine, devices successfully obtain IP address on my network.  I put my new device in DMZ, still no luck.  I hope they obi/poly can get there registration servers working soon.

Jbyrne

#13
Morning update.  Tried to register using **5 and still down.  I see active NAT sessions on port 10000 using UDP thus, the device is communicating to obitalk, just won't register. 

I also tried unchecking google voice as suggested in this thread.

The saga continues, will try again tonight.

Jbyrne

I have been trying the **5 registration periodically throughout today with no success.  The operation still times out and my Obitalk is not registered.

I have been also trying **9 222-222-222 and the echo test works fine.  I can see chatter on port 10000 using UDP to the obitalk servers running in AWS.

registartion process is still down.  I am not posting these to be a pest, I am sharing this info so others will know they are not alone trying to register their Obitalk in vain.

Jbyrne

Just tried again this morning, will not register.

echo test using **9 222-222-2222 works fine.

Jbyrne

Just tried again this morning, will not register.
I will keep trying through out the day.

echo test using **9 222-222-2222 works fine.

I am going to contact my IP phone vendor and see about a refund.  I think the polycom acquisition has really screwed up obitalk.  Might be time to transition to a new IP vendor to something like ooma.  A free phone services that does now work is worthless.


azrobert

What firmware level do you have? I think the current level is 5921.
Download:
http://fw.obihai.com/OBi202-3-2-2-5921EX-332148940.fw

A factory reset can't hurt.

Do you hear "**5xxxx has been sent to the server"?

Groutard

still same issue here as well. Obi200, installed the latest firmware (my obi200 was purchased 5yrs ago and stayed in its box till now...I know...). Tried over 30 times the past 4 days, I do get "the number you dialed **5... has been sent to the server" but the Add an OBi Device page doesn't seem to receive it and ends up timing out, every time.
**9-222-222-222 echo test works properly...
Any suggestion would be welcome.

Jbyrne

I installed the firmware to the latest 5921 and tried again.  I enter **5 #### and i do get 'the number has been sent to the server' response.  Still not registering, times out.

I logged into my router and I see the following communications.  Looks good to me.  I see communication on port 10000 to my obitalk at 192.168.3.11.

-------------------------------------------------------------------------------
    Private IP :Port #Pseudo Port         Peer IP :Port  Interface
-------------------------------------------------------------------------------
  192.168.3.11 49898        51308    173.0.48.220   123    WAN2
  192.168.3.11 33720        35130    54.241.160.4   443    WAN2
  192.168.3.11    53           53  185.232.64.121 33707    WAN2
  192.168.3.11 10000        44178     52.9.223.41 10120    WAN2
  192.168.3.11 10000        44178    54.241.160.4 10000    WAN2
  192.168.3.11 10081        44259     52.9.223.41 10120    WAN2
  192.168.3.11   389          389    14.1.112.177 50238    WAN2