How to reboot OBi device using OBiTALK web portal
jimates:
Quote from: RonR on April 25, 2012, 09:37:48 pm
I thought one of the main reasons for using the OBiTALK Web Portal was to administer remote/unattended OBi's.
How do you dial ***9 remotely?
How often do find a need to reboot your device, remote or direct, without making a change prior to the reboot?
Ostracus:
Well rebooting as a way of fixing "I'm hung" issues, or in the case of the Obi202, fixing downstream issues.
Felix:
Quote from: RonR on April 25, 2012, 09:37:48 pm
I thought one of the main reasons for using the OBiTALK Web Portal was to administer remote/unattended OBi's.
How do you dial ***9 remotely?
I never tried, but can't you forward the incoming call to aa2 (that is, administrative IVR)? Maybe for specific caller id. Obviously, while you are doing it the device will reboot; so the need to reboot once more may become moot :P
Quote
Well rebooting as a way of fixing "I'm hung" issues,
Well, if the device is hung, it will probably not respond to commands from web portal. Heck, for me it was really hung and didn't respond to commands from the router, either!
justme:
i am having problems with one of my Obi110 devices. the other party cannot hear me. it doesn't reboot changing anything on the web portal. the other party did dial ***91 but i am not sure how successful got it done. i need to be able to do it remotely, anyone? i had changed the inbound route call to ph but i am still getting the AA. that means that, even though i got the Okay for the change, nothing happened.
Navigation
[0] Message Index
[*] Previous page