[VoiceOps] VoIP Monitor - How do you roll ?

[Christopher Aloi]

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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20160211/1be0f336/attachment.html>