Vestalink Call Quality
nedsobi110:
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.
Taoman:
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.
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.
If you ran their "Easy Setup Tool" then outgoing calls are only going thru Vestalink. Google Voice is not involved other than you're spoofing your GV number. How is the quality of your outgoing calls?
I assume incoming calls are going thru Google Voice and then being handed off to Vestalink but I'm not entirely sure based on your wording. What number is being dialed for incoming calls? Your Vestalink number or your GV number? If your Vestalink number is being dialed then Google Voice is not involved but I assume that's not happening.
If you remove your Vestalink DID number from your Google Voice account then the only way incoming calls will get to your Obihai is if the caller uses your Vestalink DID number. Kind of makes sense, doesn't it?
I am experiencing the same thing as you with my Obi ATA . My biggest problem is extreme latency when using my Vestalink DID as a forwarded number in Google Voice. The delay is so bad that having a conversation is almost impossible. I just sent in a support request to see if anything can be done (like changing my DID number). I have read the reason Vestalink gives for this problem is that the DID number they assign is on a "different upstream provider" than the GV number. Say what? Sucks to be me. :'(
My outgoing call quality with Vestalink is ok.....not great.......but tolerable. So currently I am using Vestalink only for outgoing calls. I got a free DID (IPKall) and a free SIP account (Anveo), configured it on SP2, and put it as a forwarding number in Google Voice. I get much better call quality and no latency going this route for my incoming calls. It's a bitch considering I'm paying for Vestalink but it is what it is. My current configuration, although not ideal, is at least workable for me. Hopefully, Vestalink will come up with a solution of some kind but I'm not holding my breath.
Good luck.
PS. If you ran the Vestalink Easy Setup tool then your Obi is "locked" to their configuration and you won't be able to configure SP2 (and have it stick) until it is unlocked. Search this site to find out how. This reply is already WAY too long to go there.
giqcass:
You are using an Obi110 so it sounds like you have phone service through your internet provider(likely a telephone company) as well. Is that the case? If so incoming calls might be routed through that service if you are forwarding your Google Voice number to it. Your outbound calls are likely all going through Vestalink. If you have a true POTS line I would make sure 911 calls were directed to the POTS line instead of through Vestalink. I do not know if Vesatlink does that by default.
If you log in to your Obi110s IP adress well you are making or receiving a call you can see details about the call by clicking the satus link and then the Call status link.
erkme73:
Quote from: Taoman on March 18, 2014, 04:48:19 pm
I am experiencing the same thing as you with my Obi ATA . My biggest problem is extreme latency when using my Vestalink DID as a forwarded number in Google Voice. The delay is so bad that having a conversation is almost impossible. I just sent in a support request to see if anything can be done (like changing my DID number). I have read the reason Vestalink gives for this problem is that the DID number they assign is on a "different upstream provider" than the GV number. Say what? Sucks to be me. :'(
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.
giqcass:
Quote from: erkme73 on March 21, 2014, 09:13:11 pm
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.
This doesn't solve all of you problems but why don't you call each other Obi to Obi? I bet the call quality will be a lot better.
Navigation
[0] Message Index
[#] Next page