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.
#84129 by jamgold
Thu Jul 07, 2011 10:10 am
ntoy wrote:Hello,

We apologize for the delay. We continue to investigate this issue.

Is call quality affected after a 15 minute threshold & is this happening on the downstream?

Thanks for your feedback!


Yes, even though people are complaining that they can not understand me either (which might be a different reason, though ;)

Today I had to hang up on a conference call after 15 minutes, because I could no longer understand what people were saying, that is how garbled the sound gets.
#84136 by thunderbird
Thu Jul 07, 2011 12:26 pm
jamgold wrote:
ntoy wrote:Hello,

We apologize for the delay. We continue to investigate this issue.

Is call quality affected after a 15 minute threshold & is this happening on the downstream?

Thanks for your feedback!


Yes, even though people are complaining that they can not understand me either (which might be a different reason, though ;)

Today I had to hang up on a conference call after 15 minutes, because I could no longer understand what people were saying, that is how garbled the sound gets.

Did you try this:
Power off the Ooma device for fifteen minutes. This allows time for the Ooma servers to reload your Ooma profile. Then repower the Ooma device and test.
#84139 by jamgold
Thu Jul 07, 2011 2:39 pm
thunderbird wrote:Did you try this:
Power off the Ooma device for fifteen minutes. This allows time for the Ooma servers to reload your Ooma profile. Then repower the Ooma device and test.


Yes, now the voice turns robotic after just 3 minutes and 30 seconds (Called movie phone)

I wish Ooma fixed this. I will try to contact support directly
#84144 by thunderbird
Thu Jul 07, 2011 5:31 pm
jamgold:
About the only thing you haven't tried if placing your Ooma device's Router Reserved IP address in the Router's DMZ.

If you use Norton Internet Security or one of the family of Norton products that have the Norton “Network Security Map” feature, and it is properly configured for the Ooma device’s Router reserved IP address, there is no security risk to the Router’s LAN devices at all. The “Trust Level” has to be set to “Restricted” in the Norton product, in each of your computers, for the Ooma device’s Router reserved IP Address. With the “Restricted” setting, Norton blocks all traffic to/from the Ooma device between any other device on your Router’s LAN. Norton does not restrict the operation of Ooma, or Ooma Home port traffic.
Note: If you port forward 172.27.35.1:80 in the Ooma device to be able to access Ooma Setup by typing your Router Ooma reserved IP address (http://192.xxx.xxx.xxx) in your computer browser window. It won’t work, because the Norton “Network Security Map” blocks any traffic between the Ooma device and other devices on you Router’s LAN. The way I access Ooma setup is temporarily turn off Norton Internet Security firewall just long enough to pull up the Ooma Setup page that I want. Then I turn on the firewall again.

I’ve used the Norton “Network Security Map" feature for some time and it works great.

Example: Instructions for setting up Norton Internet Security 2011 “Network Security Map” feature:

http://us.norton.com/support/kb/web_vie ... N&ln=en_US

http://us.norton.com/support/kb/web_vie ... 09160254EN

P.S. I'm not telling you to run out and purchase Norton, but it's something to think about.
#84176 by jamgold
Fri Jul 08, 2011 9:20 am
thunderbird wrote:jamgold:
About the only thing you haven't tried if placing your Ooma device's Router Reserved IP address in the Router's DMZ.

If you use Norton Internet Security or one of the family of Norton products


I actually have tried that, and it didn't make a difference. Will try again, though.

There is no PC in this household, so Norton is not an option.

Talked to Ooma support yesterday, and they claim my jitter is too high and suggest to have my ISP adjust my jitter. I don't buy it because Ooma voice sucks after 8-10 minutes even when the jitter constantly reports <2ms

I will try to experiment with Modem-Ooma-Router once more, and if that won't improve the voice quality I will dump the Ooma. It's a shame, but I wish I had known about this before I purchased it.
#84179 by jamgold
Fri Jul 08, 2011 10:34 am
After talking to Ooma support yesterday, Ooma suggested to

  • set Internet Settings to DHCP
  • set QOS to 0
  • set MAC address to automatic

I also moved the Ooma into the DMZ of my router. After 3'30'' the sound turned bad.

After changing QOS to anything but 0 the voice quality stayed intelligible longer but turned metallic after 10 minutes

Ooma still useless
#84182 by thunderbird
Fri Jul 08, 2011 10:51 am
jamgold wrote:After talking to Ooma support yesterday, Ooma suggested to

  • set Internet Settings to DHCP
  • set QOS to 0
  • set MAC address to automatic

I also moved the Ooma into the DMZ of my router. After 3'30'' the sound turned bad.

After changing QOS to anything but 0 the voice quality stayed intelligible longer but turned metallic after 10 minutes

Ooma still useless

Who is your Internet provider and what is the brand and model number of your Modem.
#84183 by jamgold
Fri Jul 08, 2011 10:52 am
thunderbird wrote:Who is your Internet provider and what is the brand and model number of your Modem.


COMCAST, Scientific Atlanta DPC2100
#84186 by murphy
Fri Jul 08, 2011 11:09 am
jamgold wrote:
thunderbird wrote:Who is your Internet provider and what is the brand and model number of your Modem.


COMCAST, Scientific Atlanta DPC2100

This will sound strange but it's based on actual experience with a DPC 2100 which I no longer use.
It would overheat and the downstream speed would drop from 12 mbps to less than 1 mbps. The upstream speed would stay normal.

If you have the DPC2100 sitting flat, take the four rubber feet off and move them to the end near the coax connector. There are places for them on that end. Sit the modem on the end with the coax connector at the lowest point. Let it temperature stabilize for 30 minutes and then see if it made any difference to your problem. You could also place a fan blowing directly on the modem to cool it down.

When I discovered that problem the DPC2100 went into my pile of useless parts. I installed a Motorola SB6120 in January of 2010 and have not had any more modem problems.

Who is online

Users browsing this forum: No registered users and 10 guests