Obihai is deleting unwanted topics
Dan_voip:
Quote from: VaHam on May 11, 2012, 05:21:25 pm
I am asking for all settings necessary to keep anyone other than myself from being able to access my OBi's for any purpose other than simple processing of phone calls.
Check ShermanObi's Reply #21 on this topic and you'll have your answer.
I have those 2 settings disabled/unchecked and I can confirm my firmware is still 1.3.0 (Build: 2690) so was not updated.
Beside those 2 you have to disable "Auto Firmware Update" and "ITSP Provisioning", that way you'll be sure your device will not be updated or provisioned.
The difference between Auto Firmware Update and OBiTALK provisioning/service enabled is for the 1st option the OBi device will check and ask for a firmware update while the 2nd one will allow Obihay to push an update to an OBi device.
RonR:
ShermanObi,
Are you sure we have the full story?
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)
Dialing **5 + nnnn in response to the OBiTALK Web Portal's Add Device prompt allows the OBiTALK Web Portal to take full control of an OBi again and in the process re-enables:
System Management -> Auto Provisioning -> OBiTALK Provisioning -> Method : Periodically
Voice Services -> OBiTALK Service -> Enable : (checked)
ShermanObi:
For the purposes of this discussion, the only two parameter settings you need to touch are the ones associated with the OBiTALK Service. This makes sense, given the desire here is to configure the OBi device so it is untethered to the OBiTALK service.
System Management -> Auto Provisioning -> OBiTALK Provisioning -> Method : Disabled
Voice Services -> OBiTALK Service -> Enable : (unchecked)
With these settings, the OBi device has no association to OBiTALK services and features as described in my original post to this topic.
The Obihai platform is quite different from it's peers in the industry in the way it supports multiple services (including the OBiTALK service) and how it approaches multiple provisioned services to be supported simultaneously, e.g. ITSP + OBiTALK.
The Auto Firmware Update parameter is found in the System Management area of the OBi device management system architecture. This is for use by individuals and organizations who want to remotely manage the firmware residing on their OBi device(s). When not disabled, the Auto Firmware Update Method parameter will invoke a firmware update based on the settings and syntax of a couple other parameters called Interval and Firmware URL. There are also UN and PW parameters that can be set to further control how the OBi updates it's firmware.
A similar approach is used for the OBi device configuration profile management when the device is managed by a service provider. These parameters are found in the ITSP Provisioning area of the OBi device management system architecture. Again, the Method setting, when not disabled, will key on its sister parameters that tell the OBi when (Interval) to retrieve its service provider provisioned profile and from where to get it (URL).
These parameters, their function and usage are described in the OBi Device Provisioning Guide found in the Documents and Downloads section of the Obihai Support web page (Click Here).
@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. ;)
RonR:
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)
pc44:
Quote from: ShermanObi on May 11, 2012, 07:05:54 pm
But then you have probably never done that. ;)
LOL that was the funniest line in the whole thread. ;D
Quote from: ShermanObi on May 11, 2012, 07:05:54 pm
The Obihai platform is quite different from it's peers in the industry in the way it supports multiple services (including the OBiTALK service) and how it approaches multiple provisioned services to be supported simultaneously, e.g. ITSP + OBiTALK.
Different from its peers is not always a bad thing. Look at Google Chrome. First major web browser to use/push SILENT UPDATES to all clients -- no user response and no notifications. Firefox seems to have now followed suit. While it raises some legitimate privacy concerns, I can see some benefits, as long as end users have an opt-out option as described above.
Navigation
[0] Message Index
[#] Next page
[*] Previous page