Obihai is deleting unwanted topics
VaHam:
Quote from: RonR on May 11, 2012, 07:15:37 pm
Quote from: ShermanObi on May 11, 2012, 07:05:54 pm
@RonR - Yes. When a user adds their device to the OBiTALK portal, dialing **5 allows OBiTALK to associate the OBi with the correct user's account.
So, even with:
System Management -> Auto Provisioning -> Auto Firmware Update -> Method : Disabled
System Management -> Auto Provisioning -> ITSP Provisioning -> Method : Disabled
System Management -> Auto Provisioning -> OBiTALK Provisioning -> Method : Disabled
Voice Services -> OBiTALK Service -> Enable : (unchecked)
The OBiTALK Web Portal is still able to take control of an OBi and change its configuration to:
System Management -> Auto Provisioning -> OBiTALK Provisioning -> Method : Periodically
Voice Services -> OBiTALK Service -> Enable : (checked)
Don't get me wrong here I love my OBi and have recommended them to many other folks as well.
That being said I think a direct answer to my question has been side stepped here. My question is broader than "untethering OBiTALK" but rather includes settings necessary to completely disable anyone other than myself from gaining control of my OBi's.
Based on the above from RonR (I haven't tried the test myself) the reason my broader question has not been addressed, would appear to be that if there are settings which would dis-allow access by anyone other than myself, they are not being presented; since if what RonR says is true then OBiHai can certainly regain control via it's web interface even when the settings referenced thus far are all configured to dis-allow external control. And it follows that if OBiHai can regain control then someone else may be able to use the same method(s) to gain control.
So once again are there settings which will prevent ANYONE other than myself from gaining control of my OBi's? This is a yes or no question.
Ostracus:
Quote from: ShermanObi on May 11, 2012, 07:05:54 pm
@RonR - Yes. When a user adds their device to the OBiTALK portal, dialing **5 allows OBiTALK to associate the OBi with the correct user's account. But then you have probably never done that. ;)
Then I guess we better not dial **5 + nnnn, or create an account to associate with.
.
Mango:
Quote from: VaHam on May 12, 2012, 12:57:03 am
if what RonR says is true then OBiHai can certainly regain control via it's web interface even when the settings referenced thus far are all configured to dis-allow external control.
What RonR says is partly true. Keep in mind that in order for Obihai to regain control, the user of the device would need to dial **5xxxx. Based on what I've seen here, the function of **5xxxx appears to be to turn on OBiTALK Provisioning and OBiTALK Service, and add the device to OBiTALK.
So yes, if you turn on OBiTALK Provisioning and OBiTALK service, then OBiTALK Provisioning and OBiTALK service will be turned on.
Disclaimer: don't consider this me defending Obihai. I absolutely do not agree with automatic firmware updates turned on by default, and I really don't agree with how it's not obvious this is happening, or that the way to disable it is not intuitive.
VaHam:
Quote from: Mango on May 12, 2012, 08:29:35 am
What RonR says is partly true. Keep in mind that in order for Obihai to regain control, the user of the device would need to dial **5xxxx. Based on what I've seen here, the function of **5xxxx appears to be to turn on OBiTALK Provisioning and OBiTALK Service, and add the device to OBiTALK.
I guess I will have to setup a test to answer my question; by blocking network access to the OBi and then dialing the **5nnnn to see if the update and provisioning bits are enabled by the **5nnnn internal to the OBi itself or are switched on only after access to the OBi network is achieved. The reason I wonder about this is Sherman's earlier statement:
Quote
Auto Firmware Update & ITSP Provisioning are parameters used primarily by ITSPs (and managed services VARs). OBiTALK does not use either of these parameters. Some individuals & organizations may use the Auto Firmware Update as described in this FAQ:
(emphasis added)
If these are not used by OBiTALK then why are they being enabled by OBiTALK?
lhm.:
System Management -> Auto Provisioning -> Auto Firmware Update -> Method : Disabled
System Management -> Auto Provisioning -> ITSP Provisioning -> Method : Disabled
System Management -> Auto Provisioning -> OBiTALK Provisioning -> Method : Disabled
Voice Services -> OBiTALK Service -> Enable : (checked)
So even though Auto Provisioning in the above is disabled Auto Provisioning & Auto Firmware Update can still occur if OBiTALK Service -> Enable : is (checked)?
Update: I guess this is the answer to the above, "To maintain OBiTALK OBi-to-OBi calling functionality (and related features), Obihai may make configuration or software modifications to devices that use the OBiTALK Service. Otherwise, when there is a ‘service’ affecting issue, we may need to update its config or software. This is memorialized in the OBiTALK terms of service and this is what we did on Wednesday." It appears they can override the "OBiTALK Provisioning -> Method : Disabled" setting.
Navigation
[0] Message Index
[#] Next page
[*] Previous page