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.
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.
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.
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.
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.
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.
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
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!
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.
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.
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.
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.
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.
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.
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.
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.
My experience has been different. I switched our landline from charter to an obi202+vestalink as sp1.
Before switching, we experimented for 7-10 days with just outbound calls to gauge the quality. The judgement was the quality was as good as, possibly better than, the quality provided by charter, so we ported our landline to vestalink. We have yet to have any problems with the quality of either incoming or outgoing calls (although a recent service outage is another matter).
Our isp is charter broadband and we're on their cheapest service.
We've been using Vestalink for a few weeks with incoming calls going thru Google Voice and then being handed off to Vestalink/Obi100. When calls connect, outgoing and incoming call voice quality is good. But about 25% of the time it takes a long time for GV calls to ring the Vestalink line compared to cell phones phones connected to GV. A fraction of the time, the Vestalink line never rings.
This morning, the Vestlink line wouldn't ring for GV incoming calls until I made a call directly to the Vestalink line. Would such problems be mostly on Google's side? I will soon contact Vestalink to see what they can do. I wouldn't trust this service for incoming calls without having GV also forwarded to a cell phone.
Quote from: mmm12 on March 28, 2014, 08:57:39 AM
This morning, the Vestlink line wouldn't ring for GV incoming calls until I made a call directly to the Vestalink line. Would such problems be mostly on Google's side? I will soon contact Vestalink to see what they can do. I wouldn't trust this service for incoming calls without having GV also forwarded to a cell phone.
I saw a post that Vestalink was down for some period of time this morning. But generally if calls to your GV number forwarded to Vestalink result in the phone connected to the obi not ringing it is a problem with Google Voice. If available I would check Vestalink logs to see if they see the call coming into you and compare it to the logs that Google Voice has.
I signed up for Vestalink about a month ago for our home due to the GV switch. We rarely use the "home phone" so we haven't noticed any issues.
The big mistake came when we signed my wife's grandma up for it. She always uses her home phone. Vestalink has been such a pain. Dropped calls. Incoming calls not connecting. Call forwarding not working. Long outages like this morning.
I regret ever using Vestalink. I will not recommend them again but have a contract with them for 2 years.
Quote from: mmm12 on March 28, 2014, 08:57:39 AM
We've been using Vestalink for a few weeks with incoming calls going thru Google Voice and then being handed off to Vestalink/Obi100. When calls connect, outgoing and incoming call voice quality is good. But about 25% of the time it takes a long time for GV calls to ring the Vestalink line compared to cell phones phones connected to GV. A fraction of the time, the Vestalink line never rings.
This morning, the Vestlink line wouldn't ring for GV incoming calls until I made a call directly to the Vestalink line. Would such problems be mostly on Google's side? I will soon contact Vestalink to see what they can do. I wouldn't trust this service for incoming calls without having GV also forwarded to a cell phone.
I'm getting the same kinds of issues here. the 911 service they include is kind of useless when these kinds of problems, imo.
I've had Vestalink for a few weeks now and I'm going to cancel. They offer a 30 day money back gaurantee so I am going to take them up on that.
Thing is, call quality is not what it was with GV and the latency is just enough to make the conversation difficult. Last night I made a call and the CID showed up on the person's phone as some number from a business. Not to mention a few times when the service 404ed on me. It's not ready for prime time.
I just signed up for PhonePower but I swear I can't figure out how to set it up on my Obi100.
The nice thing about PP is they are 24/7 support via their webpage.
The 404 error -- prob VL, however, the CID error is due to the receiving
station pulling from a database that hasn't been updated yet for CNAM.
I initially thought the call quality with Vestalink wasn't the greatest either, but then I noticed when looking at the Obi call status page (during a call via the Obi IP address directly or via Obitalk expert config) that incoming and outgoing calls were defaulting to the G.729 voice codec, which is worse than the G.711u codec. I simply went into the expert configuration and disabled the G.729 voice codec, and now all my calls default to G.711u, which is the landline PSTN codec I believe. All my calls have been sounding GREAT now with Vestalink!
I'm not sure why Vestalink was defaulting to G.729 since my cable modem connection is great with plenty of up/down bandwidth. Anyway, try disabling the G.729 codec first!
Quote from: lburgguy on April 03, 2014, 05:17:45 AM
I've had Vestalink for a few weeks now and I'm going to cancel. They offer a 30 day money back gaurantee so I am going to take them up on that.
Thing is, call quality is not what it was with GV and the latency is just enough to make the conversation difficult.
...
Thanks, PCSguyMD, for the tip. Seems to be better quality.
Thanks PCSguyMD.
I had noticed the same thing looking at "Call Status" of live calls and comparing to "voip.ms" calls. I found that all Vestalink incoming and most outgoing calls defaulted to the G729 voice codec. All incoming and outgoing calls on voip.ms defaulted to G711u voice codec.
Following your lead, I used OBiTALK Expert Configuration Tool to disable the G729 Codec. Now all my Vestalink calls and voip.ms calls default to G711u and the Vestalink audio quality has improved.
-- Specifications --
Codec BitRate Bandwidth (Kilobits)
G729a 8 Kbps 31.2 Kbps Moderate Quality
G711 64 Kbps 87.2 Kbps Better Quality
Hi Everyone:
I appreciate the feedback. I believe we have solved the issues with the 404 calling problems. But I will need more feedback. We have not had any support requests regarding these problems for a while. Furthermore We do not block any calls to the lower 48 states regardless of high cost etc. All other numbers can be reached by dialing 011+the number.
As far as Google voice latency, we are using a different carrier than Google Voice so the calls from Google Voice go over the PSTN before they get to your Vestalink account. The best way to solve this latency would be to port your number to Vestalink.
I would like some more feedback regarding the g711 vs g729 codec. The g729 codec is what we use standard on our ht701 devices because it uses significantly less bandwidth (8kb). In low bandwidth connections, like dsl you might have a choppiness issue with g711. However g711 will provide you with significantly better call quality.
Should this be a configurable option in the Vestalink account settings?
Quote from: intelafone on April 04, 2014, 07:58:08 PM
Hi Everyone:
I appreciate the feedback. I believe we have solved the issues with the 404 calling problems. But I will need more feedback. We have not had any support requests regarding these problems for a while. Furthermore We do not block any calls to the lower 48 states regardless of high cost etc. All other numbers can be reached by dialing 011+the number.
As far as Google voice latency, we are using a different carrier than Google Voice so the calls from Google Voice go over the PSTN before they get to your Vestalink account. The best way to solve this latency would be to port your number to Vestalink.
I'd like to see the codec selectable as I am too lazy to go in to advanced config. As far as the 404s go I'll try to test over the next few days. None of my outbound calls have used Vestalink. As far as Google Voice goes, I haven't noticed any latency but I haven't been using the service very much.
Quote from: intelafone on April 04, 2014, 07:58:08 PM
Hi Everyone:
I appreciate the feedback. I believe we have solved the issues with the 404 calling problems. But I will need more feedback. We have not had any support requests regarding these problems for a while. Furthermore We do not block any calls to the lower 48 states regardless of high cost etc. All other numbers can be reached by dialing 011+the number.
As far as Google voice latency, we are using a different carrier than Google Voice so the calls from Google Voice go over the PSTN before they get to your Vestalink account. The best way to solve this latency would be to port your number to Vestalink.
I would like some more feedback regarding the g711 vs g729 codec. The g729 codec is what we use standard on our ht701 devices because it uses significantly less bandwidth (8kb). In low bandwidth connections, like dsl you might have a choppiness issue with g711. However g711 will provide you with significantly better call quality.
Should this be a configurable option in the Vestalink account settings?
[/quote
I haven't had the latency issues but I tried the 711 codec as suggested since I have a good cable connection and call quality does seem better.
Quote from: BigJim_McD on April 04, 2014, 12:58:18 PM
Thanks PCSguyMD.
I had noticed the same thing looking at "Call Status" of live calls and comparing to "voip.ms" calls. I found that all Vestalink incoming and most outgoing calls defaulted to the G729 voice codec. All incoming and outgoing calls on voip.ms defaulted to G711u voice codec.
Following your lead, I used OBiTALK Expert Configuration Tool to disable the G729 Codec. Now all my Vestalink calls and voip.ms calls default to G711u and the Vestalink audio quality has improved.
-- Specifications --
Codec BitRate Bandwidth (Kilobits)
G729a 8 Kbps 31.2 Kbps Moderate Quality
G711 64 Kbps 87.2 Kbps Better Quality
This codec discussion is very interesting, especially at the bottom line of potentially better call quality, but you guys are over my head in discussing codecs. Can you give specific directions for disabling the G729 codec in ObiTALK? I can get to Profile A, which I assume corresponds with my Vestalink setup on SP1, but what to do when I get there? Thanks!
After a closer look I did see the enable check box. I unchecked the two boxes on the "codec" line and the enable box and a check of an inbound call indicated the G711U codec.
Quote from: intelafone on April 04, 2014, 07:58:08 PM
Hi Everyone:
I appreciate the feedback. I believe we have solved the issues with the 404 calling problems. But I will need more feedback. We have not had any support requests regarding these problems for a while. Furthermore We do not block any calls to the lower 48 states regardless of high cost etc. All other numbers can be reached by dialing 011+the number.
As far as Google voice latency, we are using a different carrier than Google Voice so the calls from Google Voice go over the PSTN before they get to your Vestalink account. The best way to solve this latency would be to port your number to Vestalink.
I would like some more feedback regarding the g711 vs g729 codec. The g729 codec is what we use standard on our ht701 devices because it uses significantly less bandwidth (8kb). In low bandwidth connections, like dsl you might have a choppiness issue with g711. However g711 will provide you with significantly better call quality.
Should this be a configurable option in the Vestalink account settings?
I think that would be a definite yes if it can allow for better call experience, ;D with a notation that the setting is for higher bandwidth connections. My opinion is not based on a real understanding these codecs, though I am aware of coding and decoding in other audio situations.
It would be greatly appreciated if there were a way to pick the preferred Audio Codec on the Vestalink Account Settings page. I suggest a short note or hint of the Pros and Cons between picking G729 and G711 along with a check box to select either G729 or G711 as the preferred Audio Codec.
For now, the more experienced users that manage their Obi devices on OBiTALK can use the "Expert Configuration" Tool to disable G729. Also those that manage their Obi devices manually via direct web access can disable G729 to insure the use of G711. Those that have lower band width should stick with G729.
This codec information seems so valuable. I'm really glad I stumbled onto this discussion. It might be valuable to a bunch of us using OBi's. It's little tweaks like this one that can make a big difference in call quality and satisfaction. I'm in the process of going through the headache of re-purposing some high-end interconnects in my surround system that I know will only be a small tweak, but that's what it's all about. Otherwise, just any ole gear will do.
Quote from: intelafone on April 04, 2014, 07:58:08 PM
Hi Everyone:
I appreciate the feedback. I believe we have solved the issues with the 404 calling problems. But I will need more feedback. We have not had any support requests regarding these problems for a while. Furthermore We do not block any calls to the lower 48 states regardless of high cost etc. All other numbers can be reached by dialing 011+the number.
As far as Google voice latency, we are using a different carrier than Google Voice so the calls from Google Voice go over the PSTN before they get to your Vestalink account. The best way to solve this latency would be to port your number to Vestalink.
I would like some more feedback regarding the g711 vs g729 codec. The g729 codec is what we use standard on our ht701 devices because it uses significantly less bandwidth (8kb). In low bandwidth connections, like dsl you might have a choppiness issue with g711. However g711 will provide you with significantly better call quality.
Should this be a configurable option in the Vestalink account settings?
I definitely think this should be an option in the Vestalink account settings. Many of us have plenty of bandwidth to deal with the increased demands of the g711 codec.
I am thinking that Vestalink should actually default to g711, because that's the only codec you can use with Google voice. So if you are GV user you will already have the bandwidth necessary for using g711. g711 sounds a lot better than g729. For now I am making g711 the preferred codec for Obi devices, we will implement a bandwidth saver option in the account settings that sets the default to g729. Thoughts, suggestions? Thanks
I'm OK with either codec being the default, but I really like having both codecs available; the G729 seems to work better for me than G711 (based on calls made using Vestalink (G729) and GoogleVoice (G711)).
--Tony
If the preferred codec is configured at the Vestalink end, how would this work for users with multiple SIP clients?
I use a softphone app on my phone which defaults to G.729 when on 3G/LTE, and OPUS, G711 when on Wifi. While at home when using my Obihai, I would it like to default to G711.
How can you tell which CODEC was used for a particular call?
There is probably some history that I am not aware of that others will point to, but if you are in the call status section of OBiTALK expert when making or receiving the call you will find the codec in the details.
Via accessing the OBi device "admin" page -OR- via OBiTalk "Expert Configuration" Tool.
Status > Call Status
Number of Active Calls: 1
Call 1 Terminal 1 Terminal 2
Terminal ID PHONE1 SP1
State connected connected
Peer Name
Peer Number **113036391111 13036391111
Start Time 10:57:30 10:57:30
Duration 00:00:02 00:00:02
Direction Outbound Outbound
Peer RTP Address 54.186.217.35:18040
Local RTP Address 192.168.x.xxx:16626
RTP Transport UDP
Audio Codec tx=G711U; rx=G711U
RTP Packetization (ms) tx=20; rx=20
RTP Packet Count tx=148; rx=148
RTP Byte Count tx=25456; rx=25456
I've just about had it with Vestalink. This AM, all of my incoming calls are going to their voicemail service (which is disableed in the GUI). Callers hear: "You cannot leave a message because the mailbox has not been set up".
Because I'm still using GV as a forward, all calls are intercepted by this message and no one can get a hold of me. For now, I've disabled the Vestalink forward in GV.
Further, on the Obitalk page, the device shows Unauthorized. I verified that all the settings were correct, still same. So I ran the auto configuration option. Now it says "Service not configured".
I've sent them an email, but this is pretty much the last straw. Between the excessive latency on GV forwarded calls, to the complete unreliability of "call has been rejected by the service provider" to now this latest "Unauthorized" error - I've about had it.
FWIW, my dad's box is also showing the same symptoms - so this is definitely on their end.
"Register Failed: 401 Unauthorized" under the status page of the Obitalk.com setting page. So frustrating. Power cycled the obi, rebooted it, still the same error.
I have 2 x 110 boxes. The one I tried to reconfigure using the "auto-configure" script on Vestalink's site is now showing "Service Not Configured". I've tried deleting the SP1 provider and redoing it manually, and get the same error.
Anyone else having issues?
My Obi service is down. It's not Vestalink or Future Nine. Both are up but it is Obi.
Quote from: erkme73 on April 09, 2014, 06:28:03 AM
"Register Failed: 401 Unauthorized" under the status page of the Obitalk.com setting page. So frustrating. Power cycled the obi, rebooted it, still the same error.
I have 2 x 110 boxes. The one I tried to reconfigure using the "auto-configure" script on Vestalink's site is now showing "Service Not Configured". I've tried deleting the SP1 provider and redoing it manually, and get the same error.
Anyone else having issues?
I heard Vestalink was down again this morning but I don't know how long it lasted. If that was during the same time period you were trying to configure your Obi it might have been part of the problem.
Quote from: cluckercreek on April 09, 2014, 06:35:19 AM
My Obi service is down. It's not Vestalink or Future Nine. Both are up but it is Obi.
Perhaps you could be more specific on your issue. My Obitalk connection seems to be working.
EDIT: I just tested the Obitalk network. No problems calling. No issues logging in to the web control panel. I did experience a problem with the forum and portal last night but it did not appear to affect any calling feature that I am aware of.
The light is off on the Obi and both services state Register Failed. The IP configuration page shows the same. I just checked as I'm typing this and one of the services has registered. Like others here and on DSLreports, Obitalk was down as well.
Quote from: cluckercreek on April 09, 2014, 06:42:39 AM
The light is off on the Obi and both services state Register Failed. The IP configuration page shows the same. I just checked as I'm typing this and one of the services has registered. Like others here and on DSLreports, Obitalk was down as well.
Most functions of the Obi devices should continue to work even if the Obi website completely died. Only Obi to Obi calling via Obitalk and remote administration would be affected. Connections to future9 and Vestalink are direct connections between the device and their respective servers.
And I'm able to make OBI to OBI calls just fine this AM - in fact, it's the only way (short of cellular) that I can call my pops.
Sorry for the delay in replying, but YES, I definitely think Vestalink should default to g711, as most other VoIP providers do also I believe (and what GV uses). Then offer the "Bandwidth saver" option for those with slower connections so they can go to g729 if needed. I believe some other providers offer a setting like this too.
Thanks!
Quote from: intelafone on April 06, 2014, 10:47:10 AM
I am thinking that Vestalink should actually default to g711, because that's the only codec you can use with Google voice. So if you are GV user you will already have the bandwidth necessary for using g711. g711 sounds a lot better than g729. For now I am making g711 the preferred codec for Obi devices, we will implement a bandwidth saver option in the account settings that sets the default to g729. Thoughts, suggestions? Thanks
Realize I'm a bit late to the thread, but I'll offer performance comments generally similar to those here. My outbound call quality and performance are good and consistent. Inbound call quality is a different matter. I am forwarding from GV, and experiencing fairly substantial inbound latency that I realize likely cannot be overcome short of porting my number from GV, and I"m not yet prepared to do that.
Have also noted that the G711U codec is the default on the outbound test calls I've made.
Presently, the Vestalink website is down, so that never leaves a customer with a warm-fuzzy :( Can't check account status, minutes used, etc.
Vestalink users should be aware that they do have a Twitter "status" account, @VestaLinkStatus. It isn't used often, but they tweeted an "All systems normal" message about 12 hours ago, so I have to assume the website being down is a new issue.
Google Voice had it's strong point, it being free, but I never found it to be an outstanding service. I got what I paid for and was happy not to pay a home phone bill for about year and half, but I found that porting out my number to Vestalink was a nice step up. None of these VoIP providers is perfect, but I think any one of them will provide an improved experience over using GV, for not a lot of money. Vestalink definitely works better after porting, rather than spoofing your GV number.