From: Nick Griffin (nick.jon.griffin@gmail.com)
Date: Thu Sep 30 2004 - 21:59:26 GMT-3
Scott hit it on the head, here's a bit more of what you were looking
for, good stuff to know if your deploying in different networks:
Note: VoIP calls can be established using H.323, session initiation
protocol (SIP), Media Gateway Control Protocol (MGCP) or Skinny Call
Control Protocol (SCCP) - proprietary protocol used by Cisco Call
Manager. The above example assumes H.323 Fast Connect. The following
list serves as reference for the ports used by VoIP signaling and
control channels:
*
H.323/H.225 = TCP 1720
*
H.323/H.245 = TCP 11xxx (Standard Connect)
*
H.323/H.245 = TCP 1720 (Fast Connect)
*
H.323/H.225 RAS = TCP 1719
*
SCCP = TCP 2000-2002 (CM Encore)
*
ICCP = TCP 8001-8002 (CM Encore)
*
MGCP = UDP 2427, TCP 2428 (CM Encore)
*
SIP= UDP 5060, TCP 5060 (configurable)
On Thu, 30 Sep 2004 16:44:46 +0100, Kelly, Russell G
<russell_kelly@eu1.bp.com> wrote:
> 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 : Fri Oct 01 2004 - 15:00:51 GMT-3