Obitalk Provisioning Issue
OBiSupport:
Quote from: earthtoobi on July 25, 2011, 02:57:02 pm
what it does not explain is: why this attribute managed via Obitalk as an obitalk setting is not able to propagate itself down to the device.(especially in cases when you reset values or make it null etc).
Further clarification - the posted procedure is applied to the parameters indirectly managed by OBiTalk, note, there is no '*' next to the OBiTalk setting box. For other parameters that come with a '*' in OBiExpert, you can manage them directly via OBiTalk setting check box.
OBiSupport:
Please also refer to this link for the details
http://www.obitalk.com/forum/index.php?topic=458.0
earthtoobi:
so, if an obitalk setting is checked and there is no '*' next to it, then what would be the setting applied to the device?
in my screenshot, it had empty values, and the obitalk setting is checked.
can you confirm that the screenshot is expected behavior.
Here is my understanding:
1. if obitalk setting is checked, then default obitalk values are going to be applied to the device.
2. if obitalk setting is unchecked and device default is checked, then device default is applied to the device
3. if obitalk setting is unchecked and device default is unchecked, then the entry that you put in the screen takes effect(obiexpert setting)
the variation of point 1 is the existence of a '*' next to obitalk setting, signifying feature configuration(like Inboundcallroute etc) and any new feature obi team can introduce in future using those settings(along with new fields that can get a '*' next to it). from an end user what this means is that, he better know what he is messing with when he is unchecking that box as he could cripple present/future obi functionalities.
OBiSupport:
You are correct on your understandings.
The screenshot is also expected behavior. If the OBiTalk setting is checked and the parameter doesn't come with an asterisk '*', then, the device will keep the particular setting as it is.
earthtoobi:
Quote from: OBiSupport on July 26, 2011, 04:20:50 pm
You are correct on your understandings.
The screenshot is also expected behavior. If the OBiTalk setting is checked and the parameter doesn't come with an asterisk '*', then, the device will keep the particular setting as it is.
This is where it gets un-intuitive to me.
if the obitalk setting is checked(and if there is no '*'), what you are telling me is that it is going to keep whatever setting the device currently has been set to.
is there a default setting for the cloud that it can push to the device?
the above quote means that:
for someone managing the device remotely, he can never be sure of what settings the device is currently working off of(for fields where obitalk is checked and there is no '*').
Navigation
[0] Message Index
[*] Previous page