Vestalink stopped working
dircom:
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
Dixon:
Still not working with the Obi 110. Working with Bria softphone.
Register Failed: No Response From Server
Dixon:
NVM. IDK how my VPN keeps getting turned on.
Edit: I know how. Start with WAN. Noob mistake from a senior admin.
reltub:
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.
simpleAnswers:
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......
Navigation
[0] Message Index
[#] Next page
[*] Previous page