Cancel the port ASAP and wait to seem if Ooma can resolve their carrier issues(IMO). Keep testing Ooma and then have your number ported if things improve or return the device and get your money back. I know that means paying Vonage for another month or two but if Ooma can not fix their problems (or if these problems are a sign of bigger problems for Ooma) you will at least have your number at a provider that is reliable.Willywnkah wrote:I am porting my number from Vonage - slated to be complete before Christmas. Hopefully the issue will not follow with the change.
I am calling from (815) xxx-xxxx (my Ooma VoIP phone line) to (773) 445-xxxx (an AT&T landline phone number). The problem seemed to begin around the last several days and I have emailed Ooma support today with the dates, times, phone number, and durations. Interestingly I can call the same number with using my cell phone service without a problem.
My problem only existed when dialing 10 digits but not seven. I suggest trying 7,10, & 11 digit dialing for your calls. This allowed me to eliminate my router or network as a problem.
AT&T (my previous carrier) always required me to dial all 11 digits even for local calls, maybe it is different for Ooma. I have always dialed all 11 digits for all my calls and I can hear the other party when I dial other numbers. The problem with being unable to hear the other party (at least in my case) seems to be isolated to a specific phone number in (773)-445 which is outside of my (815) area code.RyanGambrill wrote: My problem only existed when dialing 10 digits but not seven. I suggest trying 7,10, & 11 digit dialing for your calls. This allowed me to eliminate my router or network as a problem.
I emailed ooma support yesterday with numbers and timestamps and so far I am happy with their prompt reply. They have escalated the support ticket and are currently looking into the matter.Michelle539 wrote:Call ooma. I did and they had me change a setting. It is fine now.