Suddenly my Vestalink account quit working this afternoon, and I can't make it work??
Tried factory reset on the Obi100, then the Vestalink config, easy setup. Done this a couple times, but no dice.
Anyone else having issues?
Mine is dead too. I tried eveyrthing
Obi portal says Register Failed: No Response From Server
Vestalink shows devices connected.
Same...mine says "Register Failed: 401 Unauthorized (server=xxxxxxxxx:8891; retry in 28s)"
Pretty goddamed annoying, if you ask me. I think this has been happening randomly for a while, since a lot of calls are being ended up in my Google voice voicemail because Obihai isn't ringing at all.
Yep. My Vestalink connection just died too. :-[
Was working earlier today during a short call with my wife around 3:30pm Pacific. Dead when I tried again around 4:30pm Pacific.
First few outgoing test calls resulted in "The number you dialed XXXXXXXXXX was rejected by the service provider. Error 407."
Now, outgoing calls result in [SUPER LONG PAUSE] [3 ASCENDING TONES] "The number you dialed XXXXXXXXXX has not received a response from the service provider."
Incoming test calls go to my Vestalink voice mail. (I don't forward from Google Voice anymore.)
Ugh...
I had tried the restart my router and Obi202 thing first, then came here to see if others had this issue right now. Well, guess I'm not the only one. :-\
So what's up Vestalink? I pre-paid for the 2 year unlimited less than a month ago. Hope it's just a temporary glitch.
This happened to me yesterday morning. I posted about it. I thought it was my error. But it wasn't apparently. I emailed support and they replied withing 90min. It was working by then. But they only have email and chat support M-F.
Can anyone email Ryan?
Yep, down here too. Unfortunately Vestalink call forwarding doesn't work so I can't send calls to my cell phone.
At the beginning, I found the service pretty reliable...these days it has been flakey as all hell. I'm not sure if I want to drag these kinds of issues for 2 years.
Why does it says "Device: OBIHAI/OBi110-1.3.0.2824
Status: Connected
Contact: sip:xxxx@xxxxxxxxxx:xxxx
"
on my Vestalink account page? It's clearly not connected.
It would be nice for them to do a little damage control and let us know what's happening. It would go a long way in helping us keep the faith.
I sent in an email to support. I guess everyone else has as well. :-\
I've got an error too ...... and no phone service.
Any chance all of us with issues have manually configured OBi's?
Nope, auto setup here.
Good to go!
It's back!!!! Now a little explanation would be good.
I really hope they address these downtimes, because I'm getting a bit annoyed when I see a bunch of voicemails sitting online when I know the phone never rang in the first place.
I noticed my service was down around 1930 EST and I see it is back up after about 2 hours down.
This reminds me of living in the country, when phone service would go down randomly.
At least we could see that the intelafone server was up the whole time.
I really hope this doesn't develop into a trend, I just convinced my very skeptical wife that we could save a bunch by moving to an obi device plus a voip provider...
Ryan replied:
Our central SBC and database has crashed under sudden load. It has been scaled up to support the influx of customers right now. The service is back up and running. We will continue to monitor and auto-scale services to support the load.
Please let me know if you are still experiencing issues. Thanks
Just got my update from Vestalink and give a thumbs up for updating us! ;)
Still down for me.
Quote from: Dixon on March 08, 2014, 07:01:44 PM
Still down for me.
Don't go on what ObiTALK is reporting. My still says Register:Failed but the service is working.
I'm not. Can't make calls.
Quote from: reltub on March 08, 2014, 06:35:50 PM
I noticed my service was down around 1930 EST and I see it is back up after about 2 hours down.
This reminds me of living in the country, when phone service would go down randomly.
At least we could see that the intelafone server was up the whole time.
I wrote too soon. The obi device is registered with the intelafone server, but I am getting 404 error messages when trying to place outbound calls, so my service remains down.
Thanks to Dixon, who forwarded Ryan's answer.
I'm still in contact with Ryan.
I am getting:
Retrying Register (server=54.200.193.145:5060)
Thought I was up, but still getting 404 message when dialing.
Mine was working. I came back to the forum and saw the replies and thought , what? I then checked it and same error message of 404. Hmm.
getting "The number you dialed XXXXXXXXXX was rejected by the service provider. Error 404."
If I dial my # it just rings and rings, website does not show call
Quote from: dircom on March 08, 2014, 07:56:02 PM
getting "The number you dialed XXXXXXXXXX was rejected by the service provider. Error 404."
If I dial my # it just rings and rings, website does not show call
I Tweeted Intelafone about the 404's. You might want to follow them @intelafone I asked Ryan about using Twitter to update users and he said definitely.
what about a status page on the website?
that makes more sense to me
I am not happy about this, no updates, no service
failover not working
my GV still works, perhaps it is time to investigate SipSorcery
EDIT, started wkg about 2am Sunday
Quote from: dircom on March 08, 2014, 08:16:45 PM
what about a status page on the website?
that makes more sense to me
I am not happy about this, no updates, no service
failover not working
my GV still works, perhaps it is time to investigate SipSorcery
To be fair, vestalink has responded to
my email, even if the reply was a form letter.
This disruption is a headache for me because I ported my landline number over to obivoice.
So, although I can make outgoing calls through other sip providers (I use
diamondcard and localphone as fallbacks), incoming calls are a no-go.
I hope vestalink is able to get its growing pains under control.
This happened to me yesterday as well. I had performed some recent configuration changes in Obitalk (static IP changes and Mango Dial Plans) and thought that these had caused my inability to make call/receive calls. Vestalink website showed that I was online and connected. Obitalk showed me as Registered. But got the error 404 when dialing out and a busy signal when dialing in.
So I reset to default obitalk configurations and reboot. No dice.
Then I followed the instructions here: https://intelafone.desk.com/customer/portal/articles/1425037-fixing-the-obihai-adapter-%22error-400%22
This worked for me! Hope this helps someone else.
That refers to error 400
If their tech support wants the post to refer to error 40(0-9), then they should do so
also it refers to "when attempting to make an outbound call"
In my case it was unable to dial in or out
Still not working with the Obi 110. Working with Bria softphone.
Register Failed: No Response From Server
NVM. IDK how my VPN keeps getting turned on.
Edit: I know how. Start with WAN. Noob mistake from a senior admin.
Quote from: spree502 on March 09, 2014, 08:03:17 AM
Then I followed the instructions here: https://intelafone.desk.com/customer/portal/articles/1425037-fixing-the-obihai-adapter-%22error-400%22
This worked for me! Hope this helps someone else.
My guess is that what you witnessed was a coincidence.
The support email that I received makes no mention of this work-around. And a scan of that port 8891 shows it is closed, so vestalink may be trying to be clever in allowing selective access based on ip addresses. If so, that will likely cause grief for most home connections without a static ip address.
Either way, with no changes on my end, my service was back up this morning.
Quote from: reltub on March 08, 2014, 09:01:11 PM
This disruption is a headache for me because I ported my landline number over to obivoice.
......I hope vestalink is able to get its growing pains under control.
Only got yourself to blame for that one I'm afraid. You ported out your number to a new startup, anyone who does that can't complain if the service is down. The call forwarding worked just as well and gives everyone enough time to evaluate before porting.
I for one will never port my number to any provider until GV shuts down for good. Any new provider could varnish tomorrow or have issues, and regardless of what they say it will still be a pain to regain control of the number. Besides no operator has the infrastructure of big G.
I have Vestalink and as much as I like them I'm still looking at other GV options to see what would be permanent. I won't stop until I get a solution that uses GV for in and out calls.
Bottomline is since my number is still with GV I can bypass issues with Vestalink until they figure out what they did......
Good evening:
Yesterday an influx of customer calls took down our database system.
More instances were deployed and the problem was resolved around 6pm PST. Intermittent issues calling east coast numbers continued until about 8pm PST.
All issues have been resolved.
We have now implemented better monitoring tools and have a system status page so customers can get the information they need in case of a service disruption.
Please visit http://status.vestalink.com for up to date system information if you experience calling trouble.
Quote from: intelafone on March 09, 2014, 07:36:26 PM
Good evening:
Yesterday an influx of customer calls took down our database system.
More instances were deployed and the problem was resolved around 6pm PST. Intermittent issues calling east coast numbers continued until about 8pm PST.
All issues have been resolved.
We have now implemented better monitoring tools and have a system status page so customers can get the information they need in case of a service disruption.
Please visit http://status.vestalink.com for up to date system information if you experience calling trouble.
Excellent on the status page. Now, I only have to figure out what I'm looking at. ;D There is a link to follow the status on Twitter for updates.
Yes, thanks for the page, now tell us what it means ???
If anybody is having the error 400 message do the following:
Go to https://www.vestalink.com/byod.php
but DON'T do the top portion about putting in your IP address since it will not work. Leave this window open since we'll need the info from the table.
open another tab or window on your browser and go to the site:
https://intelafone.desk.com/customer/portal/articles/1382461-advanced-obi-configuration
follow the instructions. If the obitalk site does not list your device, reset your device by dialing ***81 and wait at least 2 mins and see if it sees your device and continue with the instructions.
Hope this helps someone. I spent a lot of time trying to make it work.
One more thing, in the table that you see when going to the link
https://www.vestalink.com/byod.php.
The values for Service Provider Proxy Server Port should be 8891 and for
Outbound Proxy Server Port should be 8891
Quote from: arvinp on March 11, 2014, 04:46:33 AM
One more thing, in the table that you see when going to the link
https://www.vestalink.com/byod.php.
The values for Service Provider Proxy Server Port should be 8891 and for
Outbound Proxy Server Port should be 8891
Port 8891 has been suggested by Vestalink as an alternate to 5060. But it is not the standard configuration and not mandatory for use.
5060 was not working for me until I read the following on Vestalink's site:
"One of the errors Obi adapter users may experience when configuring their equipment for use with our service for the first time is an Error 400 when attempting to make an outbound call.
The easiest solution to this error is to use port 8891 instead of 5060 when entering the SIP credentials into your device from the Softphone/BYOD tab of the Vestalink web portal".
Doing what I wrote in my previous post and changing to 8891 instead of 5060 started working for me. Thanks. :)
Mine never stopped working on 5060.
Good on all of you who are back up. I'm not. Getting "Service Not Configured" on the 110 box I configured with the auto-configuration page. It was showing "Register Failed: 401 Unauthorized", so I thought, what the hell... let's try that. I've since deleted the SP1 profile and manually entered everything (including 8891 v. 5060) and still shows Service Not Configured.
The other 110 box, I haven't touched. It still shows "Register Failed: 401 Unauthorized". I'm going to manually change the proxy settings to 8891, but suspect that's wishful thinking as well.
I've power cycled both boxes, and it made zero difference.
ETA: as suspected, changing the manually configured 110's ports to 8891 did nothing to change the "Register Failed: 401 Unauthorized" error. All calls are rejected by the service provider.
Quote from: erkme73 on April 09, 2014, 06:37:59 AM
I've since deleted the SP1 profile and manually entered everything (including 8891 v. 5060) and still shows Service Not Configured.
I think the primary reason they use 8891 is because routers like the 2wire tend to choke on 5060. If a port was working for you it
should continue to do so unless you change hardware or firewall settings. I hope they work out their problems soon.
Everything has been working great until this morning. Mine is showing the Register Failed: 401 Unauthorized too. I tried 8891 and 5060 and it makes no difference. I have CallCentric set up on Sip2 and it is still working.
I was curious. Vestalink provides the failover that forwards the calls to another number. Is that still working?
both mine and a friend's service is out also. all morning so far. I tried all the suggestions.
I've reset everything from scratch manually and auto setup from vestalink.
Vestalink will NOT configure the obihai without failing. I hope this gets fixed quick or me and a whole lot of other people will be moving on to another service quickly.
Quote from: giqcass on April 09, 2014, 07:48:19 AM
I was curious. Vestalink provides the failover that forwards the calls to another number. Is that still working?
It never has worked for me. It didn't work during the previous Vestalink outage nor another time when my Obi was offline. I sent an email to support asking in what conditions the failover does work but never received a reply.
That was one (of many) reasons I moved on to PhonePower who (so far) has been rock solid and reliable. Me thinks Vestalink is still experiencing some growing pains.
I am down here as well this morning. I don't know for how long its been out. I mostly use my mobile phone, but still wanted to use the Obi for e911. Getting #407 error "service rejected by provider". Can't really rely on making an emergency call with such an unreliable service. This has been pretty unacceptable so far for the few weeks I have been with Vestalink.
I'm getting the same message with vestalink this morning on my obi 202: Register Failed: 401 Unauthorized. It's the first time it's happened with me.
Same problem here. I noticed that on the Vestalink status page the US mid graph is down. Maybe related. I'm in the mid area.
Vestalink is working for me again as of 10:45 am Mountain Time.
Well, the service came up at about 1:00 PM local time here in the East, then promptly went down again about two minutes later. Now all indicator lights on my Obi 100 are on, but I am getting a 404 error. I feel pretty stupid for giving this company my money.
I don't understand why they have a status twitter feed https://twitter.com/VestaLinkStatus when they choose to stay mute with their customers about this issue. Plenty of people asking what's going on with absolute silence from Vestalink on all fronts.
i am up also but for how long? The lack of communication when this happens will lose more customers than the actual downtime.
Quote from: gannicus on April 09, 2014, 09:49:04 AM
Vestalink is working for me again as of 10:45 am Mountain Time.
Vistalink stopped working for me today as well.
1) Checked my internet, power cycle all equipment.
2) Checked vestalink's status http://status.vestalink.com
3) Checked ObiTalk ... new error message on vestalink service
Deleted the service, re-entered the information exactly as before and everything is fine.
I've had so many internet connectivity issues over the last 48 hours that I won't even venture to guess what caused the problem. (Hopefully the new cable modem solved all that).
But deleting and then readding the service is what fixed it.
Looks like they posted an update on their twitter page:
Vestalink@VestaLinkStatus
We experienced a database problem this morning that prevented logged out users from logging back in and making calls, the issue is resolved.
Just an observation.
It appeared to me that many Vistalink users service was down during the morning. My Vestalink service went down on my OBi202 sp1 and I hadn't logged out. I suspected that it was down because it was unable to Re-Register.
OBi202 - SP1 Service Status
Status Register Failed: 401 Unauthorized (server=54.200.193.145:8891; retry in 114s)
But Vestalink continued to display that my
OBIHAI/OBi202-3.x.x.4330 sip:2xxx@71.33.164.199:5080 connected.
OBiTalk was also down much of the morning. I had to use OBi202 admin webpage to manually switchover to my backup VoIP service provider on sp2. I used Google Voice to switchover the call forwarding to my backup service until the Vestalink was back up and stable.
Glad to know it's not just me unable to get to Obitalk.com. Talk about frustrating. You want to troubleshoot the Vestalink issue and see whether the box is displaying registered, but can't get on first base with OBi's site being down - as were the forums.
I realize you can log into the IP address (which is what I was doing), but that's no consolation for those who are not as proficient with the interface.
I wonder how much of this has to do with the Heartbleed OpenSSL patch thing that's been all over the MSM. Much of "encrypted" https traffic was apparently wide open to exploitation for nearly 2 years. All the certifying authorities have to apply patches and re-issue certificates. Seems like that alone could be gumming up the system.
Here is the explanation from their twitter and status page ...
"We experienced a database problem this morning that prevented logged out users from logging back in and making calls, the issue is resolved."
Quote from: Codesmith on April 09, 2014, 04:04:56 PM
Here is the explanation from their twitter and status page ...
"We experienced a database problem this morning that prevented logged out users from logging back in and making calls, the issue is resolved."
The problem is that they posted this AFTER the issue was fixed. There was no communication via email, their status page or their twitter feed acknowledging there was a problem while it was ongoing. This caused many users to try all kinds of self remedies thinking that there was something wrong on their end.
Already scoping out my next move. I am giving them one more shot, but I do not have high hopes for Vestalink being able to handle it when GV pulls the plug in a few weeks. They are very good at presenting a slick marketing effort to get people to sign up. I hope they are putting as much effort in not being caught by surprise again.
Quote from: aopisa on April 10, 2014, 08:38:32 AM
Quote from: Codesmith on April 09, 2014, 04:04:56 PM
Here is the explanation from their twitter and status page ...
"We experienced a database problem this morning that prevented logged out users from logging back in and making calls, the issue is resolved."
The problem is that they posted this AFTER the issue was fixed. There was no communication via email, their status page or their twitter feed acknowledging there was a problem while it was ongoing. This caused many users to try all kinds of self remedies thinking that there was something wrong on their end.
Already scoping out my next move. I am giving them one more shot, but I do not have high hopes for Vestalink being able to handle it when GV pulls the plug in a few weeks. They are very good at presenting a slick marketing effort to get people to sign up. I hope they are putting as much effort in not being caught by surprise again.
Gosh, lets hope they are. I was pretty certain I wanted to use Vestalink as soon as my GV no longer works. Now not so sure...
Anyone else having trouble with Vestalink this morning?
I'm getting a "Register Failed: No Response From Server" from my OBI110
Quote from: S_in_Forum on April 15, 2014, 08:53:34 AM
Anyone else having trouble with Vestalink this morning?
I'm getting a "Register Failed: No Response From Server" from my OBI110
Just checked and mine is working. Where are you located? How long have you had the problem?
I'm in the East and having no problems with VL.
In the midwest.
Just rebooted everything (router, internet modem, and OBI110) - now working. Go figure . . .
Anyone having trouble with Vestalink? This morning my calls started going to the failover #, outgoing ok
rebooted obi, then reset Obi
now URI field is missing when I try and manually configure
waiting for Obi support to help
my other three SP's were working fine today
Someone reported this yesterday over on the GV forum, too. I can't imagine depending on this ITSP for service, given their history, and the plethora of better choices.
Except for two brief outages, my service has been working fine for over 6 months
Obviously a person hopes to get (at a minimum) what they paid for
We use 800-2000 minutes per month, feel free to suggest a better provider and the cost
What is hard for me to imagine is the people who were depending on GV for phone service
(especially the ones who ran a business)
also odd is that the URI field is missing in Obitalk.com
If I select Vestalink as a provider, URI field is missing
If I select generic, sometimes the URI filed shows up, then after I enter all the info, and go back in, it is gone
Despite having paid for a full year, I (and the members of my family that also signed up on my recommendation) jumped back to GV immediately upon the notice that it was officially supported again.
Vestalink was so incredibly fickle. I can't recall all the errors and excuses given each time I "chatted" with Andrew or whoever, but I had my fill of it. And the call quality - especially the inbound calls that were forwarded from my GV number to Vestalink were embarrassingly bad. Delays between callers was easily 1-2 seconds making conversations very frustrating.
Since moving back to GV, it's been 100% rock-solid, no delays, and call quality is at least 100% better.
Glad you have had better luck with it, but me, my father, my father-in-law, and brother, were all terribly disappointed with ObiVoice/Vestalink.
I might have had better luck, because I did not forward any numbers to Vestalink, I ported my # to them.
and I have a solid internet connection
The features set is great, the only thing that has changed is native faxing has gone away (temporarily) I am told.
Regarding GoogleVoice: the lack of reliable inbound caller ID was a deal breaker for my wife (using the CallCentric workaround for GV)
My problem seems to be with my Obi at the moment
I have had great service with Vestalink. The only issue really has been the MWI not working after several hours. For me that's not a biggie but an aggravation.
edit (user error) was entering an n instead of m as part of my credentials
I guess I was blinded my the fact that URI field in my original configuration is not currently appearing in Obitalk
Obi support says to use Generic Provider, and the URI field is gone for some reason
but after I entered the correct password for SP1, it started working again
even though my original Obi configuration and Vestalink's BYOD setup instructions show the URI field
I'm having an issue with Vestalink, and I'm wondering if anyone else is having the same.
I ported my number over from GV back in March, so GV is no longer part of the equation. However, quite often when someone calls me my phone doesn't ring. I know they call because I get an email with the voicemail message. Also, the phone quality is not constant. There are times when I'm talking to someone that my voice becomes all garbled to them, or I drop off completely. This has happened to people on different phone services, so it must be coming from my end.
My ISP is Comcast with speeds around 100Mbps. I ensured that the SIP ALG feature on my Zyxel router was disabled, and after contacting Vestalink I followed their recommendation and re-setup my Obi device. The original problems are still persisting.
Anyone else experiencing the same or similar?
I also ported my # to VL. Today my wife told me calls going to the failover #. One of my GV #'s on SP3 was also offline, power cycled Obi, and all is well again.
bump ... I'm getting the dreaded "Register Failed: No Response From Server (server=54.200.193.145:8891; retry in 18s)" error.
I've rebooted the ObiHai and made sure my device is running the latest firmware (which it was).
Anybody else?