Hi Greg, I've been putting this on the agenda too - and was planning to use ethereal to grab all port numbers sent out by the UCM/Unity... - I believe it's only there that you need to classify based on the port numbers. Maybe yes, your idea about netstat may even be a better alternative one... Another thing relating to this, is the CCME, which terminates RTP and recreates it (example: call CCME phone/VTA to UCM phone). It looks like the CCME is setting up this new RTP stream with the TOS you set on the voip dialpeer towards UCM/IPIP, so there you loose the AF41 classification in case you have a video call. cheers, Juan
________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gregory Jost (grjost) Sent: Thursday, April 17, 2008 4:07 PM To: ccie_voice@onlinestudylist.com Subject: [OSL | CCIE_Voice] QoS marking based on port 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
