MWI Timing Out On Vestalink Service (has been fixed by VestaLink)
REC25:
Quote from: cluckercreek on September 02, 2014, 06:29:01 am
Some of the settings changed during the last Obi firmware on Vestalink. I don't know why the others SP's on my 202 didn't change. After I went back in and "reset" them I haven't had a problem.
If you could find the time to post what settings you reset, it would be appreciated. I have an Obi 200 and it had firmware 3.0.1 build 4350 when I set up with Vestalink. Today I added GV which caused the Obi to update to 3.0.1 build 4420. After adding GV I deleted SP1, Vestalink, and provisioned it again. I did see a couple of changes in the settings from where it was originally, but I still have the same problem with MWI timing out within 1/2 to 2 hours. Had Anveo for 6 months before I went with Vestalink and had no problems with their MWI.
cluckercreek:
REC25,
When I updated the firmware of my Obi 202 it is 4412. Under the setting of "voice service" it deleted my check marks for MWIEnable, MWIEnable2, X_VMWIEnable, X_VMWIEnable2 and AnonymousCallBlockEnable. I rececked the boxes and the MWI started working correctly for whatever the reason. I tried to see if my unit would update to the 4420 firmware and it will NOT. Hmmm, I don't know the differences between them. Hope that helps.
REC25:
cluckercreek ,
Thank you for your reply. I checked my settings and found MWIEnable and X_VMWIEnable checked(200 has 1 phone line) but AnnonymousCallBlockEnable not checked. I went ahead and checked it just because it seemed like a good idea. From what I have been able to find it seems this problem may only affect some people, myself, ceg3, and a few others. Maybe this is a problem with certain locations. I remember seeing posts about GV taking a long time to connect and poor voice quality which just may have been due to their location since most people, including me, found GV works very well.
The update to build 4420 was done automatically. When I clicked on GV from the providers list a note popped up telling me to wait while my Obi was being updated. From what I read in another post about Google Voice being back, a reply by SteveInWA , it seems that this build may be targeted just for GV service. That is just my guess.
Considering that when you were updated to build 4412 some of your settings were changed, maybe build 4420 was done to correct that problem, because when I got that update none of my settings were changed.
cluckercreek:
Interesting. I'm using Vestalink, F9, GVoice and Callcentric with my setup. I deleted GVoice and set it back up but no update. Of course I had to go through the new GVoice authorization steps but it didn't update. I guess I'll just keep using as is since no problems have popped up since the MWI issue. Thanks for your input and info!
REC25:
ceg3,
With firmware updated and a re-provision of Vestalink, the problem stays the same. Since there are not many replies on this topic, I guess the MWI timeout is only affecting a few users, or a lot of them have an answering machine like I do and don't realize there is a problem. When I was looking around for info about Vestalink, I did not notice your post as I was looking for "Vestalink" in the subject line. Perhaps you could modify your subject line to include "Vesalink" in order to attract more Vestalink users to read and comment on it. Just a thought.
Navigation
[0] Message Index
[#] Next page
[*] Previous page