jlumby Posted June 26, 2008 Report Share Posted June 26, 2008 I am aware of the registry changes that should be made in order to set DSCP on outgoing packets, however microsoft also installs a QOS packet scheduler by default, and binds it to the NIC. Is this good, bad, or indiferent from the PBXnSIP point of view? Just wondering if I should leave it, or not. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted June 28, 2008 Report Share Posted June 28, 2008 I am aware of the registry changes that should be made in order to set DSCP on outgoing packets, however microsoft also installs a QOS packet scheduler by default, and binds it to the NIC. Is this good, bad, or indiferent from the PBXnSIP point of view? Just wondering if I should leave it, or not. IMHO the packet scheduler makes only sense if the traffic that leaves the computer can exceed the speed limit of the NIC. For example if the NIC is connected to a T1 and you run both voice and data on it, well then a packet scheduler is really useful. If you have a 100 MBit NIC to the LAN and the computer is not a busy file server well then there it does not make sense to me. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.