Intermittent CallFwdNoAnswer and no Caller ID syslog with UnconditionalFwd!

<< < (3/3)

GWCS:
I agree that your configuration is better (much better) with no call forwarding settings in place and the X_InboundCallRoute set as instructed, and I don't foresee ever changing that. I have not been at home for a couple of days and changed the settings remotely, so I have not actually seen if I can answer the call on the Obi, but I will take it on faith that it works until I get home to see for myself.

I do, however, still see the inconsistency of the CallerID syslog generation as a bit of a bug, but I suppose that is a matter of opinion. Don't get me wrong. I really like my Obi, and am considering buying a couple more of them, including one for my mom so that she has a "home phone" in addition to her cell.

The idea that a future firmware upgrade might eliminate the CallerID syslog generation altogether, in the interest of "trimming the fat" of electronic verbage, is an unsettling thought. I do have the default of Auto Firmware Update under Auto Provisioning as "disabled", so I presume I won't just get saddled with a deficient firmware upgrade without my consent. I see that it is easy to save my configuration, but is there a way to save my current firmware on a computer's hard drive in the event that I do a firmware upgrade in the future, only to discover that I wish to revert to the current version?

Navigation

[0] Message Index

[*] Previous page