Obi100 No inbound calls, outbound works fine

(1/4) > >>

pbd3mon:
Hello,

I have been using my OBi100 for several years now without any issues but in the last 2 weeks we stopped receiving calls (outbound calls still work fine).  When I call from my cell I get silence for about 15-20 seconds and then a busy signal.  No changes have been made to any of the settings.  I tried the basics like rebooting the OBi and my modem but that did not work.  I have been digging around to find possible solutions to our problem but so far I haven't had any luck.

Here is some additional info:

- using Voip.ms
- using OBi100
- Made sure server on OBi100 matches the server registered with Voip.ms
- Dialed *79 to disable DND (do not disturb)
- Checked Voip.ms echo test and it worked fine
- Checked Voip.ms call record and I see the incoming calls on the list
- Logged into OBi100 web interface and I do not see any of the incoming calls only the outbound calls are on the list.

I think I have reached a limit of my technical ability so I hope that I can tap into the vast knowledge of this community and I'd like to thank everyone for their time and effort in advance.

pbd3mon

SteveInWA:
Hi:  disclaimer:  I'm not a voip.ms customer, and so hopefully somebody who is, will chime in.

Just a couple of quick thoughts:  

If all inbound calls (tests you have made from your cell phone, and others, for example) appear on your voip.ms webpage as received, then it would seem that the inbound call route is working to their server, but failing to reach your SIP client (your OBi).  

Is your OBi 100 listed on your OBiTALK web portal account?  http://www.obitalk.com/obinet/pg/obhdev

If so, look at the status page, and click the device name, and view its status page.  Scroll down to look at the "status" column.  Does it say "Registered", or something else?

If your device is not on OBiTALK, then pick up the attached phone and press ***1 and write down the IP address it speaks to you.  Go to that address on your web browser, to view the status information.  You can also view the call history from that web page, to see if it shows the inbound calls.

The goal here is to see if there's a problem with your voip.ms setup on the OBi.

If it shows "Registered" but inbound calls fail, I'd suggest opening a ticket with voip.ms to troubleshoot.  If it isn't showing "Registered", you can try eliminating the OBi as the source of the problem by unplugging your OBi, then installing a SIP "softphone" client on your computer, and entering your voip.ms SIP server credentials (user name and SIP password), then trying inboubd and outbound calls.   Here's an easy-to-use and free softphone:  http://www.counterpath.com/x-lite/

If it works with X-Lite, but fails with the OBi, then you've got an OBi problem we can troubleshoot.

pbd3mon:
SteveInWA,

Thank you for your reply,

The status of my OBi says Registered.  When I said "Logged into OBi100 web interface" I meant through the IP address, in the call history there I do not see any of the incoming calls only the outbound calls are on the list.

Should I still try troubleshooting with the softphone?  Or does this sound like an OBi issue?

SteveInWA:
I think it would be worth it to try unplugging your OBi and trying it with X-Lite.  It shouldn't take more than 10 minutes, and it will quickly determine if you have a configuration issue with your OBi.  If it fails in the same way as it does when using the OBi, then open a ticket with voip.ms.

By the way, have you changed anything at all with regard to your home network or internet service recently that might correlate with the failures beginning?

BruceW:
Hello,
  You might want to try logging into your voip.ms Portal Home page.
Take a look at the "Issues and Mainteance" section and you will see
that there has been some problems with US DID numbers Inbound
issues. This problem has been going on since Dec 4th and not sure
all network issues have been fixed. You might at first try another server
like tampa - newyork - atlanta etc, to see if that helps. Other than that
open a trouble ticket with voip.ms and let them know what is going on.
They will help you out.
Bruce.

Navigation

[0] Message Index

[#] Next page