From: Sasa Milic (smilic2@pexim.co.yu)
Date: Tue Nov 09 2004 - 07:52:10 GMT-3
Tim,
you can match IP Prec 5 for RTP/cRTP packets, and match IP Prec 3 for
signaling packets. But, don't put them into same class ! Usually,
you need "priority" class for RTP/cRTP and "bandwidth" class for
signaling. Since priority class also modify queue depth and does
policing it can have negative impact on signaling. I have TAC case
regarding this (signaling stops working if it is part of priority
class, when fragment size is less than 580 bytes ...).
Regards,
Sasa
ccie2be wrote:
>
> Hi guys,
>
> Where does this fit in? Can this also be used to match voip traffic and
> signalling?
>
> class-map VOIP
> match protocol rtp
>
> If matching rtp can't be used for matching voip traffic & signalling, when
> would someone use match prot rtp?
>
> Thanks, Tim
>
> ----- Original Message -----
> From: "Kelly, Russell G" <Russell_Kelly@eu1.bp.com>
> To: "David Duncon" <david_ccie@hotmail.com>; <ccielab@groupstudy.com>
> Sent: Thursday, September 30, 2004 11:44 AM
> Subject: RE: Matching Voice Signalling traffic
>
> > 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.
> >
> > _________________________________________________________________
> > Click here for the latest chart ringtones:
> > http://ringtones.com.au/ninemsn/control?page=/ninemsn/main.jsp
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Thu Dec 02 2004 - 06:57:40 GMT-3