Anybody Having Trouble Today?

A friend just called me on my cell and said she had been trying to reach me all afternoon, but that both lines were busy -- not voice mail, but busy signals. We did not have DND enabled (and if we had, we would have sent calls to voice mail), and we weren't on the phone.

I then checked the phones, and everything seemed normal. I called myself from my cell, and both lines rang normally.

So I'm wondering whether anyone else noticed a problem with inbound calls today, or whether my friend was somehow misdialing?

As far as I know, all has been well here in South Florida...at least with the phone service.:rolleyes:

Well, I checked my call history, and all the calls appear there. Six to my primary line and one to my Add-on line. Strange. I submitted a ticket (ONP-952704). Could network problems cause a busy signal?

knock plastic ..... no problem here (NJ)

I had a lot of problems yesterday, but all slightly different than yours.

Damn, I spoke too soon! Over the last few days my LINE 1 has shut down 3 times and I have to reboot the ATA. Line 2 remains active. The first time it happened I ignored it, but it has happened twice more since I posted my earlier "no problem here" message on Friday.

Quote:

---

Originally Posted by MisterEd

Damn, I spoke too soon! Over the last few days my LINE 1 has shut down 3 times and I have to reboot the ATA. Line 2 remains active. The first time it happened I ignored it, but it has happened twice more since I posted my earlier "no problem here" message on Friday.

---

I too lost line 1 on Friday. Kept wondering what the issue was (I have several phones connected to line 1), since it occurred shortly after I used line 1 to check for voicemail and thought I may have done soemthing silly. Finally looked at the adapter and line 1 was dark. Reboot fixed the issue. All the time line 2 was functional.

And more problems. Tried making a call using line 1 all I heard was dead air and then I used line 2 and the heard the ring right away. The person at the other end asked me if I'd called a few minutes earlier and said they saw all zeros on their caller-id.

A few minutes later they called. I picked up but heard nothing. They tell me it went to my voice mail.

Sigh.

My config is the RT31P2 being directly connected to my UVerse router with UDP ports 5004-65000 forwarded to the RT31P2.

one line service here is OK today at 11:30A PT

Quote:

---

Originally Posted by MisterEd

Damn, I spoke too soon! Over the last few days my LINE 1 has shut down 3 times and I have to reboot the ATA. Line 2 remains active. The first time it happened I ignored it, but it has happened twice more since I posted my earlier "no problem here" message on Friday.

---

X2 - after no problems for a long long time, I am losing line 1 every couple days requiring a reboot of the ATA.

Quote:

---

Originally Posted by voipinit

X2 - after no problems for a long long time, I am losing line 1 every couple days requiring a reboot of the ATA.

---

Yes, my issues too were out of the blue. Rock solid service until this phase.

No increase in support here and everything's been running smoothly. If you guys have issues, open a ticket when you notice it so we can look at it for you.

Come back home and line 2 is dead (no light on the ATA). Make a call on line 1 and don't hear any ringing ... then I hear a hello from the other party.

This sure sounds like some router problems.
Maybe NAT or some needed ports not opening up.

Quote:

---

Originally Posted by burris

This sure sounds like some router problems.
Maybe NAT or some needed ports not opening up.

---

And, now both lines are lit up - I didn't do anything at all.

As previously mentioned: My config is the RT31P2 being directly connected to my UVerse router with UDP ports 5004-65000 forwarded to the RT31P2.

I'm not too familiar with UVerse, but if they use a router, as we know it, you may be double natting or conflicting something when you connect one router behind the other.

Have you checked with support. I'm sure by now that they have gained some experience with connecting those customers who have UVerse.

Quote:

---

Originally Posted by burris

I'm not too familiar with UVerse.

---

And that's a very good thing.

Quote:

---

Originally Posted by stevech

And that's a very good thing.

---

Bad experience I take?

I'm running Uverse at home and do not have any problems with numerous, numerous, numerous devices behind the UVerse gateway.

Russell:

I am curious as to if the recent experience could be related to any kind of updates and or network pushes that they have been doing recently.

In the last 24 hours I've noticed a couple of things (this could be completely coincidental, or irrelevant, however - just some observations).

Last night around midnight CST and PST (the reason I say this) is because it happened for me here locally in Houston at midnight and then later for a friend at midnight PST, there was a loss of connection for about 5-10 minutes.

Earlier today from three separate AT&T locations (UVerse & DSL) (in different geographic locations) Facebook.com was unaccessible.*

* Let me add it was specific to AT&T... I could access it from alternate networks.

Just some personal observations... not sure if there is any relevancy to your recent experience.

Quote:

---

Originally Posted by VOIPoTim

No increase in support here and everything's been running smoothly. If you guys have issues, open a ticket when you notice it so we can look at it for you.

---

Been there, done that. What can they do? If a line is down, then it comes up, when they get the ticket the reply is "everything is OK." Which it is. :)

I post problems here not with the intent to complain to VOIPo but just to see if anyone/everyone else in "the community" is having a problem. I realize there isn't much you can do unless there is a major outage.

Quote:

---

Originally Posted by MisterEd

Been there, done that. What can they do? If a line is down, then it comes up, when they get the ticket the reply is "everything is OK." Which it is. :)

I post problems here not with the intent to complain to VOIPo but just to see if anyone/everyone else in "the community" is having a problem. I realize there isn't much you can do unless there is a major outage.

---

Which is the same reason I don't create tickets and report here.

Tim: if you feel there is a point in creating tickets for something which is not reproducible, please let me know. It takes a certain amount of emotional energy to create the ticket for a problem which does not exist (e.g., my line 2 line not being lit for a certain period yesterday and being lit later) and if I'm going to be faced with an "everything is OK." response as described above, it's best for my sanity not to create the ticket :-).

Brandon, I do hear what you're saying. Both lines are lit up at the moment. However, the next time I find issues, I'm going to reboot all (the two described below) components.

To summarize my setup: the RT31P2 is plugged into the 2Wire with UDP ports forwarded. Plus my main computer is plugged in the RT31P2. Everything else on the network does wireless from the RT31P2.

Problems still persist. So this morning I decided to reboot all affected components: first turned power off to computer, RT31P2 and UVerse box. Let all sit for at least 2 minutes. Then powered up the UVerse box - it takes a long time to be ready. When it was, I powered up the RT31P2 and finally the attached computer, from which I'm typing this. If this doesn't get things working normally, I guess, it's ticket time. And, UDP 5004-65000 forwarded to the RT31P2 from the UVerse box.

On some calls I have a long silence and never hear any ringing - this is after the reboot described in the previous post. Opened RKQ-526057.

Quote:

---

Originally Posted by Russell

On some calls I have a long silence and never hear any ringing - this is after the reboot described in the previous post. Opened RKQ-526057.

---

I am experiencing the "no ringing" and 'choppy audio' and it's not the first time.

I've given up on submitting trouble tickets (over 40 since July 2008) - the issues always seem to reoccur.

My problems may be just mine, but they are problems. I didn't have them with my previous VOIP provider and I won't have them with my next.

Ken..

I don't work for VOIPo but have been involved since the beta days. Even in those beta days while helping test the service, I haven't experienced anything like what you describe.
Sure, I expect some blips along the way, VOIP you know, but even during the beta days, I still had no land line and for the most part, it worked pretty well.

As Tim mentioned a few times in the past, for whatever reason, a handful of users will just not work with certain providers no matter what. The vicissitudinous nature of VOIP I suppose.

Burris -

Don't take this personally. I was merely letting Russell know that I have also experienced the same issues. As a matter of fact, the next call I made after posting not only didn't ring, but returned to a dialtone - a first! Some calls made this morning are still not ringing.

I also have been with VOIPo since the pre-launch date; there were many difficult periods. I can't count the times we were without service and my wife wanted me to ditch the effort.

You have mentioned many times that you are satisfied with VOIPo's performance. Unfortunately, there are others that do have problems. As I said, "My problems may be just mine, but they are problems." The same is true for any other person reporting an issue.

For whatever reason, VOIPo isn't performing optimally for me. I think I've been more than patient, but it's time for a change.

Ken

Quote:

---

Originally Posted by KenH

Burris -

Don't take this personally. I was merely letting Russell know that I have also experienced the same issues. As a matter of fact, the next call I made after posting not only didn't ring, but returned to a dialtone - a first! Some calls made this morning are still not ringing.

I also have been with VOIPo since the pre-launch date; there were many difficult periods. I can't count the times we were without service and my wife wanted me to ditch the effort.

You have mentioned many times that you are satisfied with VOIPo's performance. Unfortunately, there are others that do have problems. As I said, "My problems may be just mine, but they are problems." The same is true for any other person reporting an issue.

For whatever reason, VOIPo isn't performing optimally for me. I think I've been more than patient, but it's time for a change.

Ken

---

Ken....

I empathize with you.

I had the same situation years ago with ViaTalk and found that it was cheaper and more effective to change providers than to have my wife file for divorce. ;)

Quote:

---

Originally Posted by KenH

Burris -

Don't take this personally. I was merely letting Russell know that I have also experienced the same issues.As a matter of fact, the next call I made after posting not only didn't ring, but returned to a dialtone - a first! Some calls made this morning are still not ringing.

I also have been with VOIPo since the pre-launch date; there were many difficult periods. I can't count the times we wer e without service and my wife wanted me to ditch the effort.

You have mentioned many times that you are satisfied with VOIPo's performance. Unfortunately, there are others that do have problems. As I said, "My problems may be just mine, but they are problems." The same is true for any other person reporting an issue.

For whatever reason, VOIPo isn't performing optimally for me. I think I've been more than patient, but it's time for a change.

Ken

---

Thanks, Ken, I do appreciate your very well written post. Like you I too am well aware of Burris' satisfaction :-). My situation could not be more vanilla - a VOIPo provided device connected to a UVerse router with all the appropriate forwarding as suggested by VOIP. I'd like to attach a screen capture of my UVerse config in case some UVerse user sees something stupid on my part, but I'm having an issue trying to get it within the right pixel limits.

Russell -

Thank you for the kind words.

I have done it all - two modems (Moto & Linksys), two different routers (D-Link & ASUS (Tomato & DD-WRT)), three ATA's (PAP2, PAP2T, HT502), & three different phone systems including hard-wired. I've tested every conceivable configuration of these devices. The only thing I haven't tried is changing ISP's ;).

I wish you luck.

Ken

Quote:

---

Originally Posted by KenH

Russell -

Thank you for the kind words.

I have done it all - two modems (Moto & Linksys), two different routers (D-Link & ASUS (Tomato & DD-WRT)), three ATA's (PAP2, PAP2T, HT502), & three different phone systems including hard-wired. I've tested every conceivable configuration of these devices. The only thing I haven't tried is changing ISP's ;).

I wish you luck.

Ken

---

I do sense your frustration. Despite that, your posts are a model of gentility.

I'm hoping my case is a lot simpler. After all, it's a configuration that Brandon has tested and is known to work. Which makes me wonder if the cause is in those mysterious upstream providers - and, if in the search for more economic routes those have changed, and I'm paying the price.

For 6 hours now, friends are having to call on cell not in the simul ring to get me. They call the voipo number and get 1.5 rings then a fast busy. Same when I call from a cell to my voipo number. Nothing on my end rings, not even the simul ring number. All incoming calls are showing on the call log for 0 seconds duration. I can call out ok.. 4 hours since I put in a service request and nothing back from them yet.

I'm a fairly new VOIPo customer as well as this being my first VOIP experience moving from AT&T pots. Things were going great until the last few days or so, I'm experiencing the exact same issue as reported here; no ringing then the called party will answer after a long silence (15-20 secs or so).

One time I called my Dad at his cabin and it stayed silent for a long time with no answer, when I tried that number from my cell phone his line was busy. I did get through some time later with my cell and found that he was on the internet (dialup).

So I've experienced a no ring with long silence then answer as well as a no busy signal at the called party, I'm really hoping these glitches get fixed ASAP.

My wife is getting a little chippy over these 'glitches' which she has also experienced,of course she has little tolerance for as them as they weren't experienced with AT&T.

I am on Charter cable in Michigan (no internet access issues during these phone issues), D-Link DIR-655 (no changes from initial install when the service was working problem free, Linksys RT31P2 router (I have not had the line lights go out on the device).

I will be starting a ticket but wanted to share with others.

Quote:

---

Originally Posted by ExCavTanker

I'm a fairly new VOIPo customer as well as this being my first VOIP experience moving from AT&T pots. Things were going great until the last few days or so, I'm experiencing the exact same issue as reported here; no ringing then the called party will answer after a long silence (15-20 secs or so).

---

I'm glad you shared. It's reassuring to know that others are having the same issue. Tech supports focus based on my ticket so far appears to be on my end. When multiple people report the issue and folks like me have a very simple setup (VOIPo router connected to UVerse box with ports forwarded), it makes me wonder whether the problem is not in my setup. Do note, I don't experience the issue on all calls - I just made two calls to numbers I know (no one at the other end) and it rang right away.

Russell,

I'm using VOIPo on U-verse and my configuration is a little different than yours. Instead of forwarding ports I have the Residential Gateway configured to give my PAP2T its external IP address and to forward all traffic not destined for another system on my network to it (DMZplus). You can configure DMZplus in the RG in Settings -> Firewall -> Applications, Pinholes and DMZ. Select your adapter from the list of devices, click the radio button near the bottom for Allow all applications and then click Save. To assign it the external IP address go to Settings -> LAN -> IP Address Allocation. Find your adapter in the list, change Address Assignment to Public and change WAN IP Mapping to Router WAN IP address. I haven't had any issues with this setup. I'm still able to forward specific traffic (Remote Desktop, Peer-to-peer, etc.) to other systems using firewall rules; just anything that doesn't match a firewall rule or isn't a reply to an outbound request gets sent to the VOIPo adapter.

Quote:

---

Originally Posted by 97526

For 6 hours now, friends are having to call on cell not in the simul ring to get me. They call the voipo number and get 1.5 rings then a fast busy. Same when I call from a cell to my voipo number. Nothing on my end rings, not even the simul ring number. All incoming calls are showing on the call log for 0 seconds duration. I can call out ok.. 4 hours since I put in a service request and nothing back from them yet.

---

Got eMail this am from voipo, said issue with simul ring and all should be ok.
This was fixed the morning, now 6 hours later, same issues.

Quote:

---

Originally Posted by JimDog

Russell,

I'm using VOIPo on U-verse and my configuration is a little different than yours. Instead of forwarding ports I have the Residential Gateway configured to give my PAP2T its external IP address and to forward all traffic not destined for another system on my network to it (DMZplus). You can configure DMZplus in the RG in Settings -> Firewall -> Applications, Pinholes and DMZ. Select your adapter from the list of devices, click the radio button near the bottom for Allow all applications and then click Save. To assign it the external IP address go to Settings -> LAN -> IP Address Allocation. Find your adapter in the list, change Address Assignment to Public and change WAN IP Mapping to Router WAN IP address. I haven't had any issues with this setup. I'm still able to forward specific traffic (Remote Desktop, Peer-to-peer, etc.) to other systems using firewall rules; just anything that doesn't match a firewall rule or isn't a reply to an outbound request gets sent to the VOIPo adapter.

---

Thanks, JimDog. Your instructions are excellent and if I've got to move to the DMZ I'll do it and the instructions will most certainly help. However, on principle I dislike putting my ATA in the DMZ, but that's a different thread :-).

I had another call this evening where I couldn't hear the caller. Since then I tech support remotely accessed my RT31P2 and say, "We've applied a few adjustments to the account to aid in stabilizing the service. No further action is needed at this time. " So, I'm hoping all is well.

Quote:

---

Originally Posted by Russell

, "We've applied a few adjustments to the account to aid in stabilizing the service. No further action is needed at this time. " So, I'm hoping all is well.

---

one always wonders why such adjustments, if not mere guesses, were not previously applied!

I may have to take them up on the 30 days to return all for a refund....and just renew phone power

Quote:

---

Originally Posted by stevech

one always wonders why such adjustments, if not mere guesses, were not previously applied!

---

Having suffered through the glitches, I would have loved to have known why I (with a very vanilla setup) merited those changes. But, I'm going to assume they work, assume they don't tell the average customer what has been done, and not take any of their time pursuing the subject in the ticket.

So far the "adjustments" appear to be working. Not many calls, but no issues with the calls that have been made or received.

Quote:

---

Originally Posted by Russell

So far the "adjustments" appear to be working. Not many calls, but no issues with the calls that have been made or received.

---

Glad to see. See, sometimes opening a ticket really does work. ;)