From: Derek Pocoroba (dpocoroba@gmail.com)
Date: Mon Sep 24 2007 - 13:10:10 ART
Something to keep in mind between the two options. Some difference between
them is the matching even vs odd. As well as matching the real time control
packets (RTCP). Here is a quick break down on the ways to mark RTP traffic
1) "match ip rtp"
a. Matches even UDP port numbers from 16384 32767
b. Does not match the RTCP packets ( Real Time Control Packets )
2) "Access-list 100 per udp any any range 16384 32767"
a. Matched even and odd UDP port numbers
b. Does match the RTCP packets
3) "Match protocol rtp"
a. Relies on NBAR to look at the RTP payload. Looking at the actual
CODEC's
b. Does not match the RTCP packets
HTH
On 9/24/07, ISolveSystems <support@isolvesystems.com> wrote:
>
> When the question asks you to match voice traffic, is there a preferred
> way
> of doing it? For the first one, do I have to match both ways? Is it
> necessary to always permit tcp 1720?
>
> 1. ip access-l ex VOICE
> per tcp any any eq 1720
> per udp any any range 16384 32767
>
> OR
>
> 2. class-map match-all VOICE
> match ip rtp 16384 16383
>
> Thanks.
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
-- Derek Pocoroba CCIE #18559
This archive was generated by hypermail 2.1.4 : Sat Oct 06 2007 - 12:01:15 ART