There is no service available to complete the call
Harvey:
My Obitalk Dashboard shows that my Obitalk is online (green light), but, whenever I call out with my phone I get a message now, "There is no service available to complete the call". For the past week I had no such problem, but just today suddently I could not dial out through my phone attached to my Obiha. I found that my Obitalk was offline. I uninstalled the device then installed a new device and got back the green light. But I still have the same problem ""There is no service available to complete the call"
I tried the test someone recommended in another post, "Pickup the phone and dial **9 222 222 222 and see if you can run OBiTALK's echo server test." That worked.
That same person in the other post also suggested, "try dialing **9 333 333 333 and see if you can get to AA (from there you can select option 2 and then dial another US number, end with a # key as an additional test). Then I tried that and got "There is no service to complete the call".
Any ideas?
I just verified by making another call out from my Gmail voice and
it worked without the Obihai device.
RonR:
Your post is very confusing. OBiTalk and Google Voice are totally unrelated and one doesn't need the other to work:
1. You don't need OBiTalk or its Dashboard for Google Voice calls to work (**1 and/or **2).
2. It doesn't make sense that you can successfully call **9 222 222 222 but not **9 333 333 333. They are both OBitalk calls and use the very same service in your OBi.
Harvey:
Sorry, RonR, I need to clarify.
1. I understand that I don't need OBiTalk or its Dashboard for Google Voice calls to work (**1 and/or **2).
I just wanted to inform everyone that my Dashboard does show that the Device is Online. My issue is that I can not dial out (or receive calls into my phone set that is attached to my Obihai device). I did try calling again now with the prefix **2 (my Obihai is listed as SP2 on my dashboard), and even using the prefix **1 and still I get the same error message, "There is no service to complete your call".
2. You wrote "It doesn't make sense that you can successfully call **9 222 222 222 but not **9 333 333 333. They are both OBitalk calls and use the very same service in your OBi." I just now tried those two tests again and now both tests work. Thanks for the heads up.
However, if someone calls to my Google Voice number, although for a week I had no problem, now my phone set attached to my Obihai does not even ring and when I pick it up, I only hear a dial tone, although calls to my Google Voice number come into my landline properly. I was able to call out through my Google Voice via my handset connected to my Obihai for about one week, but now, even if I try to call out with the **2 or **1 I can not get through (same error message).
I have upgraded to the newest Obihai firmware and have my Google Voice settings set so that calls to my Google Voice number are to ring both to my landline and my "Google Chat".
biomesh:
Quote from: Harvey on February 26, 2011, 07:41:16 am
I have upgraded to the newest Obihai firmware and have my Google Voice settings set so that calls to my Google Voice number are to ring both to my landline and my "Google Chat".
So are you logged in to GV/Google chat when this issue happens? If this is the case, it is due to being registered to GV twice and the devices are fighting over who is the primary connection.
I would make sure you stay logged out of GV/GC and see if that fixes the issue.
RonR:
biomesh,
Google Voice does not use SIP and there is no concept of being registered. Being logged into your Google Voice account shouldn't cause problems (it doesn't for me). Having Google Voice ring a landline as well as Google Chat should also not be a problem.
Navigation
[0] Message Index
[#] Next page