Phone Power pergatory
jlynnwatts:
I spent some quality time with tech support today at Phone Power. Since it did not meet my needs, I had just cancelled my Vestalink service and was having trouble getting my Obi to accept the Phone Power software setup. In order to get the Obi100 to configure correctly we had to do a factory reset. I used a modified sequence similar to the one that "BHochstrasser" mentioned on this forum. It took care of all the residual programming that Vestalink had apparently left on my Obi. Here is what we did:
Getting rid of any remnants of the previous provider:
1. De-couple service provider from SIP1 and SIP2 on the Obi100.
2. Delete the Obi100 from ObiTalk.
3. Using a paper clip, hold the reset for 15-20 seconds until I got a fast blinking green
light and finally a red light for the factory reset.
4. From ObiTalk, Add New Device.
5. Enter the "**5-xxxx" code from my phone handset to register the factory reset device
with ObiTalk.
6. Finally, have Phone Power set up the Obi as the new provider.
After the reset and Phone Power provider install everything seems to work very well indeed!
jwatts
Taoman:
It is saying the period of time before your Obi should "register" again with Phone Power is 240 seconds. Your setting is probably less than that but it isn't hurting anything. Mine is currently set for 180 seconds. Setting the registration interval higher uses less data.
This shouldn't have anything to do with your relative not being able to call you. Log into the PP web portal and look at your Call log/usage. Do you see the phone call from your relative listed there?
Go back to the SIP Credentials page under Modify Services. What do you see under Registered User Agents?
When you go into the Obitalk Dashboard does it say "registered" under Status? I can tell you how to set your registration interval to 240 seconds but it would mean going into Expert Configuration. I realize it is intimidating to go into Expert Configuration. But just about everything is intimidating until you've done it a few times. Right? ;) You can't do any potential damage unless you uncheck the ObiTALK settings box, change the setting, and then click on the Submit button at the bottom of the page. And even if you did mess something up you now know how to start all over......which should take you less than 5 minutes. I would recommend you become comfortable with the procedure of starting over again and reconfiguring everything. Do it for drill. It doesn't hurt anything and you will then become comfortable enough to start fine tuning your configuration (like registration interval). If something gets screwed up....big deal. Just start over again and you'll be back up and running in 5 minutes. Understand that your subscription with Phone Power is heavily discounted and a BYOD (bring your own device) service which means you are responsible for the correct functioning of your OBi, not Phone Power. Tech support may try and help you but you can't count on them as you apparently found out.
Just my opinion. Others may disagree.
lburgguy:
Thanks Taoman. It's not that I'm intimidated really, I enjoy a challenge, I was just afraid I had messed something up previously in the Expert Mode but I suppose doing the factory reset resets it.
Yeah, I put a lot of effort into choosing my number so my relative could call toll free. I was hoping it was just a glitch that they couldn't call me when I could call my Obi with my cell phone. I looked up the exchange again and it should be local. IDK, I ask them to try again today.
I do see the Obi registered in the SIP page at PP. I understand that BYOD means no real tech support and I'm not one to run and seek help from anyone usually but it's funny that they didn't know how to fix the issue even after multiple calls and a few hours trying to diagnose the situation. I guess their autoconfiguation simply doesn't work.
Thanks again for everyone helping me get this working. I sure hope this is a better experience than Vestalink. BTW, I could tell IMMEDIATELY that the call quality was better with PP! It was crystal clear when I called my relative unlike Vestalink.
Navigation
[0] Message Index
[*] Previous page