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
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
Most states in the US have single party consent laws where at least 1 party needs to know if the calls are being recorded. Some have 2 party consent. Otherwise it's pretty much an unauthorized wire tap. On Feb 11, 2016, at 12:11 PM, Carlos Alvarez <caalvarez at gmail.com<mailto: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<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<mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops
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/
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
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
On 02/11/2016 02:21 PM, Carlos Alvarez wrote:
Chris must have one hell of a busy voice service if he's overloading on just signaling.
Oh, it doesn't take that much, especially if VoIP Monitor isn't designed for high-throughput systems. We have a number of customers in the short-duration / call centre space that run 500-1500 CPS through CSRP. They attempt to use Homer (SIP capture only) for diagnostic purposes and find its ingestion and database processing challenging with that amount of trash. -- 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/
We use VoIP monitor successfully (running on an ec2 instance) at a max of about 600 CPS and over 4 million call attempts/day with 7 days of data retention.
On Feb 11, 2016, at 12:23 PM, Alex Balashov <abalashov at evaristesys.com> wrote:
On 02/11/2016 02:21 PM, Carlos Alvarez wrote:
Chris must have one hell of a busy voice service if he's overloading on just signaling.
Oh, it doesn't take that much, especially if VoIP Monitor isn't designed for high-throughput systems.
We have a number of customers in the short-duration / call centre space that run 500-1500 CPS through CSRP. They attempt to use Homer (SIP capture only) for diagnostic purposes and find its ingestion and database processing challenging with that amount of trash.
-- 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/
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
Hi Alex - It does, you can capture SIP + RTP, SIP, or SIP + RTP headers. On Thu, Feb 11, 2016 at 2: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
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
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<mailto: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<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<mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops
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: 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
If you have the base config set to record rtp headers only, then you can add a specific capture rule under ?capture rules? to override the base config. Set RTP to ON in the rule. From: Peter E [mailto:peeip989 at gmail.com] Sent: Thursday, February 11, 2016 6:38 PM To: Matt Ladewig <matt at univoip.com> Cc: Christopher Aloi <ctaloi at gmail.com>; Carlos Alvarez <caalvarez at gmail.com>; voiceops at voiceops.org Subject: Re: [VoiceOps] VoIP Monitor - How do you roll ? 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<mailto:matt at univoip.com>> 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: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<mailto:caalvarez at gmail.com>>; voiceops at voiceops.org<mailto: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<mailto: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<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<mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops
Thanks Matt On Feb 11, 2016, at 21:47, Matt Ladewig <matt at univoip.com> wrote: If you have the base config set to record rtp headers only, then you can add a specific capture rule under ?capture rules? to override the base config. Set RTP to ON in the rule. From: Peter E [mailto:peeip989 at gmail.com] Sent: Thursday, February 11, 2016 6:38 PM To: Matt Ladewig <matt at univoip.com> Cc: Christopher Aloi <ctaloi at gmail.com>; Carlos Alvarez <caalvarez at gmail.com>; voiceops at voiceops.org Subject: Re: [VoiceOps] VoIP Monitor - How do you roll ? 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: 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
Yup - what Matt said is the way we do it too. You can expire the filter after a time duration which is nice, removes the filter after x days. I've also passed tcpdump args such as "port 5060 AND host x.x.x.x" ( something like that ) as the capture filter in the voipmonitor.conf file. You can use these args to drop RTP or chatty hosts you may not need to see. Very flexible. --- Christopher Aloi Sent from my iPhone
On Feb 11, 2016, at 9:52 PM, Peter E <peeip989 at gmail.com> wrote:
Thanks Matt
On Feb 11, 2016, at 21:47, Matt Ladewig <matt at univoip.com> wrote:
If you have the base config set to record rtp headers only, then you can add a specific capture rule under ?capture rules? to override the base config. Set RTP to ON in the rule.
From: Peter E [mailto:peeip989 at gmail.com] Sent: Thursday, February 11, 2016 6:38 PM To: Matt Ladewig <matt at univoip.com> Cc: Christopher Aloi <ctaloi at gmail.com>; Carlos Alvarez <caalvarez at gmail.com>; voiceops at voiceops.org Subject: Re: [VoiceOps] VoIP Monitor - How do you roll ?
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:
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
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:
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
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:
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
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
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 <avorlando at yahoo.com> 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 <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:
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 <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
participants (7)
-
abalashov＠evaristesys.com -
avorlando＠yahoo.com -
caalvarez＠gmail.com -
ctaloi＠gmail.com -
gmina＠connectfirst.com -
matt＠univoip.com -
peeip989＠gmail.com