From: Joe Martin (joe@martinsweb.org)
Date: Thu Mar 11 2004 - 03:29:16 GMT-3
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
This archive was generated by hypermail 2.1.4 : Thu Apr 01 2004 - 08:15:17 GMT-3