I've had my OBI100 for over a year, using GV with no problems. Anticipating the loss of GV, I switched to PhonePower which I configured on SP2, made it the default for outgoing calls and left GV on SP1. It worked immediately - BUT about once every two days, the phone stops working. If I dial out, I get a "service not configured" message. Rebooting the OBI fixes the problem. I deleted GV on SP1, in case that was somehow the issue, but that had no effect.
Any ideas? I didn't change anything other than the provider, but the phone has gone from very reliable to flakey.
Quote from: EdWilliams on April 23, 2014, 10:59:06 AM
I've had my OBI110 for over a year, using GV with no problems. Anticipating the loss of GV, I switched to PhonePower which I configured on SP2, made it the default for outgoing calls and left GV on SP1. It worked immediately - BUT about once every two days, the phone stops working. If I dial out, I get a "service not configured" message. Rebooting the OBI fixes the problem. I deleted GV on SP1, in case that was somehow the issue, but that had no effect.
Any ideas? I didn't change anything other than the provider, but the phone has gone from very reliable to flakey.
I also signed up with PhonePower and configured it on SP2, made it the default for outgoing calls and left GV on SP1.
It also worked immediately and then this afternoon, when I tried to make a call, I got "service not configured" message as well.
After rebooting the device all was good again. I hope this is not a sign of the way things are going to be.
Update: I removed the Google Voice configuration completely (it was on SP1) and move the SIP (PhonePower) from SP2 to SP1. So far so good. I will see how it is in the morning.
Same problem here. When this happens, the phone light is OFF on the OBi device, and I can't make calls. However, when I log into the OBi device web page, it shows the service is still registered.
I need to reboot my OBi100 daily. Does anyone have any advice on configuration changes that may avoid this problem?
Keep-alive, registration period, etc.?
Here is some more information on this problem:
When trying to make calls from the outside or a cell phone to my PhonePower phone number, I get a recorded message that says "(my phone #) can't take your call now. To transfer to a fax machine press 7. At the tone please record your message. When you have finished recording, simply hang up or press # for further options." Then I get a beep.
When I login to OBiTalk and check the dashboard, the SP1 shows OBi PhonePower with status Registered.
If I restart the device all is good again.
Quote from: adutchman on April 24, 2014, 02:03:23 PM
Here is some more information on this problem:
When trying to make calls from the outside or a cell phone to my PhonePower phone number, I get a recorded message that says "(my phone #) can't take your call now. To transfer to a fax machine press 7. At the tone please record your message. When you have finished recording, simply hang up or press # for further options." Then I get a beep.
This is because the call is going to PhonePower's voicemail system which you haven't set up yet. I realize this doesn't explain why the calls aren't going thru to your Obi device but that is why you are hearing that recording.
Quote from: Taoman on April 24, 2014, 02:20:16 PM
This is because the call is going to PhonePower's voicemail system which you haven't set up yet. I realize this doesn't explain why the calls aren't going thru to your Obi device but that is why you are hearing that recording.
Actually I did set up the voice mail. It is even forwarding the messages to my e-mail address. No, there is definitely a problem.
I was just on a TechChat with PhonePower. He told me on to make sure that SIP ALG is disabled on my Netgear router and then to following the instructions at this URL...
http://www.phonepower.com/wiki/Obihai_Lite#Obihai_Initial_Sync
I will check things out when I get home later are report back.
I have had the same problem with my Obi100 and PhonePower.
Did a tech chat with the phonepower site and he had me re-submit the information on the obihai site and then reboot the device. Sounds from this like rebooting the device would have been sufficient.
Clearly, this is a problem.
It's even a bigger problem if you read the fine print - once can only get out of the annual phonepower contract for the first 30 days, after that you write off your year's charges if you leave.
I asked the chat tech guy how often I could expect this to happen and whether they were having any incompatibility with obi devices. He blamed the "portal", and when I asked for clarification he meant the Obi website.
But it seems like there is a real problem of dropped service with utterly no warning... nice that they include E911, but damn glad I wasn't calling E911 last night because we had no phone service.
ObiHai needs to weigh in on this. Any Obi people posting here?
all best...
After getting home I checked my Netgear router as the PhonePower tech support person suggested. I found the Disable SIP ALG setting and it was not checked. This means that SIP ALG is in fact enabled. I checked the box and disabled SIP ALG and restarted by OBi100 device.
I remember having to do the same thing a few years ago on my old Linksys router when I was using a MagicJack which is also a SIP device.
My OBi100 device and phone service always seems to work for a while after restarting it. It always seemed to not be working sometime the following day. I will post an update tomorrow to let everyone know how it turns out.
I found a short article about SIP ALG and why VoIP providers often recommend that you turn it off here...
https://support.gradwell.com/entries/23128463-What-is-SIP-ALG-and-why-does-Gradwell-recommend-that-I-turn-it-off-
For those that are having this same problem after switch from Google Voice to a standard VoIP provider, what have you got to lose. See if your router has a SIP ALG setting and disable it. You can always change it back.
Here is an e-mail response from Obihai Support Team...
Do this:
1. Look at your router's configuration.
Go to your router's (the router that OBi is connected to) configuration and disable "SIP ALG"
For example:
http://screenshots.portforward.com/routers/Netgear/WGR614v9/WAN_Setup.htm
Google Voice is not SIP, therefore you never had to do this.
2. After you have saved the setting, reboot your router to make sure that the setting is applied.
3. Now try to make calls out again.
-Obihai Support Team
I have an ASUS RT-N66U ("Dark Knight") router. I couldn't find any SIP settings either on the web interface or by telnetting in and executing "nvram show|grep sip".
I then updated the firmware to the latest version 3.0.0.4.374_720.
I now have a new toggle under WAN|NAT Passthrough for SIP passthrough. (also with the telnet there's a new variable fw_pt_sip=1).
For the moment I've left it enabled to see what happens. The article https://support.gradwell.com/entries/23128463-What-is-SIP-ALG-and-why-does-Gradwell-recommend-that-I-turn-it-off- suggests to turn it off because it may be poorly implemented. If the firmware upgrade doesn't fix things, I'll try turning the NAT passthrough off.
This morning I tried to call me house but it went straight to voicemail and it was really important that I get through because nobody in the house was answering their cell phones.
Then just now, without changing anything, I tried calling the house number from my cell and the call when through. I also have a dial tone to make outgoing calls.
Perhaps things are working okay now, but I have my doubts.
FWIW, I've been experiencing the same thing with my phonepower account - once a week or so, it will simply stop working. My OBi is connected directly to the cable modem (no firewall or router), so the SIP-ALG settings do not apply. Also, (while trying to figure out what to do with the OBi in the post-GV world), I have three SIP accounts on my OBi 202 - I have never seen this type of random failure with the Anveo or Vestalink accounts.
Update:
Steps taken last night (4/25/2014)...
1) Rebooted router to make sure SIP ALG setting change took effect.
2) Completely reset OBi100 device by following instructions provided by PhonePower beginning with step # 2 - ReSetting your Obihai. Here is the link they provided http://www.phonepower.com/wiki/Obihai_Lite
Note that I did not press the reset button located on your Obihai phone adapter
3) Restarted OBi100 device.
As of 3:00 pm today (4/26/2014) everything is still working as it should be.
I, too, had these same problems. First off, I chose Phonepower voip. I was knocked off of the system twice. In both cases I had noticed that my config info was missing. The 1st time i manually replaced the info and went to the phone power site to sync the devices. The next morning no service. The second time I configured through Obitalk approved service providers section. I tabbed on the phone power followed the promps and placed phonepower in the sp1 and left googlevoice in the sp2 section. After the configs were done, I returned to the phonepower site to sync the devices. Earlier I had tried to remove GV to replace with CircleNet voip in sp2. It messed up everything so I reconfig to GV. Now, I have been on for 2 days with no probs.
I hope that this advice works for you as well it has for me.
Good Luck!!
I'm glad to have checked this forum on this matter, as I was attempting to do the setup of Phone Power (using an OBi 100 currently on GV, from the "Approved Providers" page). My problem is that the page will not let me select either the OBi device or the SP slot (from the pulldowns). No info is in the pulldown. And when I try and click the "Signup at PhonePower" button, it turns those previous fields red and says I haven't chosen anything. This isn't looking good, OBi! I really wanted to choose the OBi Lite offering from PhonePower.
Update 5/3/14: Turns out in order for my OBi device and all to display I had to be logged into OBi using my Google account, and not just my Yahoo mail account. After this things showed up correctly and I was able to sign up for the PhonePower deal. However, even though I'm keeping GV on SP1 until May 15, on SP 2 I can't get better than a "Registered" in the Dashboard for PhonePower. The Dashboard won't accept my PhonePower VoIP number with a "1" for country code. Says I have to limit it to 11 characters (which this is), but the Dashboard is appending the sip.phonepower.com into that field. Don't know what's up with this.
Quote from: EdWilliams on April 24, 2014, 07:08:42 PM
I have an ASUS RT-N66U ("Dark Knight") router. I couldn't find any SIP settings either on the web interface or by telnetting in and executing "nvram show|grep sip".
I then updated the firmware to the latest version 3.0.0.4.374_720.
I now have a new toggle under WAN|NAT Passthrough for SIP passthrough. (also with the telnet there's a new variable fw_pt_sip=1).
For the moment I've left it enabled to see what happens. The article https://support.gradwell.com/entries/23128463-What-is-SIP-ALG-and-why-does-Gradwell-recommend-that-I-turn-it-off- suggests to turn it off because it may be poorly implemented. If the firmware upgrade doesn't fix things, I'll try turning the NAT passthrough off.
To follow up on this, this morning I got the same "Service not Configured" message. I've now disabled SIP Passthrough on the router and I'll see if this does anything useful.
I registered for PP and set it up about a week ago. It worked fine for 2 or 3 days and then suddenly stopped working (outgoing calls gave a service not available message). I found some references where people were saying disabling SIP made a difference and others that said putting the Obi's IP in the DMZ fixed this issue, so I did both per PP's instructions for my router: http://www.phonepower.com/wiki/D-Link_DIR_655 (http://www.phonepower.com/wiki/D-Link_DIR_655)
So far, so good but I will have to wait to see if this is a permanent fix. Maybe this will help someone.
Quote from: adutchman on April 26, 2014, 01:14:08 PM
Update:
Steps taken last night (4/25/2014)...
1) Rebooted router to make sure SIP ALG setting change took effect.
2) Completely reset OBi100 device by following instructions provided by PhonePower beginning with step # 2 - ReSetting your Obihai. Here is the link they provided http://www.phonepower.com/wiki/Obihai_Lite
Note that I did not press the reset button located on your Obihai phone adapter
3) Restarted OBi100 device.
As of 3:00 pm today (4/26/2014) everything is still working as it should be.
4/27/2014 Update:
I was out shopping this afternoon and called the house phone and my call went straight to voicemail. I called my son's cell phone and asked him to pick up the house phone. He did and told me that there was a dial tone. I told him to hang it up.
I tried calling the house phone again, and again, it went straight to voicemail. This is very frustrating.
When I got home about 1 hour later, I picked up the house phone and got a dial tone. I hung it up and called from my cell. This time the phone rang.
I'm not sure what is going on, but it isn't good. I've never had these kind of issues when I was using GV with the OBi100.
Hello everybody!
I'm having the SAME problem everyone else is having. I have done a factory reset on the OBI 100, reconfigered the OBI device and the PhonePower configuration, and have disabled the sip on my Netgear router. After doing this, I'm still having to reset the Obi constantly. I have 2 weeks left on my 1st month of signing up with PhonePower, and I'm going to cancel unless there's a fix on this issue. It's strange that the first week and a half it worked perfectly with no problems. Thanks to everyone here for all your suggestions. I've tried them all to no avail!
I suggest trying a different service provider. There are plenty to choose from, and it will a) troubleshoot whether it's the provider vs. your setup, and b) help you find a provider that actually provides reliable service. There's just no excuse for it being so flaky.
4/28/2014 Update:
Checked the phone service this morning. I had dial tone and could make outgoing calls.
No incoming service at all. Checked status light on OBi100 and the Phone LED status light was off.
Rebooted device and all was good again.
One of the reasons I went with PhonePower is because they had a local number for my city. However, I am going to cancel the service if there is no fix for this soon.
I am reviewing the plans out there now to replace my GV account for my in-home office. I work from home and need a reliable service as I am on the phone between 500-800 minutes a week. The basic plans won't work for me but I like the PhonePower listed plan for unlimited minutes per month. I was really eying that plan but it looks like there is a service issue all of you are having.
Given this thread, and the number of users, are there any out there that aren't having this difficulty? And are all of the issues with a certain Obi model? I notice the mention of the 100 in several posts, while I am using the 202. If this is a common theme with PhonePower, I might have to see if I can find a comparable service and rate, with a better reliability.
IMO, this is a really good thread to keep updated. Thanks to the OP for bringing it up.
Quote from: CheapSk86 on April 28, 2014, 10:21:45 AM
Given this thread, and the number of users, are there any out there that aren't having this difficulty?
I have PhonePower and it has been rock solid from day one. It has never lost connection and it's been over 1 month. I did configure my Obi thru the web portal but that configuration didn't work after the signup process was complete and I had my SIP credentials. I had to delete my PhonePower configuration and manually add it back in again. Since that day I have had zero problems.
I am really perplexed at the number of people that seem to be having problems. I just don't get it. I have a very old Linksys wrt54g router with stock firmware and an Obi 110 using Comcast as my ISP. I have tried and configured Google Voice, SipGate, Vestalink, Callcentric, IPComms, PhonePower, Anveo, and CallWithUs with absolutely no issues. Well, I did have major latency issues with Vestalink but that had nothing to do with my Obi, router, or ISP.
For those having problems losing their connection with PhonePower have you tried using their softphone?
I would suggest installing PhonePower's softphone on your PC and keep it up and running 24 hours a day if possible. When you lose connection with PP on your Obi are you still connected to PP with your softphone? Also, for those that call in from the outside and their Obi connected phone does not ring, does your PP softphone on your computer ring? Same way for outgoing calls. If you can't call out with your Obi connected phone are you able to call out with the PP softphone?
You should be able to have 4 UAs connected to your PP account at one time. When someone calls me both my Obi connected phone and PP softphone ring simultaneously. Likewise, I can have 2 simultaneous outgoing calls with my PP account: one on my Obi connected phone and one on the PP softphone.
Using the PhonePower softphone may help in troubleshooting and isolating where the problem lies.
Lets pay attention to the comment from PeterFales - he doesn't have a router in his system but is still having the same problem. Doesn't this mean that "SIP ALG" is a red herring?
Seems to me that if the router wasn't handling things right, it wouldn't work fine for days and then disconnect. It sounds more like a problem between the Obihai site and the phonepower site.
Time is counting down for me on whether I cancel the year of phonepower or not, and we haven't really seen an answer for this. Is that because some people don't have the problem, or just don't comment on the forum?
One workaround is simply to cycle power off/on the obihai device fairly often, like every morning, but that's extremely halfassed. Shouldn't have to treat a new VOIP service like a $50 used car.
Are there router brands that don't have this problem, or - more likely - is this an obihai problem that they aren't bothering to fix? GV never did this, nor did VOIP.MS.
Getting right down to it, the PhonePower service seems to just be unreliable with Obi devices, that seems to be the long and the short of it. The SIP ALG advice may just be baffling us with BS while the 30-day refund period runs out. Sorry if I sound cynical, but this is the "preferred provider" Obi directed us to... where are they now?
DJ
TP-Link wired router
Update 4/28/2014:
As another user suggested, I had put my OBi100 device in the DMZ of my router, which is almost like plugging it directly into my cable modem's Ethernet port. This did not resolve the issue either.
It seems that usually after about 1 hour or so, incoming calls go straight to voicemail. I have noticed when this occurs, the Phone LED status light on the OBi100 is off.
OBIHAI's FAQ page states that when the Phone LED is not on, "The service provider configured in the OBi needs to have a valid credential. Make sure you have entered the correct information in you OBiTALK under your Service Provider configuration.
I started a chat with PhonePower tech support and explained the situation to them. Since my device was in the DMZ, they were able to access and check my OBi100 configuration. The support tech said that everything looked okay. He even made a call to my house which I answered and we talked about the situation.
Then the tech enabled a syslog capture on my device and told me that he would periodically call my number until they were able to duplicate the problem.
I received a message a few hours later and they told me that they were able duplicate the issue and captured the data and are forwarding this to their network team for analysis and will report back to me.
Also, last night I opened a support ticket with OBIHAI tech support explaining what has been happening up to this point. They sent a reply this evening with the following message...
"We have upgraded your OBi100 to a newer firmware that should have the registration to PhonePower more stable."
I have verified that the firmware is in fact newer that what is available to download from their web site.
So far my device has been up for over 2 hours since the firmware upgrade and incoming calls have been working.
Quote from: adutchman on April 28, 2014, 06:20:10 PM
"We have upgraded your OBi100 to a newer firmware that should have the registration to PhonePower more stable."
I have verified that the firmware is in fact newer that what is available to download from their web site.
Wow. Could you please post what your firmware version is now?
I too opened a support ticket with Obihai and they replied that they had updated my firmware, we'll see how that goes. I'm glad they are trying stuff. Hasn't dropped connection yet but it hasn't been long.
Not sure if this is the firmware #, but at the Obi config page my device now says SoftwareVersion 1.3.0 (Build: 2858)
I have an Obi100.
fingers crossed...
I'm at Software Version 1.3.0 (Build: 2824)
Anybody got a link to build 2858?
Thanks
Quote from: zorlac on April 29, 2014, 03:50:52 AM
I'm at Software Version 1.3.0 (Build: 2824)
Anybody got a link to build 2858?
I'm at the same build you are. There is no link as of yet. This appears to only be available from Obihai support.
I talked to a rep at PhonePower and he sent me this info. After I set this up according to the instructions, I did a FACTORY reset on the Obi100 and reinstalled the Obi100 plus the PhonePower . It's been over 36 hours and so far all is good. Incoming and outgoing calls are working fine. No having to keep resetting the Obi100. I'm keeping my fingers crossed. This link is for a Netgear router but the PhonePowers sight lists many others to work from. Hope this helps anyone. http://www.phonepower.com/wiki/NetGear_WNR2000v3
By the way, this has been working with the old firmware #2824, not the new firmware #2858.
If you guys could keep us updated with the latest given that some now have new firmware, and others seem to be receiving a positive response from PP, I, as I'm sure others, would appreciate the additional information.
I really like the look of the PP unlimited plan, especially given my monthly usage, but the service reliability has to be there for me.
Piggy backing on that, are any of you using the unlimited plan with them? And do you know if their unlimited plan is truly unlimited, or is it an advertising bait-and-switch like some of the others with maximum of 3000 or 4000 minutes?
Thanks again for all this info you guys are posting.
After countless hours trying to get this to Phone Power to work, I have given up. I simply don't have that much time to spend on it. I cancelled (now less than 24 hours after I signed up). Good luck to the rest of you!
I am guessing that everybody has already tried this?
http://www.phonepower.com/wiki/Obihai_plans (http://www.phonepower.com/wiki/Obihai_plans)
Just one more thing I realized that might have been causing the problem with PhonePower..The IP address of my router was DIFFERENT than what was being stored on the Obi100 by 1 number. It had it listed as 192.168.0.1. in the Obi100, whereas it should have been 192.168.1.1. I found this out by mistake by trying to log in on my web browser with the 192.168.0.1. number and it wouldn't connect to my Netgear router. After digging around on the web I found that my router was ACTUALLY the 192.168.1.1. number. After changing this on my router and in the Obi100, and doing what I posted earlier, I've had no problems with having to reset the Obi100 all the time. Just wanted to share this 1 more thing that might be causing people their problem with PhonePower.
About one week ago, whenever I was dialing out I heard the "No Service Configured error, Please login to configure your device." But, when I logged into my Obitalk account I find that the PhonePower at SP1 is "registered", which means it does not need to be configured. I was able to speak to a tech from PhonePower who used a remote service to take over operation of my computer and accessed my router and made some changes, the main one being that he disabled the SIP ALG in my router and, since that time, I have not had any problems with the PhonePower through my Obihai. If problems develop, I will update this comment.
I suggest that users, before cancelling, contact PhonePower and let them try to work out a solution to your problems. I am glad that I signed up with a service that allows me to actually speak to a tech agent who can even use remote to access my router.
I also have encountered this problem. I asked Obi to update the firmware on my OBI100 and they have.
But also, I found this page for setting up the Obi with your router. It involves selecting protocols for various ports.
http://www.phonepower.com/wiki/Obihai_set_up
My router (switch really) is a TP-Link, but they have a page that lists all sorts of brands:
http://www.phonepower.com/wiki/Customer_Provided_Routers
Re disabling SIP ALG. I contacted TP-Link and they told me it doesn't support the SIP ALG anyway. In other words, this could not have been the cause of the problem in my case.
We'll see if the firmware and configuring the router helps.
I still have GV as SP1 but told my OBi to use SP2 (Phone Power) for outgoing calls.
I was wondering if others who've encountered the problem also still have GV on SP1?
Thanks,
Bob
Same problems... Just signed up this weekend for PhonePower in anticipation of loss of google. I have never gotten past "service not configured" on the obi dashboard. I will try some of these fixes and report back as well.
I completely eleminated GV from my Obi100 and have PhonePower as my SP1. I just forward my number from GV to my new phone number from PP.
Quote from: Taoman on April 28, 2014, 07:01:07 PM
Quote from: adutchman on April 28, 2014, 06:20:10 PM
"We have upgraded your OBi100 to a newer firmware that should have the registration to PhonePower more stable."
I have verified that the firmware is in fact newer that what is available to download from their web site.
Wow. Could you please post what your firmware version is now?
This is what I have:
ModelName OBi100 help
HardwareVersion 3.4 help
SoftwareVersion 1.3.0 (Build: 2858)
Quote from: zorlac on April 29, 2014, 03:50:52 AM
I'm at Software Version 1.3.0 (Build: 2824)
Anybody got a link to build 2858?
Thanks
I don't think that have made this public yet. Create a ticket with Obihai support, let them know that you switched from GV to PhonePower and are having problems with the service and you would like the firmware update.
Quote from: CheapSk86 on April 29, 2014, 10:04:35 AM
If you guys could keep us updated with the latest given that some now have new firmware, and others seem to be receiving a positive response from PP, I, as I'm sure others, would appreciate the additional information.
I really like the look of the PP unlimited plan, especially given my monthly usage, but the service reliability has to be there for me.
Piggy backing on that, are any of you using the unlimited plan with them? And do you know if their unlimited plan is truly unlimited, or is it an advertising bait-and-switch like some of the others with maximum of 3000 or 4000 minutes?
Thanks again for all this info you guys are posting.
After making some phone calls, I must say, the audio quality of the calls with Phonepower is really good. That coupled with having a local phone number for my area (couldn't get that with MagicJack or Google Voice), it is worth the $35 per year to have a phone number for incoming calls.
Quote from: Bob_in_MA on April 29, 2014, 03:44:44 PM
I also have encountered this problem. I asked Obi to update the firmware on my OBI100 and they have.
But also, I found this page for setting up the Obi with your router. It involves selecting protocols for various ports.
http://www.phonepower.com/wiki/Obihai_set_up
My router (switch really) is a TP-Link, but they have a page that lists all sorts of brands:
http://www.phonepower.com/wiki/Customer_Provided_Routers
Re disabling SIP ALG. I contacted TP-Link and they told me it doesn't support the SIP ALG anyway. In other words, this could not have been the cause of the problem in my case.
We'll see if the firmware and configuring the router helps.
I still have GV as SP1 but told my OBi to use SP2 (Phone Power) for outgoing calls.
I was wondering if others who've encountered the problem also still have GV on SP1?
Thanks,
Bob
Thanks for posting these links Bob! I have a Netgear wireless router. My specific model is not listed, but looking at all of the ones that are similar, they all say that the OBi device needs to be put in the DMZ.
I guess I'm going to put my OBi100 device back in the DMZ, after all, it was working that way once I got the updated firmware.
People should not be so quick to give up on PhonePower and OBi devices. I think they will work out the kinks and things will be just fine.
Quote from: adutchman on April 29, 2014, 07:29:39 PM
Quote from: zorlac on April 29, 2014, 03:50:52 AM
I'm at Software Version 1.3.0 (Build: 2824)
Anybody got a link to build 2858?
Thanks
I don't think that have made this public yet. Create a ticket with Obihai support, let them know that you switched from GV to PhonePower and are having problems with the service and you would like the firmware update.
Thanks but I'm not that desperate, I can wait until they release the 2858 firmware as a downloadable file on their website.
Let the early adopters work out the kinks. ;D
mail from phone power:
If you notice that you have to reboot to restore the service on the obi 100, send a email to obi support , support@obihai.com , provide them the 9 digit obi number ,and advised that you need to reboot or re sync to restore the phone service .
obi support will push a firmware update , this has resolved the problem . If you are having difficulties adding the device back to obi talk , contact obi support on that issue.
I wonder if this FW update would cure any of the Anveo heartaches?
For what's it's worth, I haven't done the firmware update and all has been good for the last 3 days. I'm sure it couldn't hurt if your still having problems, but what I've read on this forum, sometimes the firmware updates cause some people problems until they work out the kinks.
4/30/2014 Update:
It has been 2 full days since firmware upgrade by OBi Support and all is still good with phone power service. I'm able to make and receive calls okay. Even the Phone LED has been green on the device.
Follow-up from my previous post...
I ended up deleting Google Voice and PhonePower from my Obi.
Hard restore of Obi (paperclip pressing button in on bottom of device for 15sec--> button flashes red)
Re-entered PhonePower in SP1
Sent Re-sync from PhonePower website.
PhonePower now "registered" and I have had no problems since. Call quality is good.
I did also successfully use my GV phone number as a spoof in my PhonePower set-up and added the new PhonePower number to my GV acct-- all seems to be working well.
Reporting back.
Turning off "SIP passthrough" on my Asus router didn't fix the problem. It took a couple of days, but I lost the second green light on the OBI and was back to "service not configured". I've contacted OBI support and will try the new firmware.
Keep us posted. It sounds like the firmware may be helping. If this is true and the service is starting to look good, the PP plan may be something for me to look at.
I have been trying to compare what you get for cost. It looks like PhonePower has every bit of service Anveo has, or more, for a better cost. Can you guys who have chosen it comment to that? Aside from these initial hiccups?
And are you all on 100's or do any of you have 202s?
I have made the switch to PhonePower as well... I also have intermittent not configured issues.
I have enabled syslog on the Obi100; immediately following a reboot the first REGISTER messages returns a 401 Unauthorized response from PhonePower yet my calls go through... wait a couple minutes or hours and the phone no longer works.
The current solution? Reboot Obi100. LAME!
Syslogd is listening to port# 514:
<145> Reboot is scheduled in 1 seconds
<0> Reboot checking.....<0> Final Cleanup before reboot....
<144> Goodbye! Reboot Now. (reason: 4)
<6> ==== Networking is ready ====
<0> IP Address= 192.168.200.XXX <0> Gateway = 192.168.200.1 <0> Netmask = 255.255.255.0 <3> SYSTEM REBOOTED (Reason: 4, lifecycle: 1377)
<173> ZT: CustomID 1
<0> SLIC_init ...<0> Reset SLIC...<150> Setup Provisioning for system start! 1500
<0> SLIC & DAA is initialized<6> Start Main Service Now<7> Voice Main
<7> [SLIC] DAA command with wrong id: 0, 2, 0, 0, 0, 0<7> [CPT] --- FXS s/w tone generator (ringback) ---
<7> BASESSL:load cert:5
<7> BASESSL:Load certificate ok
<7> REG:Create 0
<7> [SLIC]:Slic#0 ON HOOK
<7> sendto d0400806:5060(597)
REGISTER sip:sip.phonepower.com:5060 SIP/2.0
Call-ID: 49250263@192.168.200.XXX
Content-Length: 0
CSeq: 15767 REGISTER
From: "Me" <sip:XXXXXXXXXX@sip.phonepower.com>;tag=SP14bae5f535468a2d9
Max-Forwards: 70
To: "Me" <sip:XXXXXXXXXX@sip.phonepower.com>
Via: SIP/2.0/UDP 192.168.200.XXX:5060;branch=z9hG4bK-7862a1cf;rport
User-Agent: OBIHAI/OBi100-1.3.0.2824
Contact: "Me" <sip:XXXXXXXXXX@192.168.200.XXX:5060>;expires=14400;+sip.instance="<urn:uuid:00000000-0000-0000-0000-9cadef10fe5f>"
Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,OPTIONS,REFER,UPDATE
Supported: replaces
<7> RxFrom:d0400806:5060
SIP/2.0 401 Unauthorized
Call-ID: 49250263@192.168.200.XXX
CSeq: 15767 REGISTER
From: "Me" <sip:XXXXXXXXXX@sip.phonepower.com>;tag=SP14bae5f535468a2d9
To: "Me" <sip:XXXXXXXXXX@sip.phonepower.com>;tag=192.168.22.50+1+6e571c+4390576c
Via: SIP/2.0/UDP 192.168.200.XXX:5060;received=98.150.XXX.XXX;branch=z9hG4bK-7862a1cf;rport=5060;alias
WWW-Authenticate: Digest realm="sip.phonepower.com",nonce="247ae489b0c6",stale=false,algorithm=MD5,qop="auth"
Server: DC-SIP/2.0
Organization: Phone Power
Content-Length: 0
Also here is a snippet of what the logs show when you CANNOT MAKE OR RECEIVE INCOMING CALLS through PhonePower. I get the SIP/2.0 403 Forbidden error. Again the solution is reboot Obi100. LAME!
<7> [SLIC]:Slic#0 OFF HOOK
<7> [CPT] --- FXS h/w tone generator (stutter)---
<7> [DSP]: ---- H/W DTMF ON (level:1) : 8 @ 273580 ms----<7> [DSP]: ---- H/W DTMF OFF @ 273670 ms ----
<7> [DSP]: ---- H/W DTMF ON (level:1) : 5 @ 273800 ms----<7> [DSP]: ---- H/W DTMF OFF @ 273870 ms ----
<7> [DSP]: ---- H/W DTMF ON (level:1) : 5 @ 274000 ms----<7> [DSP]: ---- H/W DTMF OFF @ 274050 ms ----
<7> [DSP]: ---- H/W DTMF ON (level:1) : 7 @ 274180 ms----<7> [DSP]: ---- H/W DTMF OFF @ 274250 ms ----
<7> [DSP]: ---- H/W DTMF ON (level:1) : 6 @ 274380 ms----<7> [DSP]: ---- H/W DTMF OFF @ 274450 ms ----
<7> [DSP]: ---- H/W DTMF ON (level:1) : 7 @ 274590 ms----<7> [DSP]: ---- H/W DTMF OFF @ 274660 ms ----
<7> [DSP]: ---- H/W DTMF ON (level:1) : 1 @ 274790 ms----<7> [DSP]: ---- H/W DTMF OFF @ 274860 ms ----
<7> [DSP]: ---- H/W DTMF ON (level:1) : 0 @ 274990 ms----<7> [DSP]: ---- H/W DTMF OFF @ 275060 ms ----
<7> [DSP]: ---- H/W DTMF ON (level:1) : 5 @ 275190 ms----<7> [DSP]: ---- H/W DTMF OFF @ 275260 ms ----
<7> [DSP]: ---- H/W DTMF ON (level:1) : 1 @ 275390 ms----<7> [DSP]: ---- H/W DTMF OFF @ 275460 ms ----
<7> sendto d0400806:5060(962)
INVITE sip:18557671051@sip.phonepower.com:5060 SIP/2.0
Call-ID: 5625b6d4@192.168.200.125
Content-Length: 311
CSeq: 8001 INVITE
From: "Me" <sip:XXXXXXXXXX@sip.phonepower.com>;tag=SP14bae5f535468a2d9
Max-Forwards: 70
To: <sip:18557671051@sip.phonepower.com>
Via: SIP/2.0/UDP 192.168.200.125:5060;branch=z9hG4bK-308f4669;rport
User-Agent: OBIHAI/OBi100-1.3.0.2824
Contact: "Me" <sip:XXXXXXXXXX@98.150.XXX.XXX:1045>
Expires: 60
Supported: replaces
Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,OPTIONS,REFER,UPDATE
Remote-Party-ID: "Me" <sip:XXXXXXXXXX@sip.phonepower.com>;party=calling;privacy=off
Content-Type: application/sdp
v=0
o=- 28383 1 IN IP4 98.150.XXX.XXX
s=-
c=IN IP4 98.150.XXX.XXX
t=0 0
m=audio 16604 RTP/AVP 0 8 18 104 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=rtpmap:104 G726-32/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
a=ptime:20
a=xg726bitorder:big-endian
<7> RxFrom:d0400806:5060
SIP/2.0 100 Trying
Call-ID: 5625b6d4@192.168.200.125
CSeq: 8001 INVITE
From: "Me" <sip:XXXXXXXXXX@sip.phonepower.com>;tag=SP14bae5f535468a2d9
To: <sip:18557671051@sip.phonepower.com>
Via: SIP/2.0/UDP 192.168.200.125:5060;received=98.150.XXX.XXX;branch=z9hG4bK-308f4669;rport=5060
<7> RxFrom:d0400806:5060
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 192.168.200.125:5060;received=98.150.XXX.XXX;branch=z9hG4bK-308f4669;rport=5060
Call-ID: 5625b6d4@192.168.200.125
CSeq: 8001 INVITE
From: "Me" <sip:XXXXXXXXXX@sip.phonepower.com>;tag=SP14bae5f535468a2d9
To: <sip:18557671051@sip.phonepower.com>;tag=aprqngfrt-88757g300o724
<7> sendto d0400806:5060(397)
ACK sip:18557671051@sip.phonepower.com:5060 SIP/2.0
Call-ID: 5625b6d4@192.168.200.125
Content-Length: 0
CSeq: 8001 ACK
From: "Me" <sip:XXXXXXXXXX@sip.phonepower.com>;tag=SP14bae5f535468a2d9
Max-Forwards: 70
To: <sip:18557671051@sip.phonepower.com>;tag=aprqngfrt-88757g300o724
Via: SIP/2.0/UDP 192.168.200.125:5060;branch=z9hG4bK-308f4669;rport
User-Agent: OBIHAI/OBi100-1.3.0.2824
<7> RTP:Del Channel
<7> [CPT] --- FXS h/w tone generator (ringback)---
<7> [CPT] --- FXS s/w tone generator (sit_1) ---
<7> [CPT] --- FXS s/w tone generator (sit_1) ---
<7> [SLIC]:Slic#0 ONHOOK
Quote from: MsCint3 on April 26, 2014, 07:09:23 PM
I, too, had these same problems. First off, I chose Phonepower voip. I was knocked off of the system twice. In both cases I had noticed that my config info was missing. The 1st time i manually replaced the info and went to the phone power site to sync the devices. The next morning no service. The second time I configured through Obitalk approved service providers section. I tabbed on the phone power followed the promps and placed phonepower in the sp1 and left googlevoice in the sp2 section. After the configs were done, I returned to the phonepower site to sync the devices. Earlier I had tried to remove GV to replace with CircleNet voip in sp2. It messed up everything so I reconfig to GV. Now, I have been on for 2 days with no probs.
I hope that this advice works for you as well it has for me.
Good Luck!!
I have been on for 1 week now without any problems.
MsCint: are you using a 100 as well or a different model Obi?
Obi 100
Just an update, since we got the new firmware build from Obi support, haven't had the problem. Maybe we're just lucky but I'm starting to think maybe they fixed it. Fingers crossed... and I hope it keeps working after we pass the 30-day no-annual-refund threshold for PhonePower.
I must say, decent call quality on phonepower. There is a bit of a lag, but we're in Hawaii.
Just another update...
As I reported, I had gotten the firmware update and also did the port forwarding Phone Power recommends (http://www.phonepower.com/wiki/Customer_Provided_Routers) last week.
So far, so good. I get periodic outages from my cable provider, usually less than a minute, sometimes 5-10 minutes. It seemed to me that before, whenever one of these outages occurred the Obi wouldn't reconnect to PhonePower until I did a manual reboot.
But I just had one of these outages and afterward it reconnected without me doing anything.
So seems OK (knock on wood....)
Good luck to the rest of you!
Bob
One other point....
We're getting much less of a delay with PhonePower than with GV. It had been really pronounced when my wife called her family in Maine, like a very bad cellphone connection.
But no it seems hardly noticeable. Definitely worth the $35/year. ;-)
Bob
I have an Obi 100, and, after reading this entire thread, I checked my Obi Dashboard, and noticed
an alert icon, next to the gearbox icon settings.
The alert was to upgrade firmware, ( does it automatically, if you follow through with the message )
I did so, and it upgraded my firmware to 1.3.0 build 2824 . It took about 90 seconds.
Figured it's probably better to upgrade the Obi 100 firmware, first, before going to Phone Power.
I'm still on GV, but, plan to move to Phone Power within next couple of days.
Quote from: rodan on May 04, 2014, 10:42:16 AM
I have an Obi 100, and, after reading this entire thread, I checked my Obi Dashboard, and noticed
an alert icon, next to the gearbox icon settings.
The alert was to upgrade firmware, ( does it automatically, if you follow through with the message )
I did so, and it upgraded my firmware to 1.3.0 build 2824 . It took about 90 seconds.
Figured it's probably better to upgrade the Obi 100 firmware, first, before going to Phone Power.
I'm still on GV, but, plan to move to Phone Power within next couple of days.
Build 2824 has been available for months. That one isn't the 'silver bullet' for intermittent PhonePower.
Guess not everyone moving from GV to PP on an Obi100 is having this intermittent " not configured " problem.
The latest, standard, firmware update is 1.3.0 build 2824.
I emailed Obi support to see if I can get the latest firmware, with fix for using PP.
I had this same problem after switching to Phonepower, but whenever I got the "service not configured error" I made a test using the Phonepower softphone on my computer and both outbound and inbound calls worked fine. I just recently disconnected my local landline and migrated from GV to Phonepower on sp1, so I thought the Obi was probably not routing the calls correctly. What fixed it for me was checking the "primary line for outgoing calls" box on the portal's sp1 configuration page because it was unchecked.
It may not help others with this problem but if you configured the Phonepower service on sp2 and disconnected GV from sp1, then the outbound call route may still say to use sp1 unless you check the sp2 box as the primary line. Sounds very similar to my situation.
I suggest using the Phonepower softphone to test the service because at least it will help check if the problem is external to the Obi (Phonepower or router SIP configuration issue as was suggested). I didn't have to make any changes to my ASUS router. Hope this helps a little.
Quote from: flanda on May 05, 2014, 01:05:22 PM
What fixed it for me was checking the "primary line for outgoing calls" box on the portal's sp1 configuration page because it was unchecked.
I didn't have to make any changes to my ASUS router. Hope this helps a little.
I had the "primary line for outgoing calls" switched to PhonePower from the day I signed up. Changes to my Asus router have had no effect. On the other hand since switching to the new firmware, I've been stable for three days.
Is it 2858 of the OBi 100 firmware that is believed to help with the problem?
Is there a similar fix for the OBi 200 series? (Does anyone who was experiencing the problem on the 200 series think that a firmware update helped? If so, what were the "before" and "after" build numbers?) For the record, I was using " 3.0.1 (Build: 4330)" when I experienced the intermittent "not configured" errors. I've since upgraded to 4350, but I don't have PhonePower anymore, so I can't test it.
5/8/2014 Update:
It has been 10 days since the firmware upgrade by OBi Support and all is still good with phone power service. I am still able to make and receive calls okay. The Phone LED has been green on the device this whole time as well.
My OBi100 device status page shows an uptime of 7 Days 23:45:35.
I believe that it was the firmware upgrade and following the router configuration instructions from PhonePower that led to the successful operation of both my OBi100 and PhonePower service.
This will probably be my last post on this thread. Good luck to all and thanks for everyone's suggestions and help.
I've now been up nearly six days since the installation of the new firmware by OBI support. It would appear this has fixed the problem I reported at the head of the thread. Kudos to OBI.
This "no service configured error" was trying me batty for weeks. I found this thread, contacted support and got the new firmware (2858). It's only been a few days, so it's too early to judge, but so far so good. Will report back in a week or two whether it's still working.
Thanks to all for reporting the problem and potential solution.
The OBi110-1-3-0-2858 build was made to specially address the issue of "phonepower service not configured" error.
I just wanted to supply my experience so far:
I did the switch last Tuesday to PhonePower from Google Voice and to make the change I just went through the ASP link from my dashboard. Once I selected the SP slot and completed the sign up with Phone Power, my Obi 202 was configured with the correct information.
I do mainly toll-free calling from it for conference lines, but have done a few land-line calls, both local and 1/2 the country away. I haven't had any drop connection or issues with PhonePower staying registered or configured. I'm running FW 4350 on my 202 and it's been solid since switching. I was really worried with so many people experiencing issues, but so far it's been solid.
I will be watching it for the next 2.5 weeks to see if anything changes or any issues occur and I will post back follow-up on it, but so far, so good.
Quote from: Bob_in_MA on May 03, 2014, 09:26:49 AM
One other point....
We're getting much less of a delay with PhonePower than with GV. It had been really pronounced when my wife called her family in Maine, like a very bad cellphone connection.
But no it seems hardly noticeable. Definitely worth the $35/year. ;-)
Bob
PP east coast server is in Boston so you are lucky. For those of us in the middle of the country (STL), we are on the Los Angeles server. There is nothing near the center of the country. :-(
I too was getting intermittent configuration error recording when initiating calls after switching from GV to Phonepower that temporarily cleared after rebooting my OBI202. Note that I have OBITalk Provisionig disabled so I could change the convoluted dialing plan the OBI/PP setup wizard gave me. I also wanted to make some other changes that should not have affected service. It seemed like every morning I would have to reboot the Obi202 to temporarily restore service again. After much researching, I saw a post where one individual solved the intermittent service by setting up a static IP address for the OBI WAN. I did this and for 3 days now, the problem has been solved. Note that on the same WD N900 router, I have a VOIPo account on a different OBI202 and it has (and is) been working for over a year using DHCP. I don't know why this work around has solved the problem but if it fails, I'll report back.
Just for a follow up: I signed up about 3 weeks ago and have been using PP since. I am on the phone every day for a minimum of 20 minutes, though mostly toll-free numbers. So far I have not had any intermittent connection issues, service or call quality issues, or drops.
I am using an OBI202 with the latest released firmware, the standard connection setup when you sign up for PhonePower through the Obi dashboard, and am using PhonePower currently for both toll-free and standard calls.
I posted a small review with additional information and feedback in another thread:http://www.obitalk.com/forum/index.php?topic=8197.0 (http://www.obitalk.com/forum/index.php?topic=8197.0) for anyone who cares about a little more.
Based on the experience so far, I will be sticking with PhonePower for my needs.
Quote from: PeteMoss on June 01, 2014, 10:30:17 AM
I too was getting intermittent configuration error recording when initiating calls after switching from GV to Phonepower that temporarily cleared after rebooting my OBI202. Note that I have OBITalk Provisionig disabled so I could change the convoluted dialing plan the OBI/PP setup wizard gave me. I also wanted to make some other changes that should not have affected service. It seemed like every morning I would have to reboot the Obi202 to temporarily restore service again. After much researching, I saw a post where one individual solved the intermittent service by setting up a static IP address for the OBI WAN. I did this and for 3 days now, the problem has been solved. Note that on the same WD N900 router, I have a VOIPo account on a different OBI202 and it has (and is) been working for over a year using DHCP. I don't know why this work around has solved the problem but if it fails, I'll report back.
After 3 days the problem surfaced again requiring another reboot. I have made some other changes and will advise.