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, 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.