From: Scott Morris (swm@emanon.com)
Date: Mon Jun 26 2006 - 02:08:49 ART
The control traffic (and also because it's TCP and has it's own mechanisms)
generally doesn't need to be prioritized. That's certainly a personal
decision, and I've had clients to it both ways. But the amount of your
control traffic on tcp/1720 compared to the RTP traffic is minimal.
That doesn't make either method incorrect though. Just the approach to get
the results is a bit different!
HTH,
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713, JNCIE
#153, CISSP, et al.
CCSI/JNCI
IPExpert CCIE Program Manager
IPExpert Sr. Technical Instructor
smorris@ipexpert.com
http://www.ipexpert.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
elias.chari@gmail.com
Sent: Sunday, June 25, 2006 9:03 AM
To: ccielab@groupstudy.com
Subject: VoIP QoS and TCP port 1720
Hi,
I have seen in a vendor's workbook various examples of prioritising VoIP, in
some occassions a class is used with NBAR to match protocol rtp and in
others an ACL to match the udp port range used for RTP and also matching the
Voice GW signalling on TCP 1720. The wording of the tasks was pretty much
identical but the solutions differ!
What is your opinion when asked to prioritise VoIP in the Lab, should one
always include TCP 1720?
Thanks
Elias
This archive was generated by hypermail 2.1.4 : Sat Jul 01 2006 - 07:57:33 ART