<div dir="ltr">Agreed, tools are indeed important. The question is, does the end justify the means, i.e. does the cost justify the perceived difference in quality of the tool? I like Empirix a lot, but I just can't justify the cost. I'd rather sink the extra couple hundred G's into product.</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 12, 2016 at 8:56 AM, Anthony Orlando <span dir="ltr"><<a href="mailto:avorlando@yahoo.com" target="_blank">avorlando@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="color:#000;background-color:#fff;font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-size:16px"><div dir="ltr"><span>I have. It's always that build vs buy for me. </span>Before Empirix we had various sniffers etc. I like having a vendor/partner I can lean on for critical items. I think most companies overlook the importance of tools. In my current role we took ticket cycle time down from 160 hrs to 22 mostly attributed to adding Empirix. Adding their analytics package will then enable me to be proactive and able to detect issues BEFORE our customers feel them. This is obviously the holy grail for all of us. </div><div dir="ltr"><span><br></span></div><div dir="ltr"><span><br></span></div><div dir="ltr"><span>We will all have issues, but it's the tools that will set us apart and will enable us to resolve problems faster. </span></div><div><br><div class="hm HOEnZb"><br></div></div><div style="display:block"><div class="hm HOEnZb"> </div><div style="font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-size:16px"><div class="hm HOEnZb"> </div><div style="font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-size:16px"><div class="hm HOEnZb"> </div><div dir="ltr"><div class="hm HOEnZb"> </div><font size="2" face="Arial"><div class="hm HOEnZb"> <hr size="1"> <b><span style="font-weight:bold">From:</span></b> Peter E <<a href="mailto:peeip989@gmail.com" target="_blank">peeip989@gmail.com</a>><br> <b><span style="font-weight:bold">To:</span></b> Anthony Orlando <<a href="mailto:avorlando@yahoo.com" target="_blank">avorlando@yahoo.com</a>> <br><b><span style="font-weight:bold">Cc:</span></b> Matt Ladewig <<a href="mailto:matt@univoip.com" target="_blank">matt@univoip.com</a>>; "<a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a>" <<a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a>><br> <b><span style="font-weight:bold">Sent:</span></b> Thursday, February 11, 2016 10:14 PM</div><div><div class="h5"><br> <b><span style="font-weight:bold">Subject:</span></b> Re: [VoiceOps] VoIP Monitor - How do you roll ?<br> </div></div></font> </div><div><div class="h5"> <div><br><div><div><div></div><div>Keep beating that drum, Anthony. Have you tried voipmonitor? You might be surprised.</div><div><div><br clear="none">On Feb 11, 2016, at 22:21, Anthony Orlando <<a rel="nofollow" shape="rect" href="mailto:avorlando@yahoo.com" target="_blank">avorlando@yahoo.com</a>> wrote:<br clear="none"><br clear="none"></div><div></div></div></div><div><div><div>Empirix Peter. Empirix <br clear="none"><br clear="none">Sent from my iPhone</div><div><br clear="none">On Feb 11, 2016, at 8:37 PM, Peter E <<a rel="nofollow" shape="rect" href="mailto:peeip989@gmail.com" target="_blank">peeip989@gmail.com</a>> wrote:<br clear="none"><br clear="none"></div><blockquote type="cite"><div></div></blockquote></div><div><div></div><div>We're in the middle of a trial of voipmonitor so this topic is timely as we're crushing the lab boxes and therefore don't trust any of the stats it is currently showing (MOS, PDD, etc). </div><div><br clear="none"></div><div>If you're capturing sip + rtp headers and you have a need (plus permission) to record full rtp for a single user, how's that done in the interface?</div><div><br clear="none">On Feb 11, 2016, at 15:40, Matt Ladewig <<a rel="nofollow" shape="rect" href="mailto:matt@univoip.com" target="_blank">matt@univoip.com</a>> wrote:<br clear="none"><br clear="none"></div><div>
</div></div><div><div>
<div><span style="font-size:11.0pt">Agreed, all sip signaling with RTP headers only for all calls. Only full RTP for specific troubleshooting and even then only by a very limited staff.
</span></div>
<div><span style="font-size:11.0pt"> </span></div>
<div><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> VoiceOps [<a rel="nofollow" shape="rect" href="mailto:voiceops-bounces@voiceops.org" target="_blank">mailto:voiceops-bounces@voiceops.org</a>]
<b>On Behalf Of </b>Christopher Aloi<br clear="none">
<b>Sent:</b> Thursday, February 11, 2016 11:35 AM<br clear="none">
<b>To:</b> Carlos Alvarez <<a rel="nofollow" shape="rect" href="mailto:caalvarez@gmail.com" target="_blank">caalvarez@gmail.com</a>>; <a rel="nofollow" shape="rect" href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a><br clear="none">
<b>Subject:</b> Re: [VoiceOps] VoIP Monitor - How do you roll ?</span></div>
<div> </div>
<div>
<div>We capture SIP signaling and RTP headers to evaluate the call quality our customers and carriers. Using the data we can proactively solve problems etc.. </div>
<div>
<div>If we are actively troubleshooting an issue we may capture the full RTP to analyze the packets. The need to capture the full packet is pretty rare.</div>
</div>
<div>
<div>
<div> </div>
</div>
<div>
<div> </div>
</div>
<div>
<div>
<div>
<div>
<div>On Thu, Feb 11, 2016 at 2:11 PM Carlos Alvarez <<a rel="nofollow" shape="rect" href="mailto:caalvarez@gmail.com" target="_blank">caalvarez@gmail.com</a>> wrote:</div>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>Doesn't anyone else see a major privacy/compliance/legal issue with capturing all packets? We only record if a customer explicitly allows us as part of a problem complaint.</div>
<div>
<div> </div>
</div>
<div>
<div>Anyway, that's my answer...only do it when necessary.</div>
</div>
<div>
<div> </div>
</div>
</div>
<div>
<div> </div>
</div>
<div>
<div>
<div>On Thu, Feb 11, 2016 at 11:45 AM, Christopher Aloi <<a rel="nofollow" shape="rect" href="mailto:ctaloi@gmail.com" target="_blank">ctaloi@gmail.com</a>> wrote:</div>
</div>
</div>
<div>
<div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>Hey Everyone - </div>
<div>
<div> </div>
</div>
<div>
<div>I know many of you are happy VoIP monitor customers, I am too !</div>
</div>
<div>
<div> </div>
</div>
<div>
<div>Currently I have a "capture" node deployed in my three data centers pushing packets back to a centralized DB/GUI instance. I hit some bottle necks around disk storage on the central instance and lost packets on the remote capture nodes.
I'm in the market for some new hardware to tidy this up a bit, curious - what does your deployment look like? what type of hardware are you using? do you split your capturing up (send/receive) or have any other hardware tips?</div>
</div>
<div>
<div> </div>
</div>
<div>
<div>Thanks - </div>
</div>
<div>
<div> </div>
</div>
<div>
<div>- Chris</div>
</div>
<div>
<div> </div>
</div>
</div>
<div> </div>
</blockquote>
</div>
</div>
<div>
<div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div style="margin-bottom:12.0pt">_______________________________________________<br clear="none">
VoiceOps mailing list<br clear="none">
<a rel="nofollow" shape="rect" href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br clear="none">
<a rel="nofollow" shape="rect" href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a></div>
</blockquote>
</div>
<div> </div>
</div>
<div>_______________________________________________<br clear="none">
VoiceOps mailing list<br clear="none">
<a rel="nofollow" shape="rect" href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br clear="none">
<a rel="nofollow" shape="rect" href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a></div>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</div>
<div><span>_______________________________________________</span><br clear="none"><span>VoiceOps mailing list</span><br clear="none"><span><a rel="nofollow" shape="rect" href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a></span><br clear="none"><span><a rel="nofollow" shape="rect" href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a></span><br clear="none"></div><blockquote type="cite"><div><span>_______________________________________________</span><br clear="none"><span>VoiceOps mailing list</span><br clear="none"><span><a rel="nofollow" shape="rect" href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a></span><br clear="none"><span><a rel="nofollow" shape="rect" href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a></span><br clear="none"></div></blockquote></div></div></div><br><br></div> </div></div></div> </div> </div></div></div></blockquote></div><br></div>