Vestalink stopped working
Codesmith:
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.
riptcity00:
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.
BigJim_McD:
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.
erkme73:
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.
Codesmith:
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."
Navigation
[0] Message Index
[#] Next page
[*] Previous page