Obitalk Provisioning Issue
earthtoobi:
i don't know what is unclear in my original post. my goal is not to manage it via obidevice webpage but via the obitalk portal.
i have shown in the screenshot, where with provisioning turned on(which i have always), the values in OBidevice and ObitalkPortal(where i manage values) are different(even after the obitalk initiated reboot to push changes to device).
let me also say that i have never ever disabled provisioning on my device and ALWAYS manage setting on obitalk portal.
my subsequent comment(as a response) was just to highlight how to sync them , now that i have run into the issue.
my only question is this:
can you run into cases where the provisioning is not applying changes made in obitalk on to the device.
RonR:
Quote from: earthtoobi on July 25, 2011, 10:35:52 am
my only question is this:
can you run into cases where the provisioning is not applying changes made in obitalk on to the device.
An Internet outage between you and the provisioning server would certainly cause your OBi to not be updated until some time after that outage was restored. An internal communications problem between the OBiTALK Web Portal and the provisioning server would likewise cause delays.
Is your OBi located somewhere other than local to your computer? In my opinion, that's the only case where it makes any sense to use the OBiTALK Web Portal OBiExpert. If the OBi is local to you, it's actually simpler to make changes directly to it and you KNOW they got made. You have access to more status and more functionality maintaining it locally than you do through the OBiTALK Web Portal OBiExpert. Other than configuring an OBi located in a remote location that you do not have access to, there's no advantage to using the OBiTALK Web Portal OBiExpert and all it accomplishes is adding an extra layer of complexity and uncertainty.
OBiSupport:
Here is the procedure to configure these parameters (back to their default)
1/ Uncheck the OBiTalk settings box for related parameters
-- CallForwardOnNoAnswerEnable
-- CallForwardOnNoAnswerNumber
-- CallForwardOnNoAnswerRingCount
2/ Check the device default box for these parameters
3/ Submit the change, wait till the device reboots, you should see OBi device settings are same to those in OBiTalk.
Please let's know if it works OK for you, thanks,
earthtoobi:
@ObiSupport: thanks for the steps.what you provide as steps is a nice workaround that works and satisfies the need.
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).
@RonR: its quite a few days between setting of the value and when the issue is reported.so, the corner cases don't apply here.
there are a few Obis that i have to manage remotely. but as far as the obi i reference in this thread, i can choose to manage them locally.i just like the idea of cloud management, even though managing it locally gives more control and these type of sync issues don't arise.
RonR:
Quote from: earthtoobi on July 25, 2011, 02:57:02 pm
i just like the idea of cloud management, even though managing it locally gives more control and these type of sync issues don't arise.
I'm pleased to see you understand the situation and the tradeoffs involved and are making an informed decision.
Navigation
[0] Message Index
[#] Next page
[*] Previous page