<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16608" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV dir=ltr align=left><SPAN class=951454718-09042008><FONT face=Arial
color=#0000ff size=2>That certainly sounds like an official "Cisco says not to
do that" sort of answer ;-)</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=951454718-09042008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=951454718-09042008><FONT face=Arial
color=#0000ff size=2>Meaning you can now go back to your IT managers and say "we
can't do that to calls, and you have to purchase/find a way NOT to send
calls through that device"</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=951454718-09042008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=951454718-09042008><FONT face=Arial
color=#0000ff size=2>;-)</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=951454718-09042008></SPAN><FONT face=Arial><FONT
color=#0000ff><FONT size=2>I<SPAN class=951454718-09042008> did that with WAN
management hw at my previous employer-- they wanted to do that as well, and once
I could get a Cisco rep to say "not a good idea" - that was all that was needed
to kill off that particular bit of IT management crazy-thinking....they
immediately didn't want to do anything Cisco recommended
against.</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=951454718-09042008></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=951454718-09042008></SPAN></FONT></FONT></FONT> </DIV>
<DIV><BR></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of </B>Wes
Sisk<BR><B>Sent:</B> Wednesday, April 09, 2008 2:36 PM<BR><B>To:</B> Nick
Griffin<BR><B>Cc:</B> Cisco VoIP List<BR><B>Subject:</B> Re: [cisco-voip] RTP
and Bluecoat<BR></FONT><BR></DIV>
<DIV></DIV>We've run into a bit of fun with WAN Optimizers, not vendor specific
though:<BR>1. extra delay/latency. must consider the added delay and
latency for signaling and media thresholds especially related to user
experience<BR>2. preservation (or not) of DSCP bits. we've encountered
several WCCP engines that discard the DSCP bits and thus loose all
QoS.<BR><BR>Generally not a good idea for media or signaling traffic for setting
up media. Of course it can be made to work with careful planning and
observation depending on your resources and motivations.<BR><BR>/Wes<BR><BR>Nick
Griffin wrote:
<BLOCKQUOTE cite=mid:a2b352c40804091116x1bb06c87ofa1cd7e7eb750f4b@mail.gmail.com
type="cite">Does anyone have any experience good/bad or indifferent regarding
running voice rtp traffic through a blue coat wan optimizer? I personally
don't care for the idea, but it seems the situation has came up and I'm
wondering if you folks have any best practices, gotchas etc, those of you who
have done it in the past.<BR><BR>Thanks in advance<BR><BR>Nick Griffin<BR><PRE wrap=""><HR width="90%" SIZE=4>
_______________________________________________
cisco-voip mailing list
<A class=moz-txt-link-abbreviated href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A>
<A class=moz-txt-link-freetext href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A>
</PRE></BLOCKQUOTE></BODY></HTML>