Alerts, forwarding on down?

<< < (2/2)

clyde_story:
Quote from: giqcass on September 22, 2014, 08:19:50 pm

First let me just say setting this up on the Obi won't help if your Obi goes down.  Like I said that needs to be done by the service providers or it won't work on failures.

Uncheck "OBiTALK Settings" next to "CallForwardOnNoAnswerEnable" and "CallForwardOnNoAnswerNumber".
Do not check any of the"Device Default" boxes.
Press "submit" and then "ok"
Check "CallForwardOnNoAnswerEnable"
Enter the number in "CallForwardOnNoAnswerNumber"
Press "submit" and then "ok"


Thanks when you uncheck one it automatically checks the other leaving the impression one has to be checked. Now are red ! the expected behavior? CallForwardOnNoAnswerEnable x !

giqcass:
Quote from: clyde_story on September 22, 2014, 08:38:25 pm

Thanks when you uncheck one it automatically checks the other leaving the impression one has to be checked. Now are red ! the expected behavior? CallForwardOnNoAnswerEnable x !


Funny mine doesn't automatically check the other box.  I'm using Firefox.  Perhaps someone with more knowledge about the portal can chime in.  I don't know what the ! are all about.  I have them on some of my settings but those settings still function.

clyde_story:
Using chrome, but it may be roboform  it loves to randomly fill in stuff when your're not looking. And from what I'm reading there's no "upstream" logic it's all in the device, so no connection, no obi, no mas. So I guess multi-ringing the obi & g-voice from ringto is as close as it's gets to redundant/fail-over/alerts with my current setup, and I set noansfw back to default since it wasn't going to do what I wanted anyway.

Navigation

[0] Message Index

[*] Previous page