Switched from GV to PhonePower - intermittent "not configured"

[adutchman]

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.

[adutchman]

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.

[adutchman]

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.

[zorlac]

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. 

[Dale]

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.

[zorlac]

I wonder if this FW update would cure any of the Anveo heartaches?

[fugley4651]

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.

[adutchman]

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.

[Drewsa]

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.

[EdWilliams]

   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.

[CheapSk86]

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?

[jlkjslksdjflksdjf]

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!

Code Select Expand


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!

Code Select Expand


<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


[MsCint3]

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.

[CheapSk86]

MsCint: are you using a 100 as well or a different model Obi?

[MsCint3]

Obi 100

[kealolo]

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.

[Bob_in_MA]

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

[Bob_in_MA]

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

[rodan]

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.

[drgeoff]

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.