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.
On Fri, Feb 12, 2016 at 8:56 AM, Anthony Orlando <[email protected]> wrote: > I have. It's always that build vs buy for me. 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. > > > We will all have issues, but it's the tools that will set us apart and > will enable us to resolve problems faster. > > > ------------------------------ > *From:* Peter E <[email protected]> > *To:* Anthony Orlando <[email protected]> > *Cc:* Matt Ladewig <[email protected]>; "[email protected]" < > [email protected]> > *Sent:* Thursday, February 11, 2016 10:14 PM > > *Subject:* Re: [VoiceOps] VoIP Monitor - How do you roll ? > > Keep beating that drum, Anthony. Have you tried voipmonitor? You might be > surprised. > > On Feb 11, 2016, at 22:21, Anthony Orlando <[email protected]> wrote: > > Empirix Peter. Empirix > > Sent from my iPhone > > On Feb 11, 2016, at 8:37 PM, Peter E <[email protected]> wrote: > > 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). > > 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? > > On Feb 11, 2016, at 15:40, Matt Ladewig <[email protected]> wrote: > > 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. > > *From:* VoiceOps [mailto:[email protected] > <[email protected]>] *On Behalf Of *Christopher Aloi > *Sent:* Thursday, February 11, 2016 11:35 AM > *To:* Carlos Alvarez <[email protected]>; [email protected] > *Subject:* Re: [VoiceOps] VoIP Monitor - How do you roll ? > > 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.. > 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. > > > On Thu, Feb 11, 2016 at 2:11 PM Carlos Alvarez <[email protected]> > wrote: > > 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. > > Anyway, that's my answer...only do it when necessary. > > > On Thu, Feb 11, 2016 at 11:45 AM, Christopher Aloi <[email protected]> > wrote: > > Hey Everyone - > > I know many of you are happy VoIP monitor customers, I am too ! > > 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? > > Thanks - > > - Chris > > > > _______________________________________________ > VoiceOps mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/voiceops > > > _______________________________________________ > VoiceOps mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/voiceops > > _______________________________________________ > VoiceOps mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/voiceops > > _______________________________________________ > VoiceOps mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/voiceops > > > >
_______________________________________________ VoiceOps mailing list [email protected] https://puck.nether.net/mailman/listinfo/voiceops
