02-13-2009 06:54 AM - edited 03-15-2019 04:12 PM
Can someone tell me the difference between these two commands. We have routers with QoS configurations done both ways. I know that the "match ip rtp 16384 16383" matches all even RTP ports, which are used for payload and does not match RTP odd ports, which are used signaling. But what is the result if you use "match ip rtp 16383 16383"? This command is also found in some old Cisco documentation but I can't find what exactly it's matching.
Thanks,
Mike
02-13-2009 07:29 AM
there really is no use on that
the 1st parameter simply is the starting port on which to apply the command
it simply covers 1 port more than the other command but that's out of the RTP
behavior is exactly the same but starts on port 16383
HTH
java
if this helps, please rate
02-13-2009 07:43 AM
So are you saying both commands will work. Both commands will match all even RTP ports within the range of 16384 to 32767?
"match ip rtp 16383 16383" = matches even ports within range 16383 to 32767?
"match ip rtp 16384 16383" = matches even ports within range 16384 to 32767?
Mike
02-13-2009 07:45 AM
exactly, that's the only difference. 1 port
HTH
java
if this helps, please rate
12-10-2016 06:36 AM
True story ;) good job !
12-10-2016 06:37 AM
The solution could have referred to IP ACL 101 with the match ip access-group 101 command, with ACL 101 matching UDP ports between 16,384 and 32,767, inclusive, to match all VoIP traffic. However, the match ip rtp command matches only the even-numbered ports in this same UDP port range. (VoIP payload only uses the even port numbers.) Therefore, the match ip rtp command is more efficient for matching VoIP, easier to configure, and only matches the VoIP payload.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide