Re: QOS - RTP

As mentioned, "rtp audio" would be a way to go for #1.
"match protocol rtp" matches both RTP audio and video, therefore you would
match video conference traffic as well.

I would look for a conflict between this an other tasks - the #1 uses NBAR,
and there could be some restriction against it.
Also, consider signalization as well. Question might mention certain
signalling - SCCP, H.323.. For h.323 you would also match tcp:1720

Really concentrate of doing what the task is asking, without any conflict
with other tasks.

On Wed, Apr 1, 2009 at 7:32 PM, Ruhann <groupstudy_at_ru.co.za> wrote:

> Hi Guys
>
> Just a quick one regarding classifying "VOIP" traffic.
>
> If the question just state prioritize VOIP traffic, without any
> specification or limitation,
> would both solutions be valid?
>
> 1.
> class-map match-all VOIP1
> match protocol rtp
>
> 2.
> access 169 per udp any any range 16384 32767
> class-map match-all VOIP2
> match access-group 169
>
> With the first option, the packets are classified as RTP based on multiple
> attributes in the RTP header, rather than even UDP port numbers alone.
>
> Would both be correct if the LAB?
>
> Please be so kind to advise
> Regards
> --
> <ruhann>
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>

-- 
Pavel Bykov
----------------
Don't forget to help stopping the braindumps, use of which reduces value of
your certifications. Sign the petition at http://www.stopbraindumps.com/
Blogs and organic groups at http://www.ccie.net