QoS: Could it really be that simple?!?

Mike Bennett · Post by **Mike Bennett** » Wed Jul 30, 2008 2:37 am

Scanning the manual for my DSL box, I noticed it has QoS features.
So does my XP Network Connection.
I wondered if they might be conflicting.
I unchecked the QoS of my Network Connection, and my calls aren't choppy any more.
Hmmm.

lonestarmagic · Post by **lonestarmagic** » Wed Jul 30, 2008 4:31 am

Thanks for that tip, I also unchecked the Qos in my Win XP and my calls aren't choppy anymore as well......

Will have to monitor this method for a few days and see how it works out.

testing123 · Post by **testing123** » Wed Jul 30, 2008 7:35 am

Mike Bennett wrote:Scanning the manual for my DSL box, I noticed it has QoS features.
So does my XP Network Connection.
I wondered if they might be conflicting.
I unchecked the QoS of my Network Connection, and my calls aren't choppy any more.
Hmmm.

IMHO, choose "hardware" QoS over OS/"software" QoS everytime. (And do not use both at the same time).

It is best when handled by your Router for all your network traffic going in/out to the Internet.

I believe your results (and those of others) validate that.

PTravel · Post by **PTravel** » Thu Jul 31, 2008 1:13 am

I agree completely with this -- go with the hardware QOS option, and use the device closest to the modem to provide QOS services. And definitely don't have multiple devices providing it.

hvlqodvhinIyc · Post by **hvlqodvhinIyc** » Thu Jul 31, 2008 4:04 am

QOS signalling handled at the application layer by the OS with configurations supported by Magic Jack will be superior to IP layer QOS handled by routers shipping today or yesteryear. Check out Windows Rally for example.

lonestarmagic · Post by **lonestarmagic** » Thu Jul 31, 2008 4:18 am

PTravel wrote:I agree completely with this -- go with the hardware QOS option, and use the device closest to the modem to provide QOS services. And definitely don't have multiple devices providing it.

Ok, I unclicked the Qos under "network connections", but where do you find the hardware Qos?

Thx

saxman · Post by **saxman** » Thu Jul 31, 2008 5:43 am

PTravel wrote:I agree completely with this -- go with the hardware QOS option, and use the device closest to the modem to provide QOS services. And definitely don't have multiple devices providing it.

--

PT-I just got a new modem as I went to 12 mbps dsl . It's bigger then the last and is made by Motorola-now I also have Hawking-What if anything do I need to do to set everything up as far as the QOS goes? Just leave the Hawking to monitor this on its own or did you have to make modem changes?

testing123 · Post by **testing123** » Thu Jul 31, 2008 8:46 am

hvlqodvhinIyc wrote:QOS signalling handled at the application layer by the OS with configurations supported by Magic Jack will be superior to IP layer QOS handled by routers shipping today or yesteryear. Check out Windows Rally for example.

hvlqodvhinIyc, technically that may be so, however practically (IMHO) hardware QoS (at the Router) is best:

1) OS QoS is only going to help individual machines on your network
2) QoS using a Router with adequate resources and a good algorithm is going to help traffic flow for ALL your devices in and out of your network
3) What happens in mixed OS environments who have different QoS implementations (if at all)?

See pfSense for an excellent Open Source Router that runs on almost any hardware (including Thin Clients!) that has fabulous Traffic Shaping and QoS. (Based on m0n0wall)

And this is a scalable solution that can grow with the complexity of your network. Exampe config I have done: 7 unique network subnets (using soekris hardware) with multiple VOIP, multiple (Web, eCommerce, Blog, etc) Servers, internal "Private" networks and TWO multihomed ISPs -- no jitter, no dropped packets, no problems. I don't even want to imagine that config using OS/Software/QoS - the setup alone would be a nasty amount of work on multiple devices.

I understand Theory, but what matters to the average Consumer is how something works in Practice -- and something that can handle whatever hardware you hang off your network ... easily.

saxman · Post by **saxman** » Thu Jul 31, 2008 10:20 am

10-4-What matters is not what the piece of hardware is supposed to do but what it actually does. I may need to call Hawking to find out about getting everything dialed in and on the same page. I'm sure they have this happen alot but then again this voip/broadband boooster/ combo is still new and every router is different. This new one I got from Qwest is nice. They told me that the memory in it has set the settings and I don't have to do any adjustments to ity but I didn't ask about QOS- and the fact that there is a booster inline. I'm sure there's some tweeking that can be done to improve the audio quality.

lonestarmagic · Post by **lonestarmagic** » Thu Jul 31, 2008 6:45 pm

Update on Qos issue......

Today I found out that with Qos disabled on my system, the calls continued to be choppy.

I reset my system with Qos enabled and turned off my wireless router for three min. After I powered it back up and let it load everything and restarted my PC, I made a few local and long distant calls and they were totally clear, free of any choppyness.

So, in my case, my router was the issue and by powering it down for a few min, this has fixed my issue with the choppy calls.

magicJack and magicJack Plus Support, Reviews, FAQs and Tricks

QoS: Could it really be that simple?!?

QoS: Could it really be that simple?!?

Re: QoS: Could it really be that simple?!?

RE: QoS: Could it really be that simple?!?

Re: RE: QoS: Could it really be that simple?!?