Outbound OBiTALK Calls Stopped Working
Usetheforceobiwan:
LOL, I had said to try clear out your Obi's cache, based on this development it looks like Obihai needed to clear out THEIR server's cache or something. Some sort of corruption maybe that randomly impacted certain Obi's? Who knows ???
ricky:
It's back! The same frustrating problem I had back in May has returned as of last night. One of my 3 OBi devices at home, the same one as before, can no longer make outbound calls over the OBiTALK network. Incoming OBiTALK calls work fine. SIP calls work both ways. No amount of rebooting/power cycling/factory resetting makes any difference. Last time the problem went away on its own, but only after several days of downtime. Dialing any OBiTALK number from the affected unit just gives a fast busy after a few seconds delay.
This is really frustrating, as the primary purpose of this unit it to access (via OBiTALK) a magicjack physically connected to another OBi110's LINE port for outbound calls.
Is anyone else having a problem with outbound OBiTALK calls? If anyone from Obihai is listening, I'd appreciate your checking out your servers.
Midshires:
It will be of no consolation to you but I have the same problem.
This is the second day that ObiTALK has been 'off the air', at least at this location in England. Nothing has changed with my equipment and setup. But ObiTALK has stopped working outgoing (I have no means telling whether incoming calls would work).
I have tried repeatedly power cycling both the Obi100 terminal adapters and the BT Home Hub 4 (a residential gateway router modem), all to no avail. I know my broadband service is fine and a Vonage phone using its own Vonage terminal adapter and connected to the same router modem works as per normal.
But ObiTALK does nothing. The Obi100s are sitting there with a solid green light and the central green LED flickers occasionally.
Keying ***1 gives a readout of the local IP address.
Keying **9 222 222 222 returns busy tone.
Keying 222 222 222 without a prefix returns "There is no service to complete your call".
I'm at my wits' end. Although I am a great evangelist for the Obi product range, this level of unreliability is very disappointing. All help will be very welcome!
Andy Emmerson.
BigJim_McD:
On my OBi devices, I get the following results calling the OBi ECHO Test.
1) on OBi202 dialing **9222222222 returns busy tone.
2) on OBi110 dialing **9222222222 connects to OBi Echo Test.
3) on OBi100 dialing **9222222222 connects to OBi Echo Test.
Note1: All other calls on all three devices (incoming and outgoing)
work correctly, including direct calls from OBi device to the OBi device.
Note2: The OBi202 has Vestalink, Google Voice and voip.ms as service
providers and all calls to and from all Service Provider Ports are working correctly
The issue of being unable to call the **9222222222 OBi Echo Test number has
occurred before, then clear up for a while only to return again.
SteveInWA:
It's an issue on their end. I have the same problem...yesterday it went from both of my two devices working, to neither, to one working, and that's where it sits now. There's a related thread with respect to devices showing as offline on the portal, and I found that the OBiTALK SP slot shows as "backing off" on the local web page for the failing device.
Open a ticket with them. I did. They need enough cage-rattling to recognize that it's not isolated to some user error.
Navigation
[0] Message Index
[*] Previous page