VIEW TOPIC

... I haven't seen the inside of a switching center since it was filled with Strowgers (any of you young kids even heard the term?)...

What type of ISP do you have (DSL, cable, other)?

Cable modem. Comcast 8/2.

I moved the ooma in front of the router to see if that makes a difference. It goes against my nature since it seems wrong to put any device in front of your router/firewall and causes a few minor complications.

First, I am using automatic DynDNS registration on my router. Since it is beign NATed now, that doesn't work. Also, I didn't want to have to set up 2 separate port forwards (one on ooma & one on my router) every time I change something. I fixed this by opening a DMZ to my router.

On the up side, the ooma QoS is not supposed to kick in at all unless you are on a call. So, even if I have my QoS bandwidth set fairly low, ensuring a good voice session, I don't have to worry about it killing bandwidth to the rest of my systems when I'm not on the phone.

Another potential benefit of having the ooma responsible for QoS is that the link I posted earlier specifically mentions the ooma "reserving" bandwidth, along with a new setting in the next firmware allowing you to choose how much to reserve. If this is a true "reservation", ooma QoS settings would have a better effect on voice quality than ordinary QoS on the router could. Effectively rather than making sure more ooma packets get on the wire than other packets, as normal QoS could do, a reservation would effectively create two pipes of data going out, one the perfect bandwidth for ooma communication, and the other with whatever is left according your QoS limit. At least that's what I read by the term "reservation" and allowing us to choose the size.

First, I am using automatic DynDNS registration on my router. Since it is beign NATed now, that doesn't work.

If you run the client software that DynDNS provides, it will work fine with the ooma hub ahead of the router. I have yet to find a router that implements DynDNS's protocol properly.

... I haven't seen the inside of a switching center since it was filled with Strowgers (any of you young kids even heard the term?)...

Awesome. Good laugh. Thanks.

Scott

First, I am using automatic DynDNS registration on my router. Since it is beign NATed now, that doesn't work.

If you run the client software that DynDNS provides, it will work fine with the ooma hub ahead of the router. I have yet to find a router that implements DynDNS's protocol properly.

Exactly. I have ddclient on a Unix box to correct that.

Scott

I moved the ooma in front of the router to see if that makes a difference. It goes against my nature since it seems wrong to put any device in front of your router/firewall and causes a few minor complications.

If this test passes, then you know to tackle the QoS settings on your router, or live with Ooma as your first router. I have the same instincts you do. It doesn't feel right having Ooma out front, but it also is already tweaked to work perfectly.

Scott

Awesome. Good laugh. Thanks.

Scott

you're welcome! (I couldn't resist when I saw the mention of stroeger switches!)

PS I think I found my avatar!

Awesome. Good laugh. Thanks.

Scott

you're welcome! (I couldn't resist when I saw the mention of stroeger switches!)

PS I think I found my avatar!

That would be a brilliant avatar. I wish I could say I had thought of it.

Cheers,
Scott