From: Kelly, Russell G (Russell_Kelly@eu1.bp.com)
Date: Thu Sep 30 2004 - 12:44:46 GMT-3
Btw, by match do you mean QoS values? The QoS match dscp values change
with every revision of Callmanager, but here are some match QoS
statement examples for a DSL user:
class-map match-all signalling
description Match Voice Signalling Traffic
match ip dscp af31
class-map match-all voice
description Match Voice Bearer Traffic
match ip dscp ef
!
!
policy-map voice
class voice
priority 150
class signalling
bandwidth 8
class class-default
bandwidth 16
random-detect
!
Cheers
Russ
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
David Duncon
Sent: 30 September 2004 14:02
To: ccielab@groupstudy.com
Subject: Matching Voice Signalling traffic
Hello Group,
I am little unsure on the best way to *match* the Signaling traffic.
In the recent past I have a seen a config where the author has used to
match
the destination port greater than TCP 3000 , equal to TCP 2000 & 2748.
And
also equal to TCP 1720.
Can some please explain why these ports are necessary to match signaling
traffic. I was impression that signaling only uses TCP 1720 :(
And also like RTP using the *even* ports from 16384 to 32768 , I was
impression that Signaling uses *odd* ports in the same range ??
I appreciate any clarification on the above queries :-)
Thanks in advance
David.
This archive was generated by hypermail 2.1.4 : Fri Oct 01 2004 - 15:00:51 GMT-3