Vestalink stopped working

<< < (15/16) > >>

dircom:
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

cluckercreek:
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.

dircom:
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

theshiv:
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?

dircom:
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.

Navigation

[0] Message Index

[#] Next page

[*] Previous page