Obi202 won't stay registered with Phonepower
EdWilliams:
Quote from: ferrarifire on December 10, 2017, 03:22:05 pm
Just want to post this in case someone still has issues with configuring PhonePower service.
Some background: I have started working on replacing my Obi100 with Obi200 and ran into issues to make SP1 PhonePower able to make/receive calls. Using the Obitalk's named service provider (PhonePower) in the configuration did not work (Google voice for SP2 worked).
Either I could get PhonePower to work outside of Obitalk.com (by following the configuration in above messages) or only get Google Voice through Obitalk.com configuration and not PhonePower.
Below is what finally what I did to make it work.
--> Reset the Obi200 to Factory Default (Obi200 device access >> System Management >> Device Update >> Restore Configuration)
--> Login to Obitalk.com and add the device (Keep the network and phone connected to Obi200, and enter the **5 xxxx code when asked)
--> (Optional) Configure the SP2 first for Google Voice (this is my preference to have Google as secondary line). This may take couple of minutes. Check the status in Obi Dashboard on Obitalk.com and ensure the status as 'Connected' for SP2
--> Click SP1 and proceed to configure a Generic Service Provider using the following details:
Service Provider Proxy Server = sip.phonepower.com
Service Provider Proxy Server Port = 0Outbound Proxy Server = sip.phonepower.comOutbound Proxy Server Port = 0Username = UserName from SIP credentialsPassword = Password from SIP credentailsURI = 10digitNumber@sip.phonepower.com
I tried ferrarifire's method this AM - with one addition, setting the registration period to 3600 in the expert settings of Obitalk. There was a few minutes of confusing results where inbound calls would sometimes route to the voice mailbox. However since then the Obi202 has remained registered and as far as I can tell functional. Yeah!
I also checked AccessFromWAN under System Management|Device Admin in the Obitalk Expert settings. This allowed me to log into the Obi and save the configuration.
PhonePower had me port forward a bunch of ports to the Obi202:
4200 TCP
• 5000 - 5080 UDP
• 10000 - 11000 UDP
• 12060 - 12080 UDP
• 16384 - 16472 UDP
• 16600 - 16700 UDP
The only one I have so far seen in use is 10000 UDP when Obitalk updates the Obi202's configuration. I have not yet turned any of these off.
EdWilliams:
It's been several weeks and the Obi202 has been working perfectly using ferrarifire's technique. It's much simpler than what Phonepower tech support is suggesting and it works - at least for me.
NickyG:
Quote from: EdWilliams on June 08, 2018, 02:42:28 pm
... Phonepower support gave the following instructions - which I executed. However, will no occasionally register, but will not stay registered...
@EdWilliams: THANK YOU!! I followed your detailed instructions tonight, thanks so much for those and the screenshots -- and VOILA! My Obi202 shows registered with Phonepower on SP2 and seems stable. Tried multiple times with the auto-config and with ferrarefire's solution with no success but yours worked. In the midst of my frustrations I opened an account with Anveo and requested a (free) port of my Phonepower number. That hasn't come through yet but it doesn't matter as this line is only for calling out. The Anveo registration was a beautiful thing - in minutes I had a new phone number assigned and set up on my Obi (SP1); so I would recommend a switch from Phonepower to anyone who is fed up with this config issue. Basic plan is $40/year for 333 minutes and texts per month.
Navigation
[0] Message Index
[*] Previous page