Vestalink Call Quality
cluckercreek:
Quote from: JasonInDC on March 25, 2014, 08:28:51 am
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.
Almost all of the 404 errors with Vestalink, like a lot of carriers, is to High cost areas.
giqcass:
Quote from: cluckercreek on March 25, 2014, 01:04:20 pm
Quote from: JasonInDC on March 25, 2014, 08:28:51 am
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.
Almost all of the 404 errors with Vestalink, like a lot of carriers, is to High cost areas.
Based on the complaints I have heard people are getting random 404 errors to many destinations not just the high rate centers. Often the same call will go through if they redial it. This problem sounds like something bigger.
Codesmith:
Quote from: nedsobi110 on March 17, 2014, 03:38:07 pm
I just made the jump from GV to Vestalink. So far the call quality is not as good as it was on GV.
I am wondering about the routing / path and what affects call quality.
Setup - I have a DSL line with an Obi 110.
Questions:
Are my (landline) calls now going only through the Vestalink system? or are they still routed through GV? My GV account is still active as calls placed on my cell phone go through GV, and calls placed on my landline with the Obi 110 go through Vestalink.
Can I / should I disassociate my Vestalink account from GV? or does it matter? I did not port my number into Vestalink, I just let it take over the Obi 110 during the setup process. Would that make a difference as to call quality? I did select "spoofing" so that callers see my GV number, not the new number that Vestalink assigned to me.
I would like this new Vestalink system to work as well as GV has before.
I had minor problems with Google Voice forwarding with both the OBi202 and Vestalink configured on the same device. I removed Google Voice from the OBi202 and the problems went away.
I have GV forwarding to my Vestalink number, then Vestalink Spoofing GV. I had a couple friends send/receive calls from multiple mobile/landlines and was satisfied and subscribed.
CLTGreg:
Quote from: giqcass on March 25, 2014, 04:53:23 pm
Quote from: cluckercreek on March 25, 2014, 01:04:20 pm
Quote from: JasonInDC on March 25, 2014, 08:28:51 am
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.
Almost all of the 404 errors with Vestalink, like a lot of carriers, is to High cost areas.
Based on the complaints I have heard people are getting random 404 errors to many destinations not just the high rate centers. Often the same call will go through if they redial it. This problem sounds like something bigger.
I'd still like to know if a device error can cause the 404s but it sounds like more than a couple of people are having this with GV? Mostly it's an annoyance because I can just try again. But for now I'm hesitant to trust them with inbound because I can't fix that if the phone doesn't ring. Those problems may not exist anymore or it could have been a fluke, but it was enough of a hassle to use Callcentric for inbound.
giqcass:
Quote from: CLTGreg on March 27, 2014, 11:44:03 am
I'd still like to know if a device error can cause the 404s but it sounds like more than a couple of people are having this with GV? Mostly it's an annoyance because I can just try again. But for now I'm hesitant to trust them with inbound because I can't fix that if the phone doesn't ring. Those problems may not exist anymore or it could have been a fluke, but it was enough of a hassle to use Callcentric for inbound.
That's always a possibility but Vestalink is the service I hear these complaints about most. It would be interesting to hear from their customers using the Grandstream device they sell. If their own devices set up by Vestalink have the same issue then we would know where to point the finger.
Navigation
[0] Message Index
[#] Next page
[*] Previous page