Best practices for sending network maintenance notifications

[eric.kuhnke at gmail.com (Eric Kuhnke)]

And some genius at an ISP's NOC has put
rick_asley_never_gonna_give_you_up.mp3 in the their hold queue music
rotation list.

On Wed, Apr 6, 2016 at 1:56 PM, Ray Orsini <ray at orsiniit.com> wrote:

> "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
> Hold
> button."
>
>
> Now that you've said it it seems so obvious. But, honestly I'd never
> thought
> it until right now. Thanks!
>
> Regards,
> Ray Orsini ? CEO
> Orsini IT, LLC ? Technology Consultants
> VOICE ?DATA ? BANDWIDTH ? SECURITY ? SUPPORT
> P: 305.967.6756 x1009   E: ray at 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 at nanog.org] On Behalf Of Sean Donelan
> Sent: Wednesday, April 6, 2016 4:53 PM
> To: nanog at 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
> Hold
> button.
>