[VoiceOps] VoIP Monitor - How do you roll ?

Christopher Aloi ctaloi at gmail.com
Thu Feb 11 14:42:20 EST 2016


Not saying I am overloading it by just capturing the SIP.  VoIP monitor can
likely handle the load I am pushing (~100CPS) with the right hardware and
deployment.  I am just wondering how others are using/deploying the tool.



On Thu, Feb 11, 2016 at 2:22 PM Carlos Alvarez <caalvarez at gmail.com> wrote:

> Chris must have one hell of a busy voice service if he's overloading on
> just signaling.
>
> Interesting related trivia:  A friend manages the signaling analysis for
> AT&T wireless, and his system writes 13 petabytes of data per week.  They
> write every single discussion packet between all devices, including every
> cell phone currently on the network.
>
>
> On Thu, Feb 11, 2016 at 12:16 PM, Geoffrey Mina <gmina at connectfirst.com>
> wrote:
>
>> Yes. You can limit the port that the sniffer captured on.
>>
>> > On Feb 11, 2016, at 12:15 PM, Alex Balashov <abalashov at evaristesys.com>
>> wrote:
>> >
>> > Doesn't VoIPMonitor support SIP-only capture, sans RTP?
>> >
>> >> On 02/11/2016 02:10 PM, Carlos Alvarez 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
>> >> <mailto: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 <mailto: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
>> >
>> >
>> > --
>> > Alex Balashov | Principal | Evariste Systems LLC
>> > 303 Perimeter Center North, Suite 300
>> > Atlanta, GA 30346
>> > United States
>> >
>> > Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
>> > Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
>> > _______________________________________________
>> > 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/20160211/866ff396/attachment-0001.html>


More information about the VoiceOps mailing list