this thread covers it pretty well.
http://www.certificationtalk.com:81/showflat.php?Cat//Board/voice4twelve/Number/27122/page/0/view/collapsed/sb/5/o//fpart/1
here is ACL that Mark Snow posted...
--snippet--
set port qos 2/42 port-based
set qos acl ip POD12_SERVER dscp 26 tcp any range 2000 2002 any
set qos acl ip POD12_SERVER dscp 26 tcp any any range 1024 4999
set qos acl ip POD12_SERVER dscp 26 tcp any any range 11000 11999
set qos acl ip POD12_SERVER dscp 26 tcp any any eq 1718
set qos acl ip POD12_SERVER dscp 26 udp any any eq 1719
set qos acl ip POD12_SERVER dscp 26 tcp any any eq 1720
set qos acl ip POD12_SERVER dscp 26 udp any eq 2427 any
set qos acl ip POD12_SERVER dscp 26 tcp any eq 2428 any
commit qos acl POD12_SERVER
set qos acl map POD12_SERVER 2/42
--snippet--
I'll add SIP
set qos acl ip POD12_SERVER dscp 26 udp any any eq 5060
set qos acl ip POD12_SERVER dscp 26 tcp any any eq 5060
I've personally verified ports 2000, 1719, 1720, 2427, 2428 from Mark's post
in wireshark. I don't know about 1718 - Cisco docs list it as gateway
discovery (multicast?) - easy enough to add....although, I'm fairly
confident CCM doesn't support this method.
Justin
On Thu, Apr 17, 2008 at 10:07 AM, Gregory Jost (grjost) <[EMAIL PROTECTED]>
wrote:
> There's a shroud of mystery around protocol port mappings. It's
> documented one way, taught another, but no one really knows what the proctor
> is looking for. To me, the definitive answer would be to look at the open
> ports on servers ("netstat –a" from CMD), and the open ports on the routers
> ("sh ip sockets"). This will show the exact ports being used by the active
> devices, including src/dst and udp/tcp (IP 17 and 6 respectively); however,
> this may not be what the proctor is looking for. For example, if you're
> using UDP for SIP, there will not be an open TCP port. If the proctor sees
> that you've only included udp 5060 for SIP, he may deduct points. For
> something like this, there should be a right way; otherwise, we should be
> able to just remember the port numbers and use tcp/udp src/dst for all
> signaling traffic. It doesn't make sense to me that we can be overkill with
> some, but not with others. Since my lab is next week, I'm going to just
> memorize it per IPExpert and hope for the best, instead of trying to make
> sense of it. I think it's worth bringing up to the proctors though.
>
>
>
> Anyone have any thoughts or suggestions on this?
>
>
>
>
>
> Greg Jost
>
> Network Consulting Engineer
>
> Unified Communications Practice
>
> Cisco Systems, Inc.
>
> 214-274-1922
>
>
>
