Device not registered

[r111]

Service has been mostly down and occasionally up for me the last 48 hours. When I can make a call, audio quality is poor. DSL Speedtest shows internet bandwidth is good. Voipo reliability is starting to come into question with me. I have periodic outages, log tickets, get same advice to reboot, port forward, etc.

[VOIPoTim]

Service has been mostly down and occasionally up for me the last 48 hours. When I can make a call, audio quality is poor. DSL Speedtest shows internet bandwidth is good. Voipo reliability is starting to come into question with me. I have periodic outages, log tickets, get same advice to reboot, port forward, etc.

It's pretty rare that we have issues like yesterday. All those issues were cleared up yesterday morning though.

If you're having issues constantly, you may have a bad connection to VOIPo or an incompatible router. Open a ticket so it can be addressed.

[dcooper]

Today, I went to make a phone call, but had no dial-tone on line1, but line2 did. I have a cordless base station plugged in to line1 and a plain touch-tone phone on line2, just in case... I have had the cordless set for years. I was using T-Mobile 'at-home' for two years, and switched to VOIPo in Jan/Feb of this year The only difference is the addition of the pots on the second line, just because I could.

I am connected to Verizon FIOS and when I switched to VOIPo I had to place the ATA on a port setup as a DMZ host This is for my home phone.

I work from home and use RingCentral and Cisco Communicator IP SoftPhones on my desktop and laptop and have for years with no issues, and no special router/network settings. I opted to try VOIPo instead of getting another $4.99 line from RingCentral because I was thinking of eventually cancelling my $9.99 incoming 8xx number which would then cause me to lose my access to $4.99 full function lines.

That is just to give a picture of what I have and that everything is stable, except the VOIPo line.

This time when I realized that I had problems, I did look at the devices screen and saw that there were two lines on the screen. These had ports 5060 and 5061 assigned. The two line lights were alternately blinking instead of being dark and only lighting when 'in-use'.

After a power-cycle of the ATA, the devices screen showed four lines with the same date/time. Two each for the 5060/5061 ports. The phones then appeared to work for outbound calls, but when I called in from my cell, the phones rang, but when we answered line1, there was silence and line2 kept ringing. I am certain that it would have gone to VM if I had not hung up.

When we did make a successful outbound call, both line lights blinked together instead of the active line being solid. When not in use, the blink alternately.

Currently we do not seem to be receiving inbound calls. At least they do failover to VM.

More later when
I have more time to investigate.

[r111]

It's pretty rare that we have issues like yesterday. All those issues were cleared up yesterday morning though.

If you're having issues constantly, you may have a bad connection to VOIPo or an incompatible router. Open a ticket so it can be addressed.

Thanks for replying to my issue. I've had outages lasting over 24 hours almost every month since I started using VOIPo. I've opened a ticket each time. In order to eliminate any router issues, I've put the (VOIPo supplied Linksys pap2t) ATA in the router's DMZ. I've sent voipo-trace files to support on 2 occasions. No issues are indicated. I have AT&T DSL with 2.5 mb down and .5 mb up. I have VOIPo at another location and it is rock solid. So I am wondering if:
- AT&T is deliberately interfering with VOIP traffic
- The Linksys pap2t VOIPO provided is faulty (the ATA at my other location is a Linksys rt31p2)

Here are the ticket numbers I've submitted over the past few months:
ZVN-261858
CPT-390761
GPR-135680
TED-658832
ZHD-143435