More problems

[ctaranto]

I have had zero issues through all this. I hate to say things like this, because I'm basically dooming myself. But just want to post to say things aren't disastrous for everyone.

[burris]

I'll risk sharing any doom, but I've been OK here as well...

[MisterEd]

My line 1 down again this morning .... vPanel shows "no devices registered" yet my Line 2 is working fine.

The problem is that since my initial "startup problems" everything has been perfect since Mid February now all of a suddent things are getting flakey and I have to monitor my ATA all day. Telephone service should be something you should never have to think about like turning on your lights.

[ctaranto]

Unfortunately, if you want "stable" phone service, you may need to go back to POTS. They've had what, 100 years, to work out the kinks?

With VoIP, as you know, there are many areas that can affect the connectivity, some you can control, some you can't.

What is your overall network topology, ISP, and, if cable, cable modem?

[Russell]

My line 1 down again this morning .... vPanel shows "no devices registered" yet my Line 2 is working fine.

The problem is that since my initial "startup problems" everything has been perfect since Mid February now all of a suddent things are getting flakey and I have to monitor my ATA all day. Telephone service should be something you should never have to think about like turning on your lights.

If you have a cable modem, can you connect your VOIPo box (assuming it has router functionality) directly to the cable modem and see if your problems persist?

I can sense your frustration. Service for me worked perfectly for months with VOIPo. However, recently I've noticed flakiness and have started forwarding ports. Unfortunately, our call volume has decreased some - so I can't tell if all is well at present.

[VOIPoTim]

If you have a cable modem, can you connect your VOIPo box (assuming it has router functionality) directly to the cable modem and see if your problems persist?

I can sense your frustration. Service for me worked perfectly for months with VOIPo. However, recently I've noticed flakiness and have started forwarding ports. Unfortunately, our call volume has decreased some - so I can't tell if all is well at present.

Just out of curiosity, did this happen around the time East had issues (we haven't moved people back to East yet...just no reason to). I'm curious if you and the handful of uers reporting issues had a bad connection to central?

Things have just been very quiet in general so it's odd that a handful people are still reporting issues, so maybe there is something in common like that.

[Russell]

Just out of curiosity, did this happen around the time East had issues (we haven't moved people back to East yet...just no reason to). I'm curious if you and the handful of uers reporting issues had a bad connection to central?

Things have just been very quiet in general so it's odd that people are still reporting issues.

Could be - the time line in my mind is a little fuzzy right now. I know I was on East for a long long time with excellent service.

[ctaranto]

I was on east until the herd was moved to central recently. I've been on central since and although the ping times to central are longer (for me), I don't want to mess around with something that's working...

[MisterEd]

Unfortunately, if you want "stable" phone service, you may need to go back to POTS. They've had what, 100 years, to work out the kinks?

With VoIP, as you know, there are many areas that can affect the connectivity, some you can control, some you can't.

What is your overall network topology, ISP, and, if cable, cable modem?

While I agree mostly with that statement (after working C/S, LNP & Tech support for Vonage for 18 mos and had their service for 4 years I became well aware of it) I don't fully agree with it.

I understand there can be "issues" but how many are too many and what KIND are acceptable before questioning reliability? In the 1 1/2 years I worked for Vonage we had 2 full network outages, one lasting many hours and one about 1 hr. Call center sms was down as well yet calls kept coming in to the building so they went into the phone system and 10's of thousands of calls were queued up for hours. People just didn't give up. One time there was a fire warning in the building and 600 reps left and they didn't put an intercept on the incoming calls! With 2,000,000+ lines at that time you can imagine what went on.

In my last 2 years with their phone service after I left them I never had any problems except an occassional echo type of issue which I can accept.

Anyway, how much is too much and what TYPE of issues are acceptable. Those who use "how much one pays" as a reason for more reliable service are way off base.

To answer your question:
I have Fios 25/15 service (no modem), Buffalo router w/DD-WRT and the PAP2 plugged directly into the router. My physical network is not a problem (been building them for 25+ years so I have enough knowledge to not get in trouble there). Voipo started out messy for the first couple months then was perfect for the next 3 after replacing the Fios Actiontec router with the Buffalo/DD-WRT on 2/15 then problems started a few days ago. NOTHING has changed on this end and the only change in over a year was swapping the Actiontec for the Buffalo.

[ctaranto]

So now my question is: What makes yours (and select others) connectivity flaky, and mine (and select others) not?

If I was having flaky service, I'd be as frustrated, if not more, as you. I did have flaky service, but was due to a bum PAP2T. It worked for about a week, then started randomly losing re-auth. One line, then the other, then both, then neither. It would change every 5 minutes. My wife was beyond frustrated and wanted to just get POTS. I'd spend every night for hours trying different things (routers, firmware, settings, etc).

I plugged in another PAP2T, and now it's solid.

Not saying it is your PAP2T, but maybe?