Hi Chris, you are right, but only if you are asked to configure
classification in Router, and not to use ACLs.
But what Jacob is talking here is about signalling classification
configuration in Cat6500 with CATOS, where nbar is not available.
//r.a.
On Sun, Oct 26, 2008 at 10:47 PM, Chris
syntax.
-Original Message-
From: Ricardo Arevalo [EMAIL PROTECTED]
Sent: Monday, October 27, 2008 8:34 AM
To: Chris Parker [EMAIL PROTECTED]
Cc: Jacob Owen [EMAIL PROTECTED]; ccie_voice@onlinestudylist.com
Subject: Re: [OSL | CCIE_Voice] CCM Signalling Port ACL
Hi Chris, you are right
Not at all. That is what I do.
Cheers!
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sergio Polizer
Sent: Monday, October 27, 2008 6:18 PM
To: ccie_voice@onlinestudylist.com
Subject: Re: [OSL | CCIE_Voice] CCM Signalling Port ACL
Does someone see any problem if we
PROTECTED]
CC: ccie_voice@onlinestudylist.com
Subject: Re: [OSL | CCIE_Voice] CCM Signalling Port ACL
Ah ok thats true. For me i think any kind of lan qos on the 6500 is just a
time demon. The hardware is so old and unreliable you could be on your way
to a $1400 lunch real quick if it decides
Does someone have a 100% correct Signalling ACL ports to apply to say mark
DSCP values on a 6500 for traffic coming in from Call Manager? I have found
3-4 references in the IPExpert material but they all seem to be saying
different things. This is what I believe so far, if my to/from is
Jacon,
I personally have checked the ports utilization with sniffer for CCM 4.1(3).
All you writte are right except from the range 11000-11999, those ports are
not used in the CCM version (4.X).
Just would add: permit tcp any eq 1720 any for H323 gateways
communication, when the call is not
I know nbar is something one should use sparingly in real life, but why
not use it in the lab?
All you would need is:
class-map match-all ef
match protocol rtp audio
class-map match-any cs3
match protocol sip
match protocol h323
match protocol mgcp
match protocol skinny
Along with nbar
