Firmware 3.2.2 Build 5898) breaks PhonePower. Need to revert to 3.2.2 build 5757
BenE:
I didn't have to change from Phone Power to another ITSP. Why that was mentioned as a fix is why that is confusing to me, as we want to get Phone Power to work, as it did on older firmware or on older devices.
Anyway, I did have to go thorough the template provided by Phone Power to be able to use SIP Credentials, as Phone Power no longer can provision Obi devices directly. I could not get back to the firmware that did work previously due to the mismatch. All I can guess is that Phone Power might have fixed something on their end that will only register the OBI200 as a single device, or my internet outage fixed something that allows the device to properly register.
KevKan:
BenE, I am glad to hear your device mysteriously started working properly and hope it continues to be trouble free.
Being a most satisfied PhonePower customer for over four years, I too wanted them to the fix the problem.
They emphatically maintained this was not their problem, it was Obi Hai's. After hearing this for four weeks,
I started searching to see if this problem was being reported with other ITSP’s. Finding none, it appeared this
problem was exclusive with PhonePower. Based on this, I felt it was time to try a different ITSP and moved
two SIP configured devices plagued with the problem. Two other Obi Hai devices I have with PhonePower,
configured on ObiTalk when PhonePower was an approved supplier, are rock solid.
Since I am unaware of Obi Hai revising their firmware, and you say it is working, it now appears PhonePower must have accepted responsibility for their problem and proceeded to fix their software. I hope this to be true.
Please keep us posted on how your device is functioning.
Mystery Soved!! Just spoke with PhonePower tech support and they confirmed they found their problem (didn't say when) and have corrected it. It sure would have been nice if they had informed their customers.
madhouse:
Does anyone have a working sip setup with PhonePower? I am up on a Grandstream but would like to get my OBI 202 back. The OBI works to some degree but I cant get the *21 to work for voicemail. It works on the Grandstream strange enough. I can setup the ID and password OK but not sure about the 100 or so other parameters! I was able to revert build back to 3-2-2 build 5859. Thanks
etta:
Hi KevKan, may I ask what new ITSP did you choose?
Quote from: KevKan on August 13, 2018, 08:09:03 am
For clarification of my post, ITSP is the abbreviation for "Internet Telephone Service Provider" . A few of them are: Anveo, PhonePower, VOIP.MS, and Callcentric.
jman19:
Quote from: KevKan on August 16, 2018, 11:23:21 am
BenE, I am glad to hear your device mysteriously started working properly and hope it continues to be trouble free.
Being a most satisfied PhonePower customer for over four years, I too wanted them to the fix the problem.
They emphatically maintained this was not their problem, it was Obi Hai's. After hearing this for four weeks,
I started searching to see if this problem was being reported with other ITSP’s. Finding none, it appeared this
problem was exclusive with PhonePower. Based on this, I felt it was time to try a different ITSP and moved
two SIP configured devices plagued with the problem. Two other Obi Hai devices I have with PhonePower,
configured on ObiTalk when PhonePower was an approved supplier, are rock solid.
Since I am unaware of Obi Hai revising their firmware, and you say it is working, it now appears PhonePower must have accepted responsibility for their problem and proceeded to fix their software. I hope this to be true.
Please keep us posted on how your device is functioning.
Mystery Soved!! Just spoke with PhonePower tech support and they confirmed they found their problem (didn't say when) and have corrected it. It sure would have been nice if they had informed their customers.
Hi all,
New to this forum, and I hope that we can share some info that will help out.
I just ported a landline to PhonePower, after having an account with them for over a year and waiting for the right opportunity. I had an OBi200 that (unfortunately) had a lot of analog line noise with hardwired phones, so I could not port my number until I switched to an OBi202 which has much better analog performance. Anyway, I struggled this afternoon with a lot of the same issues as others are having (device unregistering and registering in the middle of phone calls, etc.) I called PP support and was told that the firmware version was causing the problem. I disabled automatic firmware updates and tried to revert to earlier FW versions without success.
I also tried signing up with CallCentric and entering this ITSP as SP2 to compare registration stability. It's too soon to know for sure, but testing is underway. So far, PhonePower has dropped off several times in the last hour, while CallCentric remains registered.
I also tried reconfiguring my OBi200 for the PP service, and noticed that both devices were showing "unregistered" at the same time. Then they both showed "Registered" a short while later. It seems there is some possible issue on the PP registration server...
CallCentric recommends trying their service before committing to a phone number port, so we will see how that works out.
Bottom line is that the support tech I spoke to said that there was still a problem and that Obihai/Polycom needed to fix it. He did mention that this had been a problem since about May, which was consistent with other postings in this forum. So, I would not be too ready to say that the problem is "fixed" - maybe Polycom is working on a FW update.
Some more info: PP tech support has been very helpful. They seem as frustrated as anyone else that this problem is still not solved. Rolling back to the last version of FW that can be loaded (5859EX) solved the problem for me, although there was a lot of parameters to change from the "default" values (mostly using port 12060 instead of 5060 and entering sip.phonepower.com for practically every server address). Obihai tech support pushed the latest FW back onto the device and broke it again (thus confirming that the 5898EX firmware is causing the problem), so I reverted again to 5859EX and it's working again. It's too soon to tell if this will continue to be an issue.
It does not seem to matter if I have the port forwarding on my network firewall enabled or disabled, so I'll keep it disabled.
I have a working configuration with the OBi202, as long as the FW stays at 5859EX or Obihai releases a newer version that fixes this once and for all.
Navigation
[0] Message Index
[#] Next page
[*] Previous page