March 2016 - VoiceOps - lists.voiceops.org

Maintenance for Performance Technologies SEGway
by scott＠socket.net May 17, 2017

May 17, 2017

We have been using a set of PTI SEGway x201s with point code emulation for a number of years now. We also have an unlicensed spare in stock. The maintenance contract renewals are due and the two quotes I've received are quite high. I know of at least one other company that has chosen to drop the vendor maintenance and take care of that in-house. I would like to hear from anyone that is currently using SEGways and find out what they chose to do for maintenance. I would also be very interested to hear of any bad experiences from chosing the in-house option. Thanks. Scott Stratman Network Facilities Manager SOCKET 573-999-4376 scott at socket.net 1-800-SOCKET-3 www.socket.net

3 2

Who is doing MMS?
by colton.conor＠gmail.com March 30, 2016

March 30, 2016

I would like to know what hosted voice providers are offering MMS integrated into their product? I know quite a few that are offering SMS, but barely anyone seems to offer MMS. What wholesale providers offer MMS enabled DIDs?

4 3

SAP SMS Deliverability - SAP?
by beckman＠angryox.com March 30, 2016

March 30, 2016

Does anyone use SAP SMS 365 directly? We get SMS messages delivered from SAP to Layered to Vitelity. For the last 8 hours we've seen SMS delivery delays of 10+ seconds to over 800 seconds, and I'm hearing that SAP is to blame. Has anyone else noticed this? Does anyone on the list do SMS? Beckman --------------------------------------------------------------------------- Peter Beckman Internet Guy beckman at angryox.com http://www.angryox.com/ ---------------------------------------------------------------------------

1 0

Looking for a good defense for a bad VoIP provider
by aaron＠heyaaron.com March 28, 2016

March 28, 2016

I'll try to make this short: I am an IT contractor for "Company X" that has ~26 offices around the western US. We are paid a flat fee to manage every office, keep things secure, train and assist users, etc... About two weeks ago, offices suddenly started going offline. After 15-20 minutes of frantically digging, we got a call from a VoIP provider who was apparently told by Company X "we want to use your VoIP service, go get it installed at all our offices". This VoIP provider walked in to several off the offices and just started yanking out switches that had various VLANs running on them and replacing them with their own Netgear PoE switches with no config and default passwords. They took down tons of virtual servers and SANs. We spent the better part of a week ripping their stuff out and putting the network back the way it was. We had a brief meeting with the VoIP provider and told them things need to be planned in advance and we would be happy to work with them to get things going. We set up a VLAN for VoIP traffic and told them how to cross-connect their switch to ours, what IP ranges to use, and even set up a VPN connection at each office so they could access the equipment remotely. They they scheduled 6 installs in 3 days and with no testing or communication they came in and hooked things up. I received repeated phone calls in the evenings, mornings, and weekends that they needed huge swaths of ports forwarded so they could remotely program phones and the phone server. And of course it was all an emergency. As in "we ported the numbers over already and the office is opening in 15 minutes, just forward the damn ports". We were even told the 6 installs could not be stopped or re-scheduled because the VoIP provider 'went out' on the equipment and really needs to finish the install so they can recoup their money. The disaster should be coming to a close this weekend, and I'm trying to clean up and gather information for a report to the CEO. My main concerns are: * We set up VPN connections. The VoIP guys aren't using them. They don't have time to test and/or troubleshoot any issues they are complaining about. * The devices all have static IPs instead of using DHCP. The phones appear to get a DHCP address off VLAN 100 properly, but when it's time for a renewal they drop the VLAN tag, get switched to the wrong network, and lose communication. * We were told to set up port forwards to every phone's *HTTP* interface as well as a forward to the phone server HTTPS interface. * Most passwords appear to be factory defaults * The CEO of Company X was told the port forward must remain in place and they can not be disabled for 'security reasons' because VoIP phone are not a computer and therefore can't be hacked. (Seriously?!?!! Who cares about hacking when your equipment has default passwords...) * They skimped on proper wiring in a lot of places and have computers jumpered through the phones * Because of that, the phones are self-tagging packets with VLAN 100 and the jumpered workstations are un-tagged which required us to accept un-tagged packets on to the network containing patient data. * If the phones or phone server gets compromised, it seems like it would be real easy to simply drop the VLAN tag and have access to a network containing patient data. * A quick sniff at our WAN interface shows all the calls and communication are happening with a server over HTTP. I was able to capture voice data in the clear containing patient information, credit card details, etc... I have worked with professional VoIP companies before. When they do it right, the networks are isolated, phones have their own network drops, no ports are exposed to the internet, etc... The CEO of Company X appears to only have been informed that the offices were 'switching to VoIP to save costs' and nothing more. He is a very data-oriented guy and loves technical documentation. When we make our case to him, I'd like to back it up with as much 'best practice references' as possible. Are there any best-practice documents out there I can provide to the CEO? I know what this provider is doing is horribly wrong and insecure, but the CEO is the kind of person who wants documentation from lots of sources to back it up. Basically the phone guys are blaming us for all the problems, and we are blaming them for causing several thousand dollars in after-hours emergency site visits and remote work because of poor planning, scheduling, and simply ripping out equipment they know nothing about. (In addition to making the network insecure as hell and not doing their due diligence.) Thanks for listening. :) -A

9 14

XMPP to SIP Gateway
by peter＠4isps.com March 23, 2016

March 23, 2016

thanks for all the input. It will have to be done in-house. On 3/22/2016 5:41 PM, Jorge Guntanis wrote: > You can do this with ejabberd and opensips relatively easily. As far > as companies doing this as a service, depending on your budget process > one might be able to help, but they are on the high end of the > spectrum and a bit condescending. Hope that helps. Jorge G > On Tue, Mar 22, 2016 at 2:09 PM Peter Rad. <peter at 4isps.com > <mailto:peter at 4isps.com>> wrote: > > btw, Microsoft OCS actually works as a XMPP/SIP gateway > > On 3/22/2016 1:41 PM, Erik Flournoy wrote: >> "Sent from my BlackBerry." >> >> Those are still out there >> >> Erik Flournoy >> 808-426-4527 >> 301-218-7325 >> >> CONFIDENTIALITY NOTICE >> This e-mail message, including any attachments from EESPRO.com - >> contain information which is CONFIDENTIAL AND/OR LEGALLY >> PRIVILEGED. The information is intended only for the use of the >> individual named above and may not be disseminated to any other >> party without written permission. If you are not the intended >> recipient, or the employee or agent responsible for delivering >> the message to the intended recipient, you are hereby notified >> that any dissemination, disclosure, distribution, copying or >> taking of any action in reliance on the contents of this e-mailed >> information is strictly prohibited. If you have received this >> transmission in error, please immediately notify i >> <mailto:info at eespro.com>nfo at eespro.com <mailto:nfo at eespro.com>, >> and permanently delete this e-mail and the attachments hereto, if >> any, and destroy any printout thereof. >> >> On Tue, Mar 22, 2016 at 3:18 AM, Alex Balashov >> <abalashov at evaristesys.com <mailto:abalashov at evaristesys.com>> wrote: >> >> ?Peter, >> >> It can be built relatively easily using off-the-shelf FOSS >> folk traditions. The fact that they're off-the-shelf makes me >> uncertain as to whether it would qualify as a full-on >> in-house building endeavour in the traditional sense. >> >> -- >> Alex Balashov | Principal | Evariste Systems LLC >> 1447 Peachtree Street NE, Suite 700 >> Atlanta, GA 30309 >> United States >> >> Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) >> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ >> >> Sent from my BlackBerry. >> >> _______________________________________________ >> 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 >

1 0

XMPP to SIP Gateway
by peter＠4isps.com March 23, 2016

March 23, 2016

I have an enterprise prospect looking to add XMPP to SIP Gateway. Does anyone provide this? Or is this something they need to build themselves and run in-house? Thanks! Peter @ RAD-INFO INC

5 9

outsource bills printing?
by ryan＠finnesey.com March 23, 2016

March 23, 2016

I am hoping the group might have some recommendation's. I am looking for a service provider we can use to outsource the mailing and printing of bills Most of our bills are one to two pages

4 3

VoIP Innovations reliability (NeuStar DDoS
by timothyl＠voipinnovations.com March 23, 2016

March 23, 2016

Kraig, That's a great video showing the routing changes that we have made over the course of the issue, thank you for sharing. We have made a lot of changes over the course of these issues in hopes to combat and mitigate the problems being caused by these attacks. I hope to have an extensive, detailed description of the attacks and what we did at some point in the near future for Ryan's email thread about DDoS attacks. In the meantime, I can share a PR release that we made yesterday describing this mitigation addition: http://www.prweb.com/releases/2016/03/prweb13286689.htm Timothy Linn Lead Systems Engineer Voip Innovations ------------------------------ Message: 4 Date: Mon, 21 Mar 2016 21:29:15 -0400 From: Kraig Beahn <kraig at enguity.com> To: "voiceops at voiceops.org" <voiceops at voiceops.org> Subject: Re: [VoiceOps] VoIP Innovations reliability (NeuStar DDoS Mitigation Addition) Message-ID: <CALsiHpwm2FKpmiTP62vH4S5w5UGFYgAJY=JOOLJgSyQdrtkVsA at mail.gmail.com> Content-Type: text/plain; charset="utf-8" VoIP Innovations DDoS (internal ENG notes): One of our customers has used VI since at least 2009, for specific (unique) types of ingress traffic for which it was not prudent [cost-effective] for us to on-ramp to our national TDM network, i.e., select rural off-net markets. They've had their ups and downs with VI, but, for the most part, VI's progressively increased in reliability...until the recent DDoS events. That said - when the DDoS issues started popping up, we were left with the same intrigue as most other VI consumers on this list. Is this really a DDoS style issue/attack? If so - what kind of DDoS issue, what can we do to help, if anything? And , if not - what's really going on and how quickly can we "jump ship"... Interestingly, and cautiously, without pushing out any more information than what is already known to the public, or is publically accessible, we can confirm that they are, in fact, and as of late, using *NeuStar's DDoS mitigation services*.* It also appears, based on BGP data, that the latest maintenance window was to integrate fully such systems.* Our engineering team created a pretty intriguing video for an internal update on the issue, showing the AS paths of their primary and secondary SBC's, which, if you follow the timeline and the ending ASN's, at least, in our opinion, show VI's commitment level. That said - kudos to the VI team, and as frustrated as our team has been, the last thought that always comes to mind is "it could have any of us". http://cdn.enguity.com/vid/VoIPInnovations-DDoS-Mitigation-2016.mp4 ...just a thought On Wed, Mar 16, 2016 at 12:30 PM, Tim Linn <timothyl at voipinnovations.com> wrote: > > > All, > > > > I can confirm that we did have 2 outages this morning spanning little > over an hour due to another DDoS attack. > > > > We have been careful of the information that we have been giving out > in public updates due to the possibility of the attacker reading that > information and using it against us in some way. > > > > The biggest change that we?ve made to combat this is a DDoS protection > service, which has caught a handful of attacks, but was largely > useless in this latest attack. We?ve made mitigating changes to our > existing setup which appears to have stopped today?s attack so far. > > > > We do have a disaster recovery site and have, honestly, appear to have > done a poor job communicating that to our customers. If you are a Voip > Innovations customer, please contact me for the IP address of the > disaster recovery site. During these outages, the site was taking > origination calls from most of our DID vendors. We?re currently > working on figuring out why all of them did not switch over. > > > > I know that words aren?t much right now, but I am truly sorry for the > issues that you have been having. I understand the importance of > reliability to you and your customers, and I know that those > expectations have not been met over the last few weeks. We are working > diligently with several different companies to continue to make > changes to our network to mitigate these attacks. The changes have > been successful for a number of the attacks that we have seen, but > it?s clear that we are still vulnerable and have work to do. > > > > Please contact me if you have any questions, and I will do my best to > answer. > > > > > > *Timothy Linn* > > *Lead Systems Engineer* > > *Voip Innovations* > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Wed, 16 Mar 2016 11:24:04 -0400 > > From: Jeff Waddell <jeff+voiceops at waddellsolutions.com> > > To: Nathan Anderson <nathana at fsr.com> > > Cc: Nate Burke <nate at blastcomm.com>, "voiceops at voiceops.org" > > <voiceops at voiceops.org> > > Subject: Re: [VoiceOps] VoIP Innovations reliability > > Message-ID: > > < > CAO+x49LG2+RQyRU6a0zmgdgaAKd0yYyxASHm6+=9z97iDxjMqA at mail.gmail.com> > > Content-Type: text/plain; charset="utf-8" > > > > Not that it helps a lot - this was posted on the VI facebook page > > > > "[Update] As of this morning, we regret to inform you that we are > again currently experiencing issues that are related to the DDoS > attack being committed by unknown parties against our network. Our > Network Engineers are currently working diligently with our upstream > carriers as well as a network security firm to combat the attack and > will continue to do so until all of the issues are resolved. Our > Senior Leadership has also been in contact with the FBI. The FBI is > considering these events a national security issue due to the number > of firms impacted, the magnitude of the attacks, and the persistence > of these attacks. The Social Media Team will post here the very moment we have further information." > > > > On Wed, Mar 16, 2016 at 10:29 AM, Nathan Anderson <nathana at fsr.com> wrote: > > > > > Down again. **** me. > > > > > > > > > > > > -- Nathan > > > > > > > > > > > > *From:* VoiceOps [mailto:voiceops-bounces at voiceops.org > <voiceops-bounces at voiceops.org>] *On Behalf Of > > > *Nate Burke > > > *Sent:* Wednesday, March 16, 2016 6:51 AM > > > > > > *To:* voiceops at voiceops.org > > > *Subject:* Re: [VoiceOps] VoIP Innovations reliability > > > > > > > > > > > > Looks like it just came back up for me. Just over 30 min. > > > > > > Nate > > > > > > On 3/16/2016 8:45 AM, Shripal Daphtary wrote: > > > > > > We are experiencing an outage as well. > > > > > > Thanks, > > > > > > > > > > > > Shripal > > > > > > > > > On Mar 16, 2016, at 9:36 AM, Nate Burke <nate at blastcomm.com> wrote: > > > > > > Problems again this morning? Looks to be acting the same as it has been. > > > > > > On 3/11/2016 6:00 PM, Alexander Lopez wrote: > > > > > > I added them to our monitoring platform, stated getting alarms this > > > past hour or so. > > > > > > Up and down. > > > > > > > > > > > > -------- Original message -------- > > > From: Nathan Anderson <nathana at fsr.com> <nathana at fsr.com> > > > Date: 3/11/2016 6:31 PM (GMT-05:00) > > > To: 'Nate Burke' <nate at blastcomm.com> <nate at blastcomm.com>, > > > voiceops at voiceops.org > > > Subject: Re: [VoiceOps] VoIP Innovations reliability > > > > > > ...aaaaaand we're back. > > > > > > -- Nathan > > > > > > -----Original Message----- > > > From: VoiceOps [mailto:voiceops-bounces at voiceops.org > > > <voiceops-bounces at voiceops.org>] On Behalf Of Nathan Anderson > > > Sent: Friday, March 11, 2016 3:30 PM > > > To: 'Nate Burke'; voiceops at voiceops.org > > > Subject: Re: [VoiceOps] VoIP Innovations reliability > > > > > > It *feels* like they are under attack again, since I get a response > > to > > > a ping once every 20 or so. > > > > > > -- Nathan > > > > > > -----Original Message----- > > > From: VoiceOps [mailto:voiceops-bounces at voiceops.org > > > <voiceops-bounces at voiceops.org>] On Behalf Of Nathan Anderson > > > Sent: Friday, March 11, 2016 3:28 PM > > > To: 'Nate Burke'; voiceops at voiceops.org > > > Subject: Re: [VoiceOps] VoIP Innovations reliability > > > > > > Confirmed. > > > > > > -- Nathan > > > > > > -----Original Message----- > > > From: VoiceOps [mailto:voiceops-bounces at voiceops.org > > > <voiceops-bounces at voiceops.org>] On Behalf Of Nate Burke > > > Sent: Friday, March 11, 2016 3:26 PM > > > To: voiceops at voiceops.org > > > Subject: Re: [VoiceOps] VoIP Innovations reliability > > > > > > Anyone else show them down again right now? My traceroutes aren't > > > even leaving Chicago. Dying at a Chicago hop on Level3. > > > > > > Nate > > > > > > On 3/6/2016 6:50 PM, Nathan Anderson wrote: > > > > Did anybody else just suffer another 45-minute-ish long outage > > > from > > > about 4:00p PST to 4:45p PST (ending about 5 minutes ago)? > > > > > > > > -- Nathan > > > > > > > > -----Original Message----- > > > > From: frnkblk at iname.com [mailto:frnkblk at iname.com > > > > <frnkblk at iname.com>] > > > > Sent: Sunday, March 06, 2016 4:43 PM > > > > To: Nathan Anderson; voiceops at voiceops.org > > > > Subject: RE: VoIP Innovations reliability > > > > > > > > More here: http://blog.voipinnovations.com/blog > > > > > > > > Frank > > > > > > > > -----Original Message----- > > > > From: VoiceOps [mailto:voiceops-bounces at voiceops.org > > > <voiceops-bounces at voiceops.org>] On Behalf Of Nathan > > > > Anderson > > > > Sent: Tuesday, March 01, 2016 8:27 PM > > > > To: voiceops at voiceops.org > > > > Subject: [VoiceOps] VoIP Innovations reliability > > > > > > > > Holy schlamoly. Anybody else use them here and being handed > > > outage > > > > after outage over the last 2 days? Seriously thinking at this > > > point > > > > about > > > doing > > > > something else. This is ridiculous. > > > > > > > > I desperately need sleep and if my cell goes off one more time... > > > > > > > > -- Nathan > > > > _______________________________________________ > > > > 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 > > > > > > _______________________________________________ > > > 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 > > > > > > > >

1 0

VoIP Innovations reliability (NeuStar DDoS Mitigation Addition)
by kraig＠enguity.com March 22, 2016

March 22, 2016

VoIP Innovations DDoS (internal ENG notes): One of our customers has used VI since at least 2009, for specific (unique) types of ingress traffic for which it was not prudent [cost-effective] for us to on-ramp to our national TDM network, i.e., select rural off-net markets. They've had their ups and downs with VI, but, for the most part, VI's progressively increased in reliability...until the recent DDoS events. That said - when the DDoS issues started popping up, we were left with the same intrigue as most other VI consumers on this list. Is this really a DDoS style issue/attack? If so - what kind of DDoS issue, what can we do to help, if anything? And , if not - what's really going on and how quickly can we "jump ship"... Interestingly, and cautiously, without pushing out any more information than what is already known to the public, or is publically accessible, we can confirm that they are, in fact, and as of late, using *NeuStar's DDoS mitigation services*.* It also appears, based on BGP data, that the latest maintenance window was to integrate fully such systems.* Our engineering team created a pretty intriguing video for an internal update on the issue, showing the AS paths of their primary and secondary SBC's, which, if you follow the timeline and the ending ASN's, at least, in our opinion, show VI's commitment level. That said - kudos to the VI team, and as frustrated as our team has been, the last thought that always comes to mind is "it could have any of us". http://cdn.enguity.com/vid/VoIPInnovations-DDoS-Mitigation-2016.mp4 ...just a thought On Wed, Mar 16, 2016 at 12:30 PM, Tim Linn <timothyl at voipinnovations.com> wrote: > > > All, > > > > I can confirm that we did have 2 outages this morning spanning little over > an hour due to another DDoS attack. > > > > We have been careful of the information that we have been giving out in > public updates due to the possibility of the attacker reading that > information and using it against us in some way. > > > > The biggest change that we?ve made to combat this is a DDoS protection > service, which has caught a handful of attacks, but was largely useless in > this latest attack. We?ve made mitigating changes to our existing setup > which appears to have stopped today?s attack so far. > > > > We do have a disaster recovery site and have, honestly, appear to have > done a poor job communicating that to our customers. If you are a Voip > Innovations customer, please contact me for the IP address of the disaster > recovery site. During these outages, the site was taking origination calls > from most of our DID vendors. We?re currently working on figuring out why > all of them did not switch over. > > > > I know that words aren?t much right now, but I am truly sorry for the > issues that you have been having. I understand the importance of > reliability to you and your customers, and I know that those expectations > have not been met over the last few weeks. We are working diligently with > several different companies to continue to make changes to our network to > mitigate these attacks. The changes have been successful for a number of > the attacks that we have seen, but it?s clear that we are still vulnerable > and have work to do. > > > > Please contact me if you have any questions, and I will do my best to > answer. > > > > > > *Timothy Linn* > > *Lead Systems Engineer* > > *Voip Innovations* > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Wed, 16 Mar 2016 11:24:04 -0400 > > From: Jeff Waddell <jeff+voiceops at waddellsolutions.com> > > To: Nathan Anderson <nathana at fsr.com> > > Cc: Nate Burke <nate at blastcomm.com>, "voiceops at voiceops.org" > > <voiceops at voiceops.org> > > Subject: Re: [VoiceOps] VoIP Innovations reliability > > Message-ID: > > < > CAO+x49LG2+RQyRU6a0zmgdgaAKd0yYyxASHm6+=9z97iDxjMqA at mail.gmail.com> > > Content-Type: text/plain; charset="utf-8" > > > > Not that it helps a lot - this was posted on the VI facebook page > > > > "[Update] As of this morning, we regret to inform you that we are again > currently experiencing issues that are related to the DDoS attack being > committed by unknown parties against our network. Our Network Engineers are > currently working diligently with our upstream carriers as well as a > network security firm to combat the attack and will continue to do so until > all of the issues are resolved. Our Senior Leadership has also been in > contact with the FBI. The FBI is considering these events a national > security issue due to the number of firms impacted, the magnitude of the > attacks, and the persistence of these attacks. The Social Media Team will > post here the very moment we have further information." > > > > On Wed, Mar 16, 2016 at 10:29 AM, Nathan Anderson <nathana at fsr.com> wrote: > > > > > Down again. **** me. > > > > > > > > > > > > -- Nathan > > > > > > > > > > > > *From:* VoiceOps [mailto:voiceops-bounces at voiceops.org > <voiceops-bounces at voiceops.org>] *On Behalf Of > > > *Nate Burke > > > *Sent:* Wednesday, March 16, 2016 6:51 AM > > > > > > *To:* voiceops at voiceops.org > > > *Subject:* Re: [VoiceOps] VoIP Innovations reliability > > > > > > > > > > > > Looks like it just came back up for me. Just over 30 min. > > > > > > Nate > > > > > > On 3/16/2016 8:45 AM, Shripal Daphtary wrote: > > > > > > We are experiencing an outage as well. > > > > > > Thanks, > > > > > > > > > > > > Shripal > > > > > > > > > On Mar 16, 2016, at 9:36 AM, Nate Burke <nate at blastcomm.com> wrote: > > > > > > Problems again this morning? Looks to be acting the same as it has been. > > > > > > On 3/11/2016 6:00 PM, Alexander Lopez wrote: > > > > > > I added them to our monitoring platform, stated getting alarms this > > > past hour or so. > > > > > > Up and down. > > > > > > > > > > > > -------- Original message -------- > > > From: Nathan Anderson <nathana at fsr.com> <nathana at fsr.com> > > > Date: 3/11/2016 6:31 PM (GMT-05:00) > > > To: 'Nate Burke' <nate at blastcomm.com> <nate at blastcomm.com>, > > > voiceops at voiceops.org > > > Subject: Re: [VoiceOps] VoIP Innovations reliability > > > > > > ...aaaaaand we're back. > > > > > > -- Nathan > > > > > > -----Original Message----- > > > From: VoiceOps [mailto:voiceops-bounces at voiceops.org > > > <voiceops-bounces at voiceops.org>] On Behalf Of Nathan Anderson > > > Sent: Friday, March 11, 2016 3:30 PM > > > To: 'Nate Burke'; voiceops at voiceops.org > > > Subject: Re: [VoiceOps] VoIP Innovations reliability > > > > > > It *feels* like they are under attack again, since I get a response to > > > a ping once every 20 or so. > > > > > > -- Nathan > > > > > > -----Original Message----- > > > From: VoiceOps [mailto:voiceops-bounces at voiceops.org > > > <voiceops-bounces at voiceops.org>] On Behalf Of Nathan Anderson > > > Sent: Friday, March 11, 2016 3:28 PM > > > To: 'Nate Burke'; voiceops at voiceops.org > > > Subject: Re: [VoiceOps] VoIP Innovations reliability > > > > > > Confirmed. > > > > > > -- Nathan > > > > > > -----Original Message----- > > > From: VoiceOps [mailto:voiceops-bounces at voiceops.org > > > <voiceops-bounces at voiceops.org>] On Behalf Of Nate Burke > > > Sent: Friday, March 11, 2016 3:26 PM > > > To: voiceops at voiceops.org > > > Subject: Re: [VoiceOps] VoIP Innovations reliability > > > > > > Anyone else show them down again right now? My traceroutes aren't > > > even leaving Chicago. Dying at a Chicago hop on Level3. > > > > > > Nate > > > > > > On 3/6/2016 6:50 PM, Nathan Anderson wrote: > > > > Did anybody else just suffer another 45-minute-ish long outage from > > > about 4:00p PST to 4:45p PST (ending about 5 minutes ago)? > > > > > > > > -- Nathan > > > > > > > > -----Original Message----- > > > > From: frnkblk at iname.com [mailto:frnkblk at iname.com > > > > <frnkblk at iname.com>] > > > > Sent: Sunday, March 06, 2016 4:43 PM > > > > To: Nathan Anderson; voiceops at voiceops.org > > > > Subject: RE: VoIP Innovations reliability > > > > > > > > More here: http://blog.voipinnovations.com/blog > > > > > > > > Frank > > > > > > > > -----Original Message----- > > > > From: VoiceOps [mailto:voiceops-bounces at voiceops.org > > > <voiceops-bounces at voiceops.org>] On Behalf Of Nathan > > > > Anderson > > > > Sent: Tuesday, March 01, 2016 8:27 PM > > > > To: voiceops at voiceops.org > > > > Subject: [VoiceOps] VoIP Innovations reliability > > > > > > > > Holy schlamoly. Anybody else use them here and being handed outage > > > > after outage over the last 2 days? Seriously thinking at this point > > > > about > > > doing > > > > something else. This is ridiculous. > > > > > > > > I desperately need sleep and if my cell goes off one more time... > > > > > > > > -- Nathan > > > > _______________________________________________ > > > > 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 > > > > > > _______________________________________________ > > > 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 > > > > > > > >

1 0

FW: [outages] Verizon FiOS Issues
by frnkblk＠iname.com March 21, 2016

March 21, 2016

FYI, from the outages listserv. From: Outages [mailto:outages-bounces at outages.org] On Behalf Of Dovid Bender via Outages Sent: Monday, March 21, 2016 1:49 PM To: outages at outages.org Subject: [outages] Verizon FiOS Issues For a little over two hours now there have been issues reaching PSTN numbers on VZ FiOS in the NY/NJ area including from Verizon Wireless to Verizon FiOS.

1 0