You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be extremely helpful to be able to specify different port ranges for each type of service for proper QoS classification on the network rather than lumping both the RTP audio streams and RTP video streams into a single RTP range. For example, most organizations would want to be able to specify 46 or the EF dscp for the audio RTP stream, 34 dscp for the video RTP stream, and then 26 dscp for the signaling. As it is right now, we are forced to incorrectly classify the different aspects of traffic into categories they should not be in and in situations where there is traffic congestion on the network, you would more than likely want to dump the video before any audio traffic. Thanks!
The text was updated successfully, but these errors were encountered:
This is a feature request.
It would be extremely helpful to be able to specify different port ranges for each type of service for proper QoS classification on the network rather than lumping both the RTP audio streams and RTP video streams into a single RTP range. For example, most organizations would want to be able to specify 46 or the EF dscp for the audio RTP stream, 34 dscp for the video RTP stream, and then 26 dscp for the signaling. As it is right now, we are forced to incorrectly classify the different aspects of traffic into categories they should not be in and in situations where there is traffic congestion on the network, you would more than likely want to dump the video before any audio traffic. Thanks!
The text was updated successfully, but these errors were encountered: