From: Gavin Lawson (GavinL@titan.net.au)
Date: Mon May 28 2007 - 23:37:08 ART
Hi Russel
Voice payload uses UDP even ports ranging from 16384 to 32767.
So if the question asks to match "voice traffic" then I would only match
the payload.
The and access list matching udp with a range from 16834 32767 would be
OK, but remember you are also matching the odd ports.
To match using "match ip rtp 16384 16383" is better (BUT a bit more
confusing)
First of all this will only match the even ports (Like we want to).
Also the syntax is a bit strange. Have you added 16384 to 16383 as it
comes to 32767 :-). Meaning it will match all ports from 16384 pluss all
ports up to 16383 above.
The "match ip rpt 16384 16383" is a better way to match voice packets.
GL
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
James Russell
Sent: Tuesday, 29 May 2007 10:10 AM
To: ccielab@groupstudy.com
Subject: QoS VoIP question
Group,
Apparently, my search-fu is not working. I've been doing some labs, and
it seems like every time they mention matching voice or VoIP traffic for
QoS, they use different solutions each time. Sometimes, they just
"match ip rtp 16384 16383". Others, they have an access list like:
ip access-list extended VoIP
permit tcp any any eq 1720
permit udp any <sometimes a range appears here> any range 16834 32767
The TCP port for call setup doesn't always appear, either. My question
is, how do we know what they want? If a question on the lab asks us to
"match all voice traffic", what path do we take? Do we match ip rtp
16384 16383? Match like the access list shown? Match protocol rtp
audio?
I apologize if this has been answered before. Like I said, I can't seem
to search too well tonight.
---------------------------------
You snooze, you lose. Get messages ASAP with AutoCheck in the all-new
Yahoo! Mail Beta.
This archive was generated by hypermail 2.1.4 : Fri Jun 01 2007 - 06:55:22 ART