From: Edwards, Andrew M (andrew.m.edwards@boeing.com)
Date: Mon Oct 25 2004 - 13:43:28 GMT-3
Tim,
That matches the rtp even ports (16384 - 32767) which are the voice
traffic. The odd ports in the range are used for rtp control/session
management.
The signaling would depend upon the signaling protocol in question.
Dial-peers use H323, so its tcp 1720. But you could get asked about
SCCP (skinny) for callmanager to Cisco Voip phones (e.g. tcp 2000), or
MGCP ( I don't know these off hand...).
But, since this is R&S, I'd assume its H323 dial peers (aka TCP 1720).
When in doubt, ask the proctor...
HTH,
andy
PS. Scott did a nice post regarding this thread and the use of the
protocols for these various signaling gateways.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
ccie2be
Sent: Friday, October 22, 2004 3:25 PM
To: Kelly, Russell G; David Duncon; ccielab@groupstudy.com
Subject: Re: Matching Voice Signalling traffic
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
This archive was generated by hypermail 2.1.4 : Sat Nov 06 2004 - 17:11:52 GMT-3