Vestalink Call Quality
erkme73:
Well, sure. I know there are workarounds, and do use them. I'm really just venting, to help confirm that this is a problem. Ideally, once they get their growing pains out of the way, it'll be a one-number, one-device solution, as it should be.
giqcass:
Quote from: erkme73 on March 21, 2014, 09:38:27 pm
Well, sure. I know there are workarounds, and do use them. I'm really just venting, to help confirm that this is a problem. Ideally, once they get their growing pains out of the way, it'll be a one-number, one-device solution, as it should be.
In my view of things I don't consider Voip to Voip calls a work around. I consider VOIP the future of how things are done. I hope you are correct and they overcome their "growing pains". In principle Vestalink could one day be an excellent provider. They are constantly trying to add new features. I wish them the best of luck.
Of course if you need a good rant go for it. lol
MurrayB:
I would not consider Obi to Obi a workaround. The Obitalk network exists for Obi to Obi communication. Speed dial another Obi and the telephone rings. All my incoming calls are forked to all locations simultaneously with excellent quality via the Obitalk network. An additional advantage is that there no per minute costs.
Good Luck!
Taoman:
Quote from: erkme73 on March 21, 2014, 09:13:11 pm
I'm glad to see I'm not the only one with this "feature" - and I thank you for the great explanation of what's happening.
Vestalink told me to run their "echo test" after I complained. It was nearly perfect, but obviously it's taking a different, shorter, and more direct route. If you think it's impossible to have an inbound phone call that comes through GV, you should hear mine... My dad and I both use OBi/GV/Vestalink. The delay is >2 seconds. Talk about frustrating. I'm ready to murder him by the time we finish a 10 min call.
Yes, the Vestalink echo test isn't worth much........especially if you're using your Vestalink DID as a forwarded number in GV.
If you want a more realistic echo test try the following:
1) Get on a browser and access Google Voice and start a "callback" phone call to your Vestalink DID.
2) Enter (408) 647-4636 in GV and after you leave a message (#1) and hear the playback, select 3 and try the echo test. That will give you a much more accurate gauge of the latency you are experiencing. You can run some of the other tests also but if your latency is real bad (like mine is) the other tests don't really matter.
You can then call that number directly on your Vestalink DID and compare the echo tests.
JasonInDC:
I have had Vestalink for a couple of weeks now and it has been a horrible experience. I get 404 errors on just about every other outbound call. The calls that do connect keep getting dropped after a couple of minutes. I have followed all of the advice from vestalink support, but nothing has corrected the issue. I'm about to start looking for alternate providers.
Navigation
[0] Message Index
[#] Next page
[*] Previous page