GV voicemail indicator
CarlAron:
Yes, it does seem to take longer for messages from people not in the contact list to show up... also from people in the contact list, but who did not ring, because I was already on the line with someone else.
It seems like maybe the act of connecting to my Obi to ring it refreshes the connection and updates the MWI status right away? Although of course the MWI signal would have to come a minute or so after the ring, since the person has to have time to leave the message... so that doesn't quite make sense.
I've never noticed the stutter-tone thing ... I suppose my phone does that, but to me a ring is a ring ... Maybe I just check voicemails when I see the light, rather than wait for the phone to ring with someone else calling, so maybe it doesn't happen that often?
One clue, though, if I look in the Obi web interface when there is a message in GV, I can see that the Message Waiting state is still off, so I think that it is Google not telling the Obi about a new message (or the Obi not asking Google about new messages), rather than the MWI signal getting through and not affecting the light on the phone.
pc44:
Quote from: CarlAron on March 22, 2012, 06:44:58 am
I've never noticed the stutter-tone thing ... I suppose my phone does that, but to me a ring is a ring ... Maybe I just check voicemails when I see the light, rather than wait for the phone to ring with someone else calling, so maybe it doesn't happen that often?
The stutter-tone that I was referring to is the sound you hear when you pick the telephone to check for dialtone. Instead of a normal steady dialtone, the stutter-tone is a fast-beep that indicates the presence of voicemail. I was curious if that was working any more consistently or reliably in your setup than the visual indicator.
Quote from: CarlAron on March 22, 2012, 06:44:58 am
One clue, though, if I look in the Obi web interface when there is a message in GV, I can see that the Message Waiting state is still off, so I think that it is Google not telling the Obi about a new message (or the Obi not asking Google about new messages), rather than the MWI signal getting through and not affecting the light on the phone.
Makes sense. I am wondering if Google lowers the priority of notifying telephone lines that are not checked for forwarding. Either way, I do hope you make progress as there must be a resolution for this.
rlev:
I'm having a problem with the voice mail indicator not going away ...
I've updated to 1.3.0 build 2690 but it still remains ...
It won't go away even when I uncheck the MessageWaiting ... hit submit and reboot
MWIEnable is check
X_VMWIEnable is check
MessageWaiting is not checked
and I still have the indicator and stutter
Any ideas ...
RonR:
rlev,
You might try the following:
Log into the OBi at the IP address returned by dialing ***1. You cannot do this from the OBiTALK Web Portal as the needed setting does not exist there.
Disable Auto Provisioning and reboot:
System Management -> Auto Provisioning -> ITSP Provisioning -> Method : Disabled
System Management -> Auto Provisioning -> OBiTALK Provisioning -> Method : Disabled
Go to:
Voice Services -> SP1 Service -> MessageWaiting
and uncheck the Default checkbox and click Submit. Unplug the power from the OBi. With the OBi powered off, clear the Message Waiting Indicator on the phone. If the Message Waiting Indicator on the phone returns with the OBi powered off, the problem obviously isn't with the OBi.
Plug the OBi back into power and go back to:
Voice Services -> SP1 Service -> MessageWaiting
If the checkbox immediately to the right of this setting becomes checked and your phone again reports Message Waiting, it's the OBi that's turning it on. If the checkbox stays unchecked, the phone should not turn on its Message Waiting indicator.
rlev:
Quote from: RonR on March 25, 2012, 06:57:26 pm
rlev,
You might try the following:
Log into the OBi at the IP address returned by dialing ***1. You cannot do this from the OBiTALK Web Portal as the needed setting does not exist there.
Disable Auto Provisioning and reboot:
System Management -> Auto Provisioning -> ITSP Provisioning -> Method : Disabled
System Management -> Auto Provisioning -> OBiTALK Provisioning -> Method : Disabled
Go to:
Voice Services -> SP1 Service -> MessageWaiting
and uncheck the Default checkbox and click Submit. Unplug the power from the OBi. With the OBi powered off, clear the Message Waiting Indicator on the phone. If the Message Waiting Indicator on the phone returns with the OBi powered off, the problem obviously isn't with the OBi.
Plug the OBi back into power and go back to:
Voice Services -> SP1 Service -> MessageWaiting
If the checkbox immediately to the right of this setting becomes checked and your phone again reports Message Waiting, it's the OBi that's turning it on. If the checkbox stays unchecked, the phone should not turn on its Message Waiting indicator.
RonR,
I've done as you asked and after turning off "Auto Provisioning" and clearing the MessageWaiting the phone still came back with a NewVoiceMail display. (Note the one thing I didn't do is clear the phone as I see no way to do that ... (the message does disapear when the obi is rebooted)
I'm fairly certain that the indication is coming from the obi as the obi gives me a stutter-tone
Navigation
[0] Message Index
[#] Next page
[*] Previous page