Outbound OBiTALK Calls Stopped Working

(1/3) > >>

ricky:
A couple days ago, one of my OBi110 units became unable to make outbound calls over the OBiTALK network. Inbound OBiTALK calls still work, and outbound SIP calls still work. I did a factory-reset on the unit, and the problem remains. I have another OBi110 and an OBi100 at the same location that are still working just fine. I even rebooted my router, but the problem still remains on the one unit.

Outbound OBiTALK call attempts on the affected unit all get a busy signal about 8 seconds after dialing. The call state during this time shows "trying" for PHONE1 and "lookup" for OBiTALK1. The OBiTALK Service Status shows "Normal (User Mode)", just like the working units do.

What could be wrong?

giqcass:
As a test create a speed dial with the following
PP(ob222222222)

See if that will connect.  If it does you may have a corrupted dial plan somewhere.

ricky:
Thanks for the reply giqcass. I just tried your suggestion, and the result is the same, about 8 seconds of silence after dialing, then a fast busy. Note that the problem remained the same even right after a factory reset, before restoring any saved config. The digit map is factory default at that point.

One thing I didn't mention before is that the OBiTALK1 call state is briefly "turn-alloc", whatever that means, prior to ending on "lookup" for most of the time before the busy signal. This happens on dialing any OBiTALK number, including using your speed dial test. The call log always shows the outbound call, but never "Call Connected". So it is not that the OBi is refusing to attempt the call, it just doesn't work. I don't think there would be a call log entry if the call didn't pass digit map processing, would it?

Usetheforceobiwan:
I would try disabling the Obitalk network connection, re-booting, re-enabling the Obitalk network and then re-booting.  I suggest this as you might have some garbage in one of the caches someplace and this might help clear it out.

ricky:
Just tried your suggestion, Usetheforceobiwan, but it didn't work. I even tried leaving it unplugged for a couple hours, in hope that the OBiTALK server would forget about, but no luck. It's as if this OBi is cursed.

Navigation

[0] Message Index

[#] Next page