From: David Hurtado (dei2viccie@hotmail.com)
Date: Thu Mar 11 2004 - 08:07:10 GMT-3
Which is the transport protocol for MGCP?
Thanks for the help
>From: <alsontra@hotmail.com>
>Reply-To: <alsontra@hotmail.com>
>To: <joe@martinsweb.org>, "'Yasser Abdullah '"
><yasser@alharbitelecom.com>, <ccielab@groupstudy.com>, "Ramasubramanian
>Sethuraman" <snrmanian@hotmail.com>
>Subject: Re: VOICE Classification - Class-maps
>Date: Thu, 11 Mar 2004 03:22:35 -0800
>
>Thanks for the responses. For the RS exam, I'm hoping this is it as far as
>voice port numbers go...
>
>Cisco H.323 uses TCP port 1720
>Cisco VoIP payload uses UDP ports 16835 - 32767
>Cisco Gatekeeper uses TCP port 1719
>SIP uses UDP port 5060
>RTP can be identified by the RTP header
>MGCP port - 1025 through 65535 (not sure how important this is)
>SCCP (not sure)
>
>I can't seem to find all of these port numbers within the docCD, so guess
>memorization is probably the best method of recall. If anyone has any
>comments as to other relevant voice port numbers I would appreciate your
>comments.
>
>
>H.323 TCP 1720
>VoIP payload UDP 16835 - 32767
>Cisco Gatekeeper TCP 1719
>SIP UDP 5060
>RTP RTP header
>MGCP 1025 through 65535 (not sure how important
>this
>is)
>SCCP (not sure)
>
>
>Thanks,
>Alsontra
>
>
>
>----- Original Message -----
>From: "Joe Martin" <joe@martinsweb.org>
>To: "'Yasser Abdullah '" <yasser@alharbitelecom.com>;
><alsontra@hotmail.com>; <ccielab@groupstudy.com>
>Sent: Wednesday, March 10, 2004 10:29 PM
>Subject: RE: VOICE Classification - Class-maps
>
>
>Also, VoIP comes in protocols other than H.323. It could be SIP, MGCP or
>SCCP which all have different port for call control. Though all of them
>use
>the same UDP port range for RTP traffic.
>
>Joe
>
>-----Original Message-----
>From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
>Yasser Abdullah
>Sent: Wednesday, March 10, 2004 9:30 PM
>To: alsontra@hotmail.com; ccielab@groupstudy.com
>Subject: RE: VOICE Classification - Class-maps
>
>
>Also, if your voice gateways register with a gatekeeper, you'll need TCP
>port 1719.
>
>-----Original Message-----
>From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
>alsontra@hotmail.com
>Sent: Thursday, March 11, 2004 8:08 AM
>To: ccielab@groupstudy.com
>Subject: VOICE Classification - Class-maps
>
>Group,
>
>This question has been asked before, but there was no answer. Forgive my
>repetition...
>
>
>If you need to classify voice and all that goes with it (H323, etc), can
>you
>assume that ports 1720 and 16384 - 32767 will encompass voice traffic? In
>general, I'm finding that most voice traffic traverse these udp ports.
>
>For example:
>
>If you asked to classify and set DSCP values on all voip traffic, would
>something of this sort do the trick?
>
>ip access-list extended VOICE
> permit udp any any range 16384 32767
> permit udp any any eq 1720
>
> class-map match-all VoIP
> match access-group name VOICE
>
>
> policy-map QOS
> class VoIP
> set dscp cs5
> class class-default
> set dscp cs1
>
>int e0/0
>service-policy input QOS
>
>
>While this is certainly not all inclusive, it essentially cover most voip
>activities correct? Or do you have to try and use the question to find the
>appropriate port numbers?
>
>Thanks,
>Alsontra
>
>_______________________________________________________________________
>Please help support GroupStudy by purchasing your study materials from:
>http://shop.groupstudy.com
>
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html
>
>_______________________________________________________________________
>Please help support GroupStudy by purchasing your study materials from:
>http://shop.groupstudy.com
>
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html
>
>_______________________________________________________________________
>Please help support GroupStudy by purchasing your study materials from:
>http://shop.groupstudy.com
>
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Thu Apr 01 2004 - 08:15:17 GMT-3