[188580] in North American Network Operators' Group
RE: Best practices for sending network maintenance notifications
daemon@ATHENA.MIT.EDU (Ray Orsini)
Wed Apr 6 16:56:19 2016
X-Original-To: nanog@nanog.org
From: Ray Orsini <ray@orsiniit.com>
In-Reply-To: <alpine.BSF.2.20.1604061648570.80272@cnex.qbaryna.pbz>
Date: Wed, 6 Apr 2016 16:56:14 -0400
To: Sean Donelan <sean@donelan.com>, nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
"The other "don't do that" is never configure Music on Hold for any NOC/SOC
lines. Few things are more annoying than a eight hour trouble shooting
conference bridge, and one of the dozen NOC/SOCs on the bridge hits the Hol=
d
button."
Now that you've said it it seems so obvious. But, honestly I'd never though=
t
it until right now. Thanks!
Regards,
Ray Orsini =E2=80=93 CEO
Orsini IT, LLC =E2=80=93 Technology Consultants
VOICE =EF=82=96DATA =EF=82=96 BANDWIDTH =EF=82=96 SECURITY =EF=82=96 SUPPOR=
T
P: 305.967.6756 x1009 E: ray@orsiniit.com TF: 844.OIT.VOIP
7900 NW 155th Street, Suite 103, Miami Lakes, FL 33016
http://www.orsiniit.com | View My Calendar | View/Pay Your Invoices | View
Your Tickets
-----Original Message-----
From: NANOG [mailto:nanog-bounces@nanog.org] On Behalf Of Sean Donelan
Sent: Wednesday, April 6, 2016 4:53 PM
To: nanog@nanog.org
Subject: Re: Best practices for sending network maintenance notifications
On Wed, 6 Apr 2016, Dan Mahoney, System Admin wrote:
> My question for the group -- does anyone know if there's a "best
> practices"
> for sending maint notifications like this? An RFC sort of thing?
It falls in the category of "Doctor, it hurts when I do this. Don't do
that." Even the most dense CSR managers figure it out after a few attempts=
.
The other "don't do that" is never configure Music on Hold for any NOC/SOC
lines. Few things are more annoying than a eight hour trouble shooting
conference bridge, and one of the dozen NOC/SOCs on the bridge hits the Hol=
d
button.
