About 3 days ago, on both my GV accounts set up on the Obi202, we're no longer getting notifications when we have a new voice mail waiting. I get notified through e-mail from GV, but the Obi doesn't seem to be sending out the stutter dial tone or the voice mail indicator signal on two different GV lines.
Did the firmware change about three days ago? I haven't changed anything in the Obi control panel, and made no changes to the GV settings. Prior to 3 days ago, everything worked fine. I tried rebooting the Obi, but that didn't fix it.
Any help is appreciated!!
Hi Studly,
The firmware did change a few days back. Although it is not yet visible on the Firmware Notification thread and although it did not come down automatically for me, you can access it via ***6.
Not sure if that will help, but it's a thought. You probably also want to double-check your MWIEnable, MWIEnable2, X_VMWIEnable, X_VMWIEnable2, and MessageWaiting settings under Voice Services -> SPx Service.
pc44
Thanks for the tips ... I just downloaded the latest firmware, and it still doesn't work. Anyone else with the 202 unit have this problem using GV?
We are working on a solution for this issue. In the meantime, there is no need to make any changes to your OBi or GV configurations.
Studly: I am having the same exact problem and admin stopped answering my mail. This started about a week ago. Now I have to use my computer to find out if anyone called.
pc44: I wish I understood what this means: (MWIEnable, MWIEnable2, X_VMWIEnable, X_VMWIEnable2, and MessageWaiting settings under Voice Services -> SPx Service.)
I am glad to hear that the admin are working on a solution to this problem. I have another phone that I was going to add but now I am leary!
Quote from: SilverHD on August 14, 2012, 04:46:54 PM
Studly: I am having the same exact problem and admin stopped answering my mail. This started about a week ago. Now I have to use my computer to find out if anyone called.
pc44: I wish I understood what this means: (MWIEnable, MWIEnable2, X_VMWIEnable, X_VMWIEnable2, and MessageWaiting settings under Voice Services -> SPx Service.)
I am glad to hear that the admin are working on a solution to this problem. I have another phone that I was going to add but now I am leary!
On your device or from the expert configuration in the Portal.
Go to Voice Service -> SP(x) Service -> Calling Features
and check the settings for MWIEnable & X_VMWIEnable (MessageWaitingIndicatorEnable & VoiceMailWaitingIndicatiorEnable)
I'm also having this issue. The Voice mail indicator was always fragile and needed to be reset about once every month. In the last week it stop work altogether. Can any one shed some light on this. I'm using GV and an obi110.
Rich
Quote from: OBiSupport on August 13, 2012, 06:15:18 PM
We are working on a solution for this issue. In the meantime, there is no need to make any changes to your OBi or GV configurations.
Thanks for the update. Do you know how we will be notified of the fix or will it be pushed.
Thank You
Just to confirm, is this something I need to activate in order for the voicemail alert to work once the "fix" is released?
http://www.obihai.com/googlevoiceFAQ.html#11
GV Voicemail Notification & Missed Calls
When you enable Google Voice voicemail notification on your OBi, you should be sure to not check the "Place missed calls in the inbox" box. Otherwise, whenever there is a missed call, the phone attached to the OBi will signal (visual and stutter dial tone) an unheard voicemail. The Missed Calls setting can be found in the Google Voice Settings: Calls tab.
Hello again: Good news! I emailed OBi last night, asking when this would be repaired. They updated my "firmware" and it is working fine now. I didn't do anything. I guess it is like they said. We have nothing wrong. They have to fix it. I'm glad they did! Now I'm going to work on putting my other line in.
There is a firmware release available that addresses the voice mail (visual and stutter dial tone) alert indication on OBi devices.
To obtain the firmware update, dial ***6 from the phone attached to your OBi device or log-in to www.obitalk.com (http://www.obitalk.com/) and from the Dashboard, select the yellow triangle adjacent to the OBi device(s) you would like to update.
- Thank you -
Quote from: OBiSupport on August 18, 2012, 01:56:02 PM
There is a firmware release available that addresses the voice mail (visual and stutter dial tone) alert indication on OBi devices.
To obtain the firmware update, dial ***6 from the phone attached to your OBi device or log-in to www.obitalk.com (http://www.obitalk.com/) and from the Dashboard, select the yellow triangle adjacent to the OBi device(s) you would like to update.
- Thank you -
This needs to be posted in the Topic: "Firmware / Advisories / Notifications for Obi Porducts"
I've been getting a notice on the OBiTALK Portal, of an Update for the past few days also.
My device is an OBi100. Does this Update effect my device?
When I choose to manually download it, I'm seeing that the Update is the same version I already have on my device. Is there an Error on the Portal, and it should not be showing an update for the OBi100??
If all of the notices are posted where they can be found under the one Topic "Firmware / Advisories / Notifications for Obi Porducts" it would better serve us all. Of course the Change Log is just as important as the Notice itself.
Many Thanks from a Happy User!
Quote from: OBiSupport on August 18, 2012, 01:56:02 PM
There is a firmware release available that addresses the voice mail (visual and stutter dial tone) alert indication on OBi devices.
To obtain the firmware update, dial ***6 from the phone attached to your OBi device or log-in to www.obitalk.com (http://www.obitalk.com/) and from the Dashboard, select the yellow triangle adjacent to the OBi device(s) you would like to update.
- Thank you -
As of August 27, the 2719 changes are still not posted at http://www.obitalk.com/forum/index.php?topic=9.0 , so the vast majority of users will not be able to find them.
I'm having the opposite problem. As of a few days ago, I can't get the voicemail notification/stutter tone to go away. I set up a second google voice account and did the firmware update the same day, so I'm guessing one of those has something to do with the problem.
I have even unchecked "Google Voicemail Notification" in the configuration for both lines. Stutter tone still won't go away. I'm about to put some electrical tape over the blinking yellow lights on my phones.
Quote from: arobatino on August 27, 2012, 11:36:40 AM
Quote from: OBiSupport on August 18, 2012, 01:56:02 PM
There is a firmware release available that addresses the voice mail (visual and stutter dial tone) alert indication on OBi devices.
To obtain the firmware update, dial ***6 from the phone attached to your OBi device or log-in to www.obitalk.com (http://www.obitalk.com/) and from the Dashboard, select the yellow triangle adjacent to the OBi device(s) you would like to update.
- Thank you -
As of August 27, the 2719 changes are still not posted at http://www.obitalk.com/forum/index.php?topic=9.0 , so the vast majority of users will not be able to find them.
Amazing, isn't it?
Quote from: rocketben on August 27, 2012, 08:15:56 PM
I'm having the opposite problem. As of a few days ago, I can't get the voicemail notification/stutter tone to go away. I set up a second google voice account and did the firmware update the same day, so I'm guessing one of those has something to do with the problem.
I have even unchecked "Google Voicemail Notification" in the configuration for both lines. Stutter tone still won't go away. I'm about to put some electrical tape over the blinking yellow lights on my phones.
I'm having the same problem on an Obi202, and this is to ask if you got yours fixed? Other than with the black electrical tape.
I updated using ***6, which moved me from 3184M to 3397. I have two GV lines and they are both doing this after the update. No unread VMMs, and in box is empty in both GV accounts. Another curiosity, the MessageWaiting field for both these voice services, which is documented as "This is a state rather than a configuration parameter.." shows cleared, so this status field is working opposite of the signals on the physical ports.
Has anyone had direct contact/resolution with ObiSupport on the stutter dial-tone issue? My GV and Anveo accounts still have the stutter, after the firmware update,with the VM notification toggled-off.
Quote from: Mark.P on September 09, 2012, 12:08:09 PM
Has anyone had direct contact/resolution with ObiSupport on the stutter dial-tone issue? My GV and Anveo accounts still have the stutter, after the firmware update,with the VM notification toggled-off.
Yes, I have. For pretty much the same case you describe. I updated firmware to the latest (in the hope of making MWI and VMWI work) and after the update reboot was getting stutter dialtone and VMWI on both phone ports, and couldn't get either either port to clear. They correctly diagnosed the issue as an unread VM in a third service provider. I cleared that, but also had to reboot twice to make the stutter DTs and VMWIs go away, explanation below. For your possible fix, see here (http://www.obitalk.com/forum/index.php?topic=3640.msg26952#msg26952), note unread in Spam, Archive, Text, etc.
My take is there is still something flaky going on, they (ObiSupport) didn't completely understand the situation (seemed to dismiss that the stutter and VMWI didn't go away automatically , it took two reboots to make this go away on both ports), and in a follow up email they implied it was working correctly. I didn't pursue it because after 36 hours of stutter DT and VMWI on both ports I was happy to have it finally clear up.
The flaky part that I still think is a problem: If you have SP1 pointed to ph1, and SP2 pointed to ph2 the MWI/VMWI all seem to work as expected. However, if you have an SP3 pointed to ph1, and set MWI (but not VMWI, and not MWI2 and not VMWI2) on sp3, and you get an unread message on SP3, you will get various results: In particular, MWI and VMWI both on on both ph and ph2 after a reboot. If you then clear the unread message, the MWI and VMWI on ph and ph2 will not go away, you have to reboot twice to clear them, one reboot clears ph, and a second reboot is needed to clear ph2. It's the combination of having an unread message waiting and rebooting that is the root issue, form what I see. Getting and clearing an unread message on SP3 seems to correctly turn on only MWI on ph, from my experimenting.
An update. There is clearly something still broken or flaky here.
I did a test this AM, where I got a missed call into a GV inbox (was set this way on purpose to test) on SP1. Upon reboot the MWI and VMWI on both ph and ph2 were stuttering and flashing. The call came in on SP1 (which is pointed to ph only). Upon marking the VM read, the MWI and VMWI on ph cleared, almost immediately. However, the MWI and VMWI on ph2 did not clear (waited 5 or 10 minutes) had to do a reboot to clear 'em up. Note that MWI2 and VMWI2 on SP1 are unchecked. I'm suspicious that SP2, my third SP (pointed to ph only) is a factor. I subsequently cleared MWI from SP2, VMWI (and MWI2 and VMWI2) were not checked on SP2.
I contacted obihai support, and they told me this:
QuoteYour SP2 has a pending voicemail to be cleared from the OBi point of view. Please enable the voicemail checking on SP2, and check your vmail by dialing **2+SP2-GVnumber. Once it is cleared, you can disable the voicemail checking, then it will no longer stutter.
It worked. However, about a week later, it came back. Which tells me something's not right. Also, the same procedure did not clear up the issue. I've been meaning to contact support again, just haven't gotten to it yet.
UPDATE:I deleted/disconnected all SP's. The stutter still occurred on both Ph1 & Ph2, without any service providers connected.
Contacted ObiSupport: They responded very quickly. Indicated/confirmed that I had the latest firmware on my 202. They advised a factory reset (***8 and press 1 to confirm). I added the device and noted that Ph1 & Ph1 no longer had the stutter-dial-tone. Configured/added my SP's, with the MWI toggled on;set-up the same as prior to the problematic persistent stutter issue. Stutter dial-tone(MWI) seems to be functioning correctly at this time.
Mark.P,
Thanks for this information and your experience with support resolving it. This will/should be very helpful to some other users here who have described a very similar problem. It seems that a factory reset is in order, as you have explained.
Thank you for sharing this info,
pc44
I had voice mail indicator / stutter tone for over a week. Calling in to voice mail said there were no new messages. Then, I got a new voice mail. I called in, listened to it and archived it. The stutter/indicator then went away!
I have some theories, but haven't had time to test them out. Most of the time, I listen to my voicemails on the computer. Maybe that doesn't "clear" the voicemail indication for the obi. And when I try to call in to voicemail, there is no new voicemail to clear, so it doesn't trigger the clear. But calling in and listening to an "unread" voicemail triggers the clear for the obi, getting rid of the voicemail indication. Complete conjecture at this point, but something worth investigating and testing.
Quote from: rocketben on September 17, 2012, 08:04:28 PM
I had voice mail indicator / stutter tone for over a week. Calling in to voice mail said there were no new messages. Then, I got a new voice mail. I called in, listened to it and archived it. The stutter/indicator then went away!
I have some theories, but haven't had time to test them out. Most of the time, I listen to my voicemails on the computer. Maybe that doesn't "clear" the voicemail indication for the obi. And when I try to call in to voicemail, there is no new voicemail to clear, so it doesn't trigger the clear. But calling in and listening to an "unread" voicemail triggers the clear for the obi, getting rid of the voicemail indication. Complete conjecture at this point, but something worth investigating and testing.
Sorry to pour water on your theory, but I never call in for my voicemail, I always listen to them on my computer (or browser on my cell phone) and my indicator works fine.
It has been reported in the past that calling into one's own voicemail helps clear the indicator more quickly than by web access. Though both *should* clear the indicator eventually; to my recollection (could have been another one of my OBi nighttime dreams), more than one person reported faster clearing via the direct dial method.
However, I do agree that the more info we can glean, perhaps the better Obihai can get to the bottom of this issue. I'm not sure I have this problem, but it seems several of you are experiencing it.
I only recently enabled my VM indicators (when others were having problems). I wanted to see if I had the same problems.
I have never called into my google voice account to check a message. I always do it on the PC. Since I have enabled the message waiting, it has worked as it is suppose to.
I'm suspicious that one of the root causes here is having a configuration where two SP services are pointed to one phone port. Such as SP1 and SP2 > ph1, and SP3 and SP4 > ph2, where ">" means InboundCallRoute for the service.
Note that I'm not saying the VM indicators are enabled on the two SP services pointed to the one phone port, just that two SP services are pointed to one phone port.
In my configuration, I've observed the MWI and VMWI have the problems listed here when SP2 has an unread message in a lesser used folder, Spam, Archive, etc.
Quote from: CoalMinerRetired on September 18, 2012, 08:04:38 PM
I'm suspicious that one of the root causes here is having a configuration where two SP services are pointed to one phone port. Such as SP1 and SP2 > ph1, and SP3 and SP4 > ph2, where ">" means InboundCallRoute for the service.
Note that I'm not saying the VM indicators are enabled on the two SP services pointed to the one phone port, just that two SP services are pointed to one phone port.
For the record, I do have SP1 and SP2 both going to PH1. And my voicemail indicator troubles only started after configuring a second GV in SP2. I have SP2 set not to cause a vm indication.
I have always had 2 google voice numbers ringing each phone on my 202, but never had MW enabled for either one.
I recently removed one google voice number from SP2 and replaced it with Callcentric. Shortly after that I enabled MW on SP1 for google voice as per my previous post.
I have 2 google voice numbers on my SP3 & SP4 ringing Ph2. Let me play with those and see what kind of results I get.
I think I finally got this to work. It seems that any unread message in your google voice mail inbox will cause the message indicator light to go on this includes any missed messages such as hang ups etc. When I checked my google voice box it said I had no new messages and the message indicator light was still on. I then checked my inbox via google voice account and there was a missed message when I marked this message the message indicator light went out.
Google voice has an option to save missed messages to your inbox or email I had this enabled so missed messages was causing my indicator to remain on.
I've been using Google's two-step verification since they first introduced it so I never expected to get stutters/flashing LEDs on my home land line via my OBi202. I've lived with it. All of my GV voicemails get delivered to my Gmail inbox and I also get notifications on my mobile phone via the Hangouts app.
I value the extra security of two-factor authentication over the voicemail alert on my OBiHAI extensions so it was never a big deal. But if I could have both, that would be a bonus.
Now that Google and OBiHAI are playing nice, and since it sounds like subsequent OBiHAI firmware upgrades have been chipping away at solving some GV/voicemail alert issues, here's my question:
Is it now possible for a 2-step verification using, OBi202-owning user like me to have both 2-step AND voicemail alerts?
I noticed that the current GV setup wizard presents no voicemail notification checkbox, but the wizard for Callcentric setup does. That leads me to believe that I can't have voicemail alerts on the GV SP slot. But of course I could play around with settings through Expert Config and change the VMI stuff if that actually mattered.
Has anyone else with a similar setup (esp. 2-step verification) gotten this to work LATELY, with all of the new GV/OBi love?
Quote from: DrJay on October 08, 2014, 07:31:29 AM
I've been using Google's two-step verification since they first introduced it so I never expected to get stutters/flashing LEDs on my home land line via my OBi202. I've lived with it. All of my GV voicemails get delivered to my Gmail inbox and I also get notifications on my mobile phone via the Hangouts app.
I value the extra security of two-factor authentication over the voicemail alert on my OBiHAI extensions so it was never a big deal. But if I could have both, that would be a bonus.
Now that Google and OBiHAI are playing nice, and since it sounds like subsequent OBiHAI firmware upgrades have been chipping away at solving some GV/voicemail alert issues, here's my question:
Is it now possible for a 2-step verification using, OBi202-owning user like me to have both 2-step AND voicemail alerts?
I noticed that the current GV setup wizard presents no voicemail notification checkbox, but the wizard for Callcentric setup does. That leads me to believe that I can't have voicemail alerts on the GV SP slot. But of course I could play around with settings through Expert Config and change the VMI stuff if that actually mattered.
Has anyone else with a similar setup (esp. 2-step verification) gotten this to work LATELY, with all of the new GV/OBi love?
Hi Jay!
The new OBi support for Google Voice no longer supports the message-waiting stutter tone or the visual message waiting indicator (MWI or VMWI). This is unrelated to 2SV; it doesn't work at all any more. The MWI/VMWI function for SIP carriers like Callcentric still works as always, but it won't help you with GV voicemail, since it would only apply to voicemail messages left on Callcentric's own VM system.
Is this something that will be added in the future? We miss not having that feature.
Jason
Quote from: roguegaston on October 08, 2014, 08:04:42 PM
Is this something that will be added in the future? We miss not having that feature.
Jason
I have no idea. Obihai may or may not disclose what they are working on, but this feature never worked consistently for more than a few months, before it broke again. My hunch is that it was a hack that they've decided to abandon.
As I suspected. Thanks, Steve!
Help!!!
Like an idiot, I paid attention to this ad without reading down the entire page and did what the first post said to do without reading further. This is what I read and I did:
Contacted ObiSupport: They responded very quickly. Indicated/confirmed that I had the latest firmware on my 202. They advised a factory reset (***8 and press 1 to confirm). I added the device and noted that Ph1 & Ph1 no longer had the stutter-dial-tone. Configured/added my SP's, with the MWI toggled on;set-up the same as prior to the problematic persistent stutter issue. Stutter dial-tone(MWI) seems to be functioning correctly at this time.
After I reset my device, I could not get anything to work at all. I tried reconfiguring GV and that would not work so I went ahead and took the recommended rebuild again, figuring that that would at least put me back in business. Well it didn't. I currently have (2) 202's and, thank God, one is still working fine because I didn't touch it. Here is the problem now. I can receive calls on one phone but on the other, it goes directly to VM. I can't call out on either therefore the green lights are both jon on the left but the one's on the right are off.
The error that I am getting is this: Error: Cannot find specified device:717579(basic_gv) even though GV is showing it is connected correctly but I don't know what this error means anyway. I contacted Support last night but they have yet to respond. Any help or assistance is greatly appreciated....please note, I am NOT a tech. Thanks much, Silver
Have you tried removing your device from Obitalk.com and then adding it back again? Sometimes that helps.
Yes, I did that right away and now I'm stuck. >:(
Hello again: Can someone please help with this situation? Like I said I am not techy. The only thing that I can see that may help in this is the error message: Error: Cannot find specified device:717579(basic_gv)
I'm just not sure what to do with that. I think I have everything hooked up to GV correctly. ???
Thanks again,
Silver
Hi Silver,
Re-adding the device to OBiTALK should resolve the issue. It appears your Google Voice account is configured correctly and showing Connected now. Please open a support ticket if you have any other questions. Our support team will be happy to assist.
Thank you for the response. It seems everything is working correctly with the exception of the second line, SP2. It still doesn't ring and goes straight to voicemail. Don't know what exactly the problem is. ???
Thanks,
Silver
Is the SP2 voice service configured and registered to a server?
Does the SP2 X_InboundCallRoute = ph2?
Is DND set on PHONE2 port?
(What does this old thread have to do with your new trouble?)
Thank you for trying to help but I have the whole thing figured out now. I mistakenly followed an advertisement and thought that OBi had configured somehow to make the 202 work with message notification and got in big trouble. Anyway, all is well, but thanks anyway.
:)Silver