Obi202 inbound call problems [voip.ms]
babo:
Ever since I bought my Obi202 about a year ago I've been having issues where inbound calls ring busy until the device is unplugged. This happens enough to be annoying -- generally about once a month.
I have the Obi setup with voip.ms and everything works fine for about one month. This problem doesn't seem like any of the obvious stuff -- because I'm able to pick up the phone and make outbound calls, and I can see the inbound calls in my CDR reports on voip.ms.
I know this sounds crazy, but when was the firmware 3.0.1 (Build: 4041) firmware released? I think I looked at it last night on Obitalk and there wasn't an update available. Now I see that there is one and the phone is busy.
Is there any chance that firmware releases cause this behavior? Like you can't receive calls until you update or something strange?
Also does anyone know of a way to remotely restart the ObiHai device?
Shale:
Reset the OBi202 remotely: I think this would work: Suppose you are not using SP4. Change
Voice Services > SP4 Service >X_CallParkedRing from 10 to 9 (or 9 to 10 next time). Then click Submit at the bottom.
The OBi202 will reset.
Now what does X_CallParkedRing do? I just picked it because it was something that will not matter. It only matters when using OBiPlus. There are various things that could be changed benignly, that would cause a reset when submitted.
Regarding firmware, if there is a newer firmware offered, On the OBiTalk Dashboard there will be a yellow triangle that you could click on to trigger new firmware. I have such a triangle myself. There will be a box that lets you change your mind or to continue. http://www.obitalk.com/forum/index.php?topic=9.0 talks about the various ways to trigger a firmware update.
Also on the Dashboard is a green icon if OBiTalk thinks it is communicating with your OBi.
I don't know anything about your phantom busy signal problem. I expect there is a SIP status indicator on the voip.ms website. Get to learn what that looks like normally, and check what it indicates when there is a problem.
babo:
Wow thanks for the fast response. Knowing an easy way to reboot the thing from the web makes dealing with this a lot easier. Before I was having to drive for 30 minutes just to unplug the thing.
1) I can place calls to the Obi # from the obitalk website and have a normal conversation with the other side. This kind of tells me it is the connectivity to voip.ms having an issue.
2) The obi hai management page says SP1 - "voip.ms Account Registered ". That kind of tells me the device WAS communicating properly at some point.
I'm like 99% sure this is an issue with the device and voip.ms at this point. I just need to access the devices log files or something I guess. Maybe it has a syslog or something handy.
babo:
I guess the device isn't able to communicate properly with voip.ms anymore. I tried everything including a full power off and left it unplugged a good 30 minutes. No luck.
It shows "registered" in green on the voip.ms status page and on the obitalk management page. The status of the device is also green in the obitalk management page and the firmware is fully up to date.
Shale:
Here is a blunt tool but relatively simple method you could use. Assuming voip.ms is on SP1, delete the SP1 in the Configure Voice Service Providers (SP) section. Then set up SP3 with the voip.ms info. Alternatively, set up SP3 with the voip.ms info on SP1 again.
Navigation
[0] Message Index
[#] Next page