OBitalk service is flakely lately!
BobTeatow:
This message received a while ago....
There has been temporary outage with the obitalk server, we are working on
this.
- Obi Support
Still, I think Obi should implement a "cache peers' IP addresses" scheme.
Stewart:
Quote from: BobTeatow on January 09, 2012, 02:20:21 pm
Still, I think Obi should implement a "cache peers' IP addresses" scheme.
If both uers are behind different NATs, P2P won't work, unless some port forwarding is in place. If you are willing to set that up, using dynamic DNS names, you can do it yourself without help from Obihai.
Alternatively, you can interconnect your OBi devices with a free or paid SIP service, a PBXes account, etc.
BobTeatow:
Stewart, good point. I'm thinking of my case, which I would expect to be fairly common -- both of my OBi boxes are on the same private subnet. They should be able to discover each other, even without the help of the Obitalk server. BUT If that took some extra configuration - I'd sure be willing to do that too, I've done a fair amount of call routing configuration "the Obi way" to get the call handling working to my satisfaction.
I also use Voip.ms which let's me assign "extension" numbers to subaccounts. Each subaccount registers to the voip.ms server via Sip. Then I can call for free from subaccount to subaccount. This works great for forwarding (Google) calls from an Obi box to my Android phone. MUCH better than the crappy Obion app for Android. I also keep a Sip registered to a guest sub-account in my guest bedroom...
(I tried the Obion app, and I still use it to make free outbound calls from my Android, but it has some problems, the worst of which it just is not reliable for inbound calls. The other problem is that it doesn't integrate with the Android contacts list.)
However, I haven't figured out how to use Voip.ms as an Obi gateway. Reading the doc, it seemed there were restrictions and "gotchas"... whereas it was relatively simple to do Obi to Obi gateway functions, EXCEPT, for the problem which began this thread -- the Obitalk server(s) are apparently not as reliable as a service like Voip.ms.
That's understandable - Voip.ms business depends on its servers' reliability. Their revenue stream is at risk. Whereas with Obihai, it seems their revenue if from the devices, not the service. But on second thought, they have chosen to tightly tie their devices to the Obitalk servers, so ...
BTW - I've been a voip.ms customer using Sipura boxes for many years. What sold me on Obi was their easy integration and exploitation of Google voice/talk to obtain completely free phone service using ordinary phone/handsets. I need to maintain two Google voice accounts - and be able to use them simultaneously (one is my office number, the other my wife's) -- so I ended up buying two Obi-boxes ... (If Google supported SIP directly, I could have used my old Sipura boxes. I'm not going to be surprized if there is a deal with or even an acquisition by Google ;-) ...
ONE more request of Obihai - it would be useful to allow another SP or two on the same box - SP3 and SP4. If necessary, you could limit the number of simultaneously active calls, but give me the flexibility of accepting inbound calls from 3 or 4 SIP providers, and routing outbound to any of 3 or 4 Sip providers.
BamaBook:
Try this. Mine went to backing off status I think because I had changed my Google password, which works with my Obitalk dashboard. I went into the account, retyped my password, and then hit refresh, and was back in business.
Navigation
[0] Message Index
[*] Previous page