OBitalk service is flakely lately!
BobTeatow:
I have an OBi100 and Obi110, they were working fine for a few months. Lately, they are having trouble staying registered/connected to the OBitalk service. SP1 and SP2 connections are okay.
When I try to pass a call from one Obi to the other, I get errors, looking into the status screens I see that one or the other is not "online" to the Obitalk server. Looking at the Obitalk status from the device screen I see "backing off"....
Seems problem is at the Obitalk service end. Please fix!!!
BobTeatow:
On the chance that there is or was a problem with my router/NAT or something,
I changed my OBI100 to use a new static address on my local net, I rebooted my router and the OBI,
and still the OBI100 shows .... "backing off" for the OBiTalk status. SP1 is google and SP2 is voip.ms and those both work okay.
Curiously my OBI110 seems okay, as does my Android/OBion softphone - both connecting through the same home router. And they can call each other via Obitalk.
What to try next?
I use the OBI100 to drive my home office phone, I use the OBI110 to drive the cordless phone system for the rest of my house. On the OBI110 SP1 is (another) google number and SP2 is Callcentric.
I was relying on Obitalk to pass/gateway calls from one to the other, depending on calling number and/or dialed number. E.g if you dial 411 or 911 on any phone the call is routed to the OBI110 and out to SP2.
If you dial 011x. on any phone, the call is routed to the OBI100 and out to SP2 to get international service from voip.ms.
As I wrote previously, all was working fine, until a few days ago. When I noticed that one or the other or both OBIs were not staying registered to Obitalk.... Let me recheck ...
Oops, now both of my OBIs have gone "red" on the OBi "Dashboard"!
lk96:
I have been experiencing similar instabilities with Obitalk.
I have both an Obi100 and and Obi110 at home. Curiously enough,
when I tried to access the Obi110 remotely (though Obitalk) I get
the error message shown in the attached image snapshot. Even though
the error message said the device was not online, I could use it
to make calls through it (but I was not using it yet as a voice gateway for
Obi to Obi forwarding/bridging).
As a sanity check, I tried to access the Obi100 device through Obitalk and that one
was perfectly reachable.
In my case, the Obi110 seemed to be functioning fine all along and was accessible
when I tried to configure it through its local (non-routable) IP address when I was at home.
The error message seemed to be intermittent.
Both Obis in my environment have static IP addresses in the 10.0.0.x space.
L.
BobTeatow:
Checking again, now both OBIs show green on the dashboard....
This is why I said flakey... I did nothing since the last post...
I was really "high" on OBI, telling all my friends and relatives how great it was...
Now I'm not so sure....
BobTeatow:
LK96, Good to see I'm not the only one. This shows that the problem is not peculiar to my household.
Of course, I get the same screen when I try to access the OBI status or configuration screens from the obitalk website, that is just another symptom of the connection between the OBi1xx device and the OBItalk network being busted.
And, yes, the design is sound enough, so that if you're making or receiving calls via SP1 or SP2, then the state of obitalk does not matter.
BUT, I was depending on the OBItalk connection for bridging/gatewaying calls between OBI1xx devices, which is one of the big selling points of OBIHai....
SUGGESTION to OBIHAI.... For OBI1xx to OBI1yy gatewaying, you could cache the addresses, so that the software would be more robust against OBItalk network/server failures.
FOr example, in my household, once the two OBI1xx devices find each other, they should cache each other's network addresses, so they can continue to pass calls back and forth to each other, WITHOUT contacting the OBItalk mother server.
If you do that, you'll have happier customers since we'll be much less likely to notice outages on your network/server(s), and you'll lighten the load on the mother server -- win-win-win.
Navigation
[0] Message Index
[#] Next page