Samsung recommends it, however, gives no real examples... here is one: Please chime in if you feel it would be better way.


priority-list 1 protocol ip high tcp 23
priority-list 1 protocol ip high tcp 6100
priority-list 1 protocol ip high udp 6000
priority-list 1 protocol ip high tcp 1719
priority-list 1 protocol ip high tcp 1720
priority-list 1 protocol ip high udp 5060
priority-list 1 protocol ip high udp 6000
priority-list 1 protocol ip medium tcp 3389
priority-list 1 protocol ip medium udp 3389
priority-list 1 default normal

int s0/1
ip rtp priority 30000 30 256
priority-group 1

int s0/1
ip rtp priority 30000 30 256
priority-group 1

port 3389 is for Remote Desktop/Terminal Server.

256 bandwidth is for RTP.. (there would be a max of 16 channels in use at any given time)..

I didn't want to cut the BW short.

I belive NBAR policy based routing would give better results if on a cisco router

Why not just mark the VoIP packets in the Samsung system and use Weighted Fair Queing based on DSCP (Diff-Serv) or IP Precedence in the router? Seems alot easier than QOS based on port and protocol, plus MPLS networks or any carrier based private network upstream of your router would expect you to have you packets marked if you expect QOS from them.....

Wkstill ,

This example is for a router ??? Cisco ???
Do we give this to the data people ??

Just a note. The last time this poster was seen on this board was in 2006. One can only assume that a response will not be coming.

While all of this information is wonderful, it is not user or admin material. Please feel free to enter the installer forum and post this stuff until your heart is content.