<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=white lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I have customer that is running a Riverbed between all IPT
sites. We officially recommend that all Riverbed devices have to stay out of
the path for voice traffic. I had couple of conference calls with riverbed
support and learn that Riverbed will be transparent for UDP traffic, but it
will try to optimize TCP (signaling) traffic. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Customer configure Riverbed to be “transparent” for signaling
but on some sites we have latency in the call establishment. Other sites works
fine. This is reported as a intermittent problem, but I am blaming
misconfiguration on the Riverbed side. Recently we had a major outage because
of faulty NIC in the riverbed.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>From the QoS perspective because we didn’t know what
riverbed is doing, we place Access lists for traffic selection on the MPLS edge
routers and deploy LLQ on the serial interface. Using this method we keep consistent
QoS configuration for the voice, and leave data to be handled by riverbed.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Long story short, if I can avoid anything on the voice path and
rely to the Cisco I would prefer this. After this project, I would recommend to
all may customers to avoid this as much as possible. This is very difficult to
troubleshoot.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Mladen<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:
"Tahoma","sans-serif";color:windowtext'> 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 3:01 PM<br>
<b>To:</b> Tim Reimers<br>
<b>Cc:</b> Cisco VoIP List<br>
<b>Subject:</b> Re: [cisco-voip] RTP and Bluecoat<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Hi Tim,<br>
<br>
That is *NOT* an official Cisco recommendation. I participate here as a
user sharing my experiences just like everyone else. Official
recommendations come from account teams on printed letterhead.<br>
<br>
/Wes<br>
<br>
Tim Reimers wrote: <o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>That certainly sounds like an official "Cisco says not to do
that" sort of answer ;-)</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>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"</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>;-)</span><o:p></o:p></p>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>I 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><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> <a
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>
[<a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>]
<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</span><o:p></o:p></p>
<p class=MsoNormal>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: <o:p></o:p></p>
<p class=MsoNormal>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>
<br>
<o:p></o:p></p>
<pre style='text-align:center'>
<hr size=4 width="90%" align=center>
</pre><pre><o:p> </o:p></pre><pre>_______________________________________________<o:p></o:p></pre><pre>cisco-voip mailing list<o:p></o:p></pre><pre><a
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><o:p></o:p></pre><pre><a
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></pre><pre> <o:p></o:p></pre></div>
</body>
</html>