From: Sean.Zimmerman@clubcorp.com
Date: Wed Apr 25 2007 - 18:46:36 ART
Since you are in charge of the egress traffic, you can place the VOIP in
an LLQ to ensure that at least the traffic going outbound is handled
correctly. Additionally, you can police the non-VOIP traffic inbound from
the ISP or you can even perform shaping on traffic egressing the Internet
perimeter towards the internal network. Both methods would be a way to
carve out a chunk of bandwidth for VOIP.
You can't do anything about congestion beyond your connection to the ISP,
and you can only indirectly influence ingress traffic. Oh, and good luck
with the finger-pointing when they experience voice quality problems! It
will always be on your end, you know.
"sirus MOGHADASIAN" <cyrus.mgh@gmail.com>
Sent by: nobody@groupstudy.com
04/25/2007 04:10 PM
Please respond to
"sirus MOGHADASIAN" <cyrus.mgh@gmail.com>
To
"Cisco certification" <ccielab@groupstudy.com>
cc
Subject
confusing QOS question
I really frustrated with this QOS problem.
Assume company that run VOIP connected to ISP for accessing to the
internet.
If this company run QOS on its edge router to prioritize voice traffic,
there is no change occur to incoming voice traffic since service provider
not run QOS and company's voice traffic must first come to service
provider
routers then come to company's edge router.
Routers implement QOS on their outgoing interface (assume we implement QOS
on edge router interface that forward traffic into company and ISP not run
QOS so traffic come across ISP router without prioritizing and running QOS
on our router not help us)
So if ISP not run QOS on its router , implementing QOS on edge router is
useless and we can't prioritize our traffic without help of ISP.
SO what's the point to implement QOS for this company?
Thanks
Sirus Moghadasian
This archive was generated by hypermail 2.1.4 : Tue May 01 2007 - 08:28:37 ART