This forum includes tips for maintaining the best audio quality possible with the Ooma System. If your Ooma system is having issues with dropped calls, static audio or echo, look here for assistance.
#75792 by cdamania1
Tue Feb 22, 2011 5:32 pm
Hello All..

I have been noticing some issues with my ooma telo in the last day or two after a reboot on saturday. What is happening is that when i call someone on verizon cell phone the phone will start ringing and i hear the rings but then it will go blank when they pick up and i keep saying hello and they can hear me but then say about 5 or 6 hellos i start hearing them.. then the quality is perfect. No issues. I tried the *99 and it works perfect..

Now the catch to that is that if the same cell phone user calls me on my home phone there are no issues..

Also if i call landline phone there are no issues at all..

I also noticed that sometimes when i call cell phone it will say incoming call and from who but it will not ring.

All this started happening after the reboot on saturday. I think the firmware was pushed out on saturday or something.. Correct me if i am wrong..

My internet speeds are awesome..

28Mbps down and 9Mbps up.
Ping test came back with results of A jitter of 3ms
Max ping response time is 30 to 40ms..

Not sure what is going on.. The firmware rev is 143368..

I have replaced my ooma device, My modem and all my network cables and everything is working good.. I also called my cable company this morning to see if there were any issues popping up with the modem and all the lines were clear..

Is anyone else experiencing these kinds of issues or similar.

Thanks in advance for all you help..
#75794 by EA PA
Tue Feb 22, 2011 5:53 pm
There has been a lot of chatter about this issue. I have the exact same issue as described, although since the new firmware was pushed out I have not tested this issue as extensively as I did before. I did have this issue before the new code was pushed out though so I don't think this is a contributor.

I have been using *99 flawlessly after an exhausting amount of testing. Without *99, I lose between about 10 to 15% of OB calls due to the 5 or so second delay to connect. I am not sure if they were cell phones though.

I did test with my own cell phones to conclude that I was getting the delay to connect to cell OB almost 100% of the time. By delay to connect I mean that after the party answers, one hears, one does not typically for 5-10 seconds or so - usually long enough for the other party to hang up....

I have heard that they are working on some sort of solution but that is about it. There is a battery of tests that can be run including U/D speed, jitter, ping, TCP max etc etc. All these have been great on my connections, so I have stopped testing and just use *99. If triple the bandwidth works, well so be it. Ill just try again once a month or so to see if there is any progress.
#75815 by cdamania1
Wed Feb 23, 2011 6:49 am
EA PA wrote:There has been a lot of chatter about this issue. I have the exact same issue as described, although since the new firmware was pushed out I have not tested this issue as extensively as I did before. I did have this issue before the new code was pushed out though so I don't think this is a contributor.

I have been using *99 flawlessly after an exhausting amount of testing. Without *99, I lose between about 10 to 15% of OB calls due to the 5 or so second delay to connect. I am not sure if they were cell phones though.

I did test with my own cell phones to conclude that I was getting the delay to connect to cell OB almost 100% of the time. By delay to connect I mean that after the party answers, one hears, one does not typically for 5-10 seconds or so - usually long enough for the other party to hang up....

I have heard that they are working on some sort of solution but that is about it. There is a battery of tests that can be run including U/D speed, jitter, ping, TCP max etc etc. All these have been great on my connections, so I have stopped testing and just use *99. If triple the bandwidth works, well so be it. Ill just try again once a month or so to see if there is any progress.


Thats Crazy.. I just hope the engineers at OOMA can fix this issue.. This product is great and works awesome and i would have to go somewhere else.. This morning i checked my cable line and everything has been working good.. The line is good the speed is good no jitter. Hopefully OOma can clear this up on the network/server side soon.
#75824 by LarryS
Wed Feb 23, 2011 9:09 am
Both my parents and I use Ooma Telo, two different homes in the same town. Two weeks ago I started noticing the same issue you describe when calling my parents’ home Ooma line from mine (Ooma to Ooma). Then last week I experienced the same issue when calling my wife from my ATT cellphone to my home Ooma line. I tried several calls with the same result. My wife, who uses the home phone line more than I do, tells me she has noticed this happening frequently in the last week. Both Ooma systems are on ATT U-verse connections with 12mb down / 2mb up speeds. They are both configured to be in the routers DMZ. I have had Ooma now for over a year and have had nothing but crystal clear connections until now. I really want to get to the bottom of this issue. Could a recent firmware deployment be causing this issue?
#75826 by EA PA
Wed Feb 23, 2011 9:18 am
I had mentioned before that I have had this issue going on since I got into the OOMA in early Jan so I doubt that it had anything to do with the recent deployment of the lastest code.

I had been testing like hell since I got OOMA setup to verify that I had no obvious connectivity issues. I do not in my opinion. My Upload speed is a bit slow but the best I can get so far at ~ 500k. I am behind modem.

I believe in pinning down issues with repeatable symptoms prior to reporting as best as possible. The cell issue has been since day 1 in early Jan since I bought, is definately repeatable and previously reported many times I am sure. The *99 workaround works for me. I would recommend it until this issue finally gets resolved. Im with Choice One / Metrocast.

All this aside, I do like the concept and product. Correcting this issue in my mind will make a good thing better. I would like to see OOMA succeed
#75828 by thunderbird
Wed Feb 23, 2011 9:26 am
LarryS:
So when you call Ooma to Ooma you have the delay before the voice is heard? Describe exactly what happens when you call Ooma to Ooma?

Information only:

I also called a neighbor this morning and heard a lot of echo.

I did the reboot of every thing and the echo seemed to go away.

My wife called me from her Sprint cell phone a little while ago. She said that the phone rang and rang. Than she hung up and tried again. The second time she got right through to our Ooma home phone.

My Ooma connection has been so good for a long time, I hope isn't "Here we go again".
#75831 by LarryS
Wed Feb 23, 2011 9:47 am
[quote="thunderbird"]LarryS:
So when you call Ooma to Ooma you have the delay before the voice is heard? Describe exactly what happens when you call Ooma to Ooma?

Yes, if I call from my Ooma line, I get ring-back, person answers and I can hear them but they can't hear me. If they don't hang up, after maybe 5-8 seconds, the issue goes away and we can talk.
Last edited by LarryS on Wed Feb 23, 2011 11:46 am, edited 1 time in total.
#75833 by thunderbird
Wed Feb 23, 2011 10:00 am
So this means that this problems is most likely a pure Ooma problem!

Not a routing problem to an outside legacy carrier.

LarryS thanks,
Last edited by thunderbird on Wed Feb 23, 2011 10:02 am, edited 1 time in total.
#75834 by EA PA
Wed Feb 23, 2011 10:01 am
I had called OOMA to OOMA a few weeks ago - I dont do lot of long distance - this one was about 30% across country - I got bad echo. I did not post because I have not tested to repeat - but now on forum so take it for what its worth on 1 call. I must admit I was surprised on an OOMA to OOMA call however.

Edit: was OB echo back - recipient heard no echo

Who is online

Users browsing this forum: No registered users and 10 guests