[VoiceOps] VoIP Monitor - How do you roll ?

[Anthony Orlando]

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 <peeip989 at gmail.com>
 To: Anthony Orlando <avorlando at yahoo.com> 
Cc: Matt Ladewig <matt at univoip.com>; "voiceops at voiceops.org" <voiceops at voiceops.org>
 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 <avorlando at yahoo.com> wrote:

Empirix Peter. Empirix 

Sent from my iPhone
On Feb 11, 2016, at 8:37 PM, Peter E <peeip989 at gmail.com> 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 <matt at univoip.com> wrote:

#yiv7350399856 #yiv7350399856 -- _filtered #yiv7350399856 {panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv7350399856 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}#yiv7350399856 #yiv7350399856 p.yiv7350399856MsoNormal, #yiv7350399856 li.yiv7350399856MsoNormal, #yiv7350399856 div.yiv7350399856MsoNormal {margin:0in;margin-bottom:.0001pt;font-size:12.0pt;}#yiv7350399856 a:link, #yiv7350399856 span.yiv7350399856MsoHyperlink {color:blue;text-decoration:underline;}#yiv7350399856 a:visited, #yiv7350399856 span.yiv7350399856MsoHyperlinkFollowed {color:purple;text-decoration:underline;}#yiv7350399856 span.yiv7350399856EmailStyle17 {color:#1F497D;}#yiv7350399856 .yiv7350399856MsoChpDefault {} _filtered #yiv7350399856 {margin:1.0in 1.0in 1.0in 1.0in;}#yiv7350399856 div.yiv7350399856WordSection1 {}#yiv7350399856 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:voiceops-bounces at voiceops.org]On Behalf Of Christopher Aloi
Sent: Thursday, February 11, 2016 11:35 AM
To: Carlos Alvarez <caalvarez at gmail.com>; voiceops at voiceops.org
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 <caalvarez at gmail.com> 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 <ctaloi at gmail.com> 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
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops 
   _______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops 
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops

_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops



  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20160212/d2de5084/attachment.html>