Synchronization of device configuration with OBiTalk and OBiExpert Configuration
SteveInWA:
This sort of mess is why I recommend, and I will say again: pick a method and stick with it. Don't dick around configuring things in both interfaces; there is no good reason to do so.
restamp:
I maintain several OBi-200's for friends. I have not disabled any provisioning. I had thought that OBiTalk would push new firmware to the devices as needed, but it apparently does not do this automatically. Instead, I get the orange triangle with "!" in it on the OBiTalk dashboard, indicating the device needs to be updated.
Is it possible to cause an OBi to update its firmware remotely? The documentation claims that clicking on the orange triangle will do it, but it just takes me to a web page in this forum which describes the various options for how to upgrade. But, I wonder if there is a work-around: For instance, would it be possible for me to call into the remote OBi's AA1 and enter ***6 from there (probably after selecting AA1's option 2) to access its AA2 and upgrade the firmware? Any other ideas?
SteveInWA:
Quote from: restamp on March 06, 2016, 07:27:07 pm
I maintain several OBi-200's for friends. I have not disabled any provisioning. I had thought that OBiTalk would push new firmware to the devices as needed, but it apparently does not do this automatically. Instead, I get the orange triangle with "!" in it on the OBiTalk dashboard, indicating the device needs to be updated.
Is it possible to cause an OBi to update its firmware remotely? The documentation claims that clicking on the orange triangle will do it, but it just takes me to a web page in this forum which describes the various options for how to upgrade. But, I wonder if there is a work-around: For instance, would it be possible for me to call into the remote OBi's AA1 and enter ***6 from there (probably after selecting AA1's option 2) to access its AA2 and upgrade the firmware? Any other ideas?
All you need to do is (on your OBiTALK dashboard) click the orange triangle next to the blue gear icon on the row for the OBi device reporting an update available. I actually just did this today for a device I remotely manage, and it simply worked. It returned a web page showing that the update was in progress, and after it was done and rebooted, the portal page returned.
If your device isn't doing this, then you've changed something to prevent it from happening.
cracker:
Okay so it is a mess. I am trying to use the expert configuration tool in OBiTalk to make needed changes and was merely trying to see how the system works. The parameters I thought would change with a reboot were set with star codes and not with the device UI.
Is it possible to change the calling feature settings using both star codes and the OBiTalk expert configurtion tool? If so, what procedure does one follow to push the settings from the OBiTalk tool to the device?
azrobert:
Quote from: restamp on March 06, 2016, 07:27:07 pm
Is it possible to cause an OBi to update its firmware remotely? The documentation claims that clicking on the orange triangle will do it, but it just takes me to a web page in this forum which describes the various options for how to upgrade. But, I wonder if there is a work-around: For instance, would it be possible for me to call into the remote OBi's AA1 and enter ***6 from there (probably after selecting AA1's option 2) to access its AA2 and upgrade the firmware? Any other ideas?
You can access the remote OBi's AA2 over the OBiTalk network.
Local OBi:
Define a speed dial: PP(123456789*0)
Change 123456789 to the OBi Number of the remote OBi.
This will send a zero to the remote OBi.
Remote OBi:
Voice Services -> OBiTalk Service
Add the following to the beginning of the InboundCallRoute:
{987654321>0:aa2},
Change 987654321 to the OBi number of your local OBi.
If the current inbound route is just "ph" it must be changed to "{ph}".
The above will check for a zero coming from your OBi and route the call to the AA2.
You don't need to enter the "***". You will receive a prompt for the AA2 options.
Navigation
[0] Message Index
[#] Next page
[*] Previous page