Then probably the only second possible identifier for RTP is the codec number. Then your match option would sum up to UDP, starting from port 1024 (usually), RTP version number, and the codec range (from 0 to 110 to be safe). Depends on you if that is sufficient.
Regards NO
On Wednesday 11 May 2005 21:27, Lucas Aimaretto wrote:
Easiest solution: buy phones which have QoS tagging build in. Second easiest solution: but your phones into a dedicated sub-network. Then it is easy to identify phone traffic according to the IP.
Well ... first solution is nice ... but I have many phones allready. Second one has many problems
- 1: If it is a softphone, I'll be giving high priority to the
PC holding the soft phone and I just want to prioritize RTP. service, not all the services of that PC.
- 2: Lets say I use fix ports for softphone's rtp ... but kind
of messy if too many softphones.
- 3: If doing NAT, according to the KTPD ( Kernel Travelling
Packet Diagram ), I could not prioritize by source IP, because, at QoS STAGE, the packet was allready nated, and so, all packets would match.
Regards,
Lucas