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 wrote: Empirix Peter. Empirix Sent from my iPhone > On Feb 11, 2016, at 8:37 PM, Peter E wrote: > > We're in the middle of a trial of voipmonitor so this topic is

Re: [VoiceOps] VoIP Monitor - How do you roll ?

Empirix Peter. Empirix Sent from my iPhone > On Feb 11, 2016, at 8:37 PM, Peter E 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

Re: [VoiceOps] VoIP Monitor - How do you roll ?

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

Re: [VoiceOps] Recommended Website/IP monitoring tool

That's great - I wish everything could blink it's IP !! --- Christopher Aloi Sent from my iPhone > On Feb 11, 2016, at 9:48 PM, Pete Mundy wrote: > > > Yep! :) > > We used the controllable built-in LED to flash out the pi's IP(v4) address so > our engineers can discover it and connect to it

Re: [VoiceOps] VoIP Monitor - How do you roll ?

Thanks Matt On Feb 11, 2016, at 21:47, Matt Ladewig 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:peeip...@gmail.com] Sent: T

Re: [VoiceOps] Recommended Website/IP monitoring tool

Yep! :) We used the controllable built-in LED to flash out the pi's IP(v4) address so our engineers can discover it and connect to it across the LAN without needing any sort of display. We also used to have it 'speak' it's IP address out the earphones port (using espeak), but ended up turning

Re: [VoiceOps] Recommended Website/IP monitoring tool

This is all sounding _very_ familiar! We do quite similar things using RPis here too, right down to the reverse SSH tunnels. Incredibly useful for remote diagnosis, visibility and proactive response. Our sample size isn't huge, only just over 3X what you've mentioned, but thus-far we've had zer

Re: [VoiceOps] VoIP Monitor - How do you roll ?

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:peeip...@gmail.com] Sent: Thursday, February 11, 2016 6:38 PM To: Matt Ladewig Cc: Christoph

Re: [VoiceOps] Recommended Website/IP monitoring tool

I can recommend uptimerobot.com. I tried their free-tier service after an earlier recommendation which was either on this list or NANOG; I forget which. The service has been very reliable other than a few blips with IPv6 to some local hosts (we're down in New Zealand and it's likely related to

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

Re: [VoiceOps] Recommended Website/IP monitoring tool

You could do some interesting things with the PI's GPIO ports too... flash a LED to locate it in a rack, triggering a relay to reset a cable modem, log environmental data etc.. On Thu, Feb 11, 2016 at 7:38 PM Graham Freeman wrote: > Yep, with my managed network customers. I have a small number o

Re: [VoiceOps] Recommended Website/IP monitoring tool

+1 for Monitis... Very good for basic monitoring and e-mail/SMS alerts. If you need anything a bit more complex, I'd use a Raspberry Pi or Arduino. You can code a script once, and deploy to dozens of units. On Thu, Feb 11, 2016 at 2:39 PM, Carlos Alvarez wrote: > I use and like Monitis for outs

Re: [VoiceOps] Recommended Website/IP monitoring tool

Yep, I've considered it. Doing so would certainly open some more remote-management doors. It's just a layer of complexity that I haven't tackled yet. (My managed-networks business is just me and some occasional help from a small number of contractors.) A unique reverse SSH tunnel to a unique

Re: [VoiceOps] Recommended Website/IP monitoring tool

In place of the SSH management tunnels, have you considered OpenVPN? ‎ -- 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.

Re: [VoiceOps] Recommended Website/IP monitoring tool

Yep, with my managed network customers. I have a small number of customers, each of which is meaningfully profitable, so a $100/year deployment of a Pi with a fancier USB wifi interface is well worth it. I set up reverse SSH sessions (originating from the Pi) to distinct per-customer bastion hosts

Re: [VoiceOps] Recommended Website/IP monitoring tool

You have pi's deployed on the customer premise running smoke ping ? Great idea, have they been reliable ? I've only played with them - never production. How do you handle managing a pi fleet ? --- Christopher Aloi Sent from my iPhone > On Feb 11, 2016, at 3:36 PM, Graham Freeman wrote: > > I

Re: [VoiceOps] Recommended Website/IP monitoring tool

Thank you. *_* *Li Tiatia, EVP International Operations* *TCN Inc. Australasia/Oceania/Asia | au.tcnp3.com * *Direct: tia...@tcnp3.com | AU+61 1300 138 298 | NZ+64 3 668 4210 | US+1800 570 1561* *Support: serv...@tcnp3.com | AU+61 1800 352 478

Re: [VoiceOps] Recommended Website/IP monitoring tool

Thank you for the details. Appreciate it. *_* *Li Tiatia, EVP International Operations* *TCN Inc. Australasia/Oceania/Asia | au.tcnp3.com * *Direct: tia...@tcnp3.com | AU+61 1300 138 298 | NZ+64 3 668 4210 | US+1800 570 1561* *Support: serv...@

Re: [VoiceOps] Recommended Website/IP monitoring tool

I use and like Monitis for outside SIP testing, ping testing, WWW page loading, etc. On Thu, Feb 11, 2016 at 1:28 PM, Li Tiatia wrote: > Hi All, > Anyone have any suggestions on recommended website/IP monitoring tools? > There are so many out there and just need help to narrow the list down > ba

Re: [VoiceOps] VoIP Monitor - How do you roll ?

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-boun...@voiceops.org] On Behalf Of Christopher Aloi Sent: Thursday, February 11, 2016 11:35 AM To: Carlos Alvarez

Re: [VoiceOps] Recommended Website/IP monitoring tool

I use and like StatusCake.com as a hosted monitoring provider, and SmokePing as an internally-managed monitoring tool. StatusCake has been reliable, and offers nice features such as worldwide monitoring endpoints, outage confirmation, configurable paging methods and thresholds, etc. They also

[VoiceOps] Recommended Website/IP monitoring tool

Hi All, Anyone have any suggestions on recommended website/IP monitoring tools? There are so many out there and just need help to narrow the list down based on what you're using or have good experience with. Thank you. *_* *Li Tiatia* _

Re: [VoiceOps] VoIP Monitor - How do you roll ?

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 wrote: > Chris must hav

Re: [VoiceOps] VoIP Monitor - How do you roll ?

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 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/lega

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 ra

Re: [VoiceOps] VoIP Monitor - How do you roll ?

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 wrote: > >> On 02/11/2016 02:21 PM, Carlos Alvarez wrote: >> >> Chris must have one hell of

Re: [VoiceOps] VoIP Monitor - How do you roll ?

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 / c

Re: [VoiceOps] VoIP Monitor - How do you roll ?

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, inclu

Re: [VoiceOps] VoIP Monitor - How do you roll ?

Yes. You can limit the port that the sniffer captured on. > On Feb 11, 2016, at 12:15 PM, Alex Balashov 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 wi

Re: [VoiceOps] VoIP Monitor - How do you roll ?

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

Re: [VoiceOps] VoIP Monitor - How do you roll ?

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 mailto:caalva...@gmail.com>> wrote: Doesn't an

Re: [VoiceOps] VoIP Monitor - How do you roll ?

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 wrote: > Hey Ev

[VoiceOps] VoIP Monitor - How do you roll ?

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 re