Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

QOS - DSCP Marking

Discussion in '3CX Phone System - General' started by dsnyc, Sep 19, 2010.

Thread Status:
Not open for further replies.
  1. dsnyc

    Joined:
    Aug 30, 2010
    Messages:
    34
    Likes Received:
    0
    I saw the following blog post:

    http://www.3cx.com/blog/voip-howto/qos-windows-2008-server-local-policy/

    My question is, this seems to mark ALL traffic from the 3CX server with a DSCP number.

    Is there a better to way to limit this so that only voice-traffic to/from 3CX Server is tagged? I don't want non-voice related traffic tagged with the same DSCP.

    I set the MSRTPTOS value in 3CX Custom Parameters to the same value that I set the DSCP QOS group policy section.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,293
    Likes Received:
    361
    Could you not use the destination IP option to limit QOS to just your VoIP provider?
     
  3. mcbsys

    mcbsys New Member

    Joined:
    Oct 8, 2008
    Messages:
    205
    Likes Received:
    23
    It looks like the Group Policy approach allows specifying the executable generating the packets, and/or the port number, so you could limit it that way.

    What I don't get is why you need Group Policy at all. I've asked that here:

    http://www.3cx.com/forums/msrtptos-does-not-add-dscp-tags-under-windows-20435.html
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.