There are a number of posts about Call Answer not functioning in some way (can't set it up, can't get notifications), but does no one else have the problem of inconsistent, unreliable service with Call Answer? None of the troubleshooting instructions help with this.
Ever since we had to switch to the fibre optic-based home phone line, we have found that Bell's system will on occasion fail to notify us of a voicemail message. No flashing light, no VM symbol highlighted on the handset's screen (and we haven't had the intermittent dial tone for a few months). We find out because the caller calls us one or two days later and mentions that we never responded to their message. If we call *98, we find the message. It's really annoying for all parties concerned.
On two occasions, Bell's notification showed up a whole week after the message was left.
I have tried to check on the notification instructions using the 4-1-3 method. After 4 and 1, I get 2 options, not 3. After option 2 comes 'to exit press star'.
We called for support in July, and we were told that, whenever this problem occurs, we need to unplug the Gigahub from the power outlet for 10 seconds, then wait for all the lights to come back on, and then unplug the phone line from the jack for 10 seconds.
Really? Is the problem truly with the modem? The Gigahub controls Call Answer notifications?**
Well, if the Gigahub is responsible, should we wait until we hear complaints from friends and family about unreturned calls before we go through the unplugging routine again? Or should we make it a daily habit?
Has anyone else had this problem? If so, have you solved it?
I hope there is a solution.
** Is it also the Gigahub that suddenly changes the number of rings-before-answering from 7 to 2? Is it the Gigahub that suddenly enables Call Waiting, a service we didn't sign up for?
for more tips on how to use Call Answer.
