<HTML><HEAD>
<STYLE type=text/css>p { margin: 0; }</STYLE>
<META http-equiv=Content-Type content="text/html; charset=UTF-8">
<META content="MSHTML 6.00.2900.3660" name=GENERATOR></HEAD>
<BODY>
<DIV>I think what happened was a user tried to address a message to an Allision but unfortunately selected the All Voice Mail Users System Distribution List. I am thinking that if I moved this System DL to a new partition that users do not have in their Calling Search Space this would eliminate the potential for accidental access. </DIV>
<DIV> </DIV>
<DIV>Steve<BR><BR>>>> STEVEN CASPER <SCASPER@mtb.com> 4/12/2010 11:59 AM >>><BR></DIV>
<DIV>Thanks for the reminder, I had forgotten about the MWI issue. Funny thing is we have our MWI ports throttled back because we had this issue when a nightly MWI synch was run. Maybe a combination of normal Monday morning call processing and the MWI/Voice mail retrievals associated with the broadcast pushed it over the edge. </DIV>
<DIV> </DIV>
<DIV>Steve<BR><BR>>>> Lelio Fulgenzi <lelio@uoguelph.ca> 4/12/2010 11:44 AM >>><BR></DIV>
<DIV style="FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY: Verdana">Wes commented on a similar situation we had not too long ago.<BR><BR>I think it came down to reducing the number of ports that can do MWIs and lowering the frequency of sending those MWIs out.<BR><BR>A search of the archives will point you in the right direction.<BR><BR>http://cisco-voip.markmail.org/search/?q=MWI connection#query:MWI connection+page:1+mid:f6fpgia4hhz4x7du+state:results<BR><BR>http://cisco-voip.markmail.org/search/?q=MWI connection#query:MWI connection+page:3+mid:pxfbcg2uiofgvslw+state:results<BR><BR>---<BR>Lelio Fulgenzi, B.A.<BR>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<BR>Cooking with unix is easy. You just sed it and forget it. <BR> - LFJ (with apologies to Mr. Popeil)<BR><BR><BR>----- Original Message -----<BR>From: "STEVEN CASPER" <SCASPER@mtb.com><BR>To: cisco-voip@puck.nether.net<BR>Sent: Monday, April 12, 2010 11:35:19 AM GMT -05:00 US/Canada Eastern<BR>Subject: [cisco-voip] Connection Broadcast messages and Code Yellow alarm<BR><BR>
<DIV>
<DIV> We had a user inadvertently send a Unity Connection Broadcast message to the entire company. This caused a 25 minute rolling Code Yellow condition on one of our primary Call Manager subscribers. Any ideas how to throttle this condition? </DIV>
<DIV> </DIV>
<DIV>Thanks</DIV>
<DIV>Steve </DIV>
<DIV> </DIV><A href="mailto:cisco-voip@puck.nether.net" target=_blank></A></DIV><PRE>************************************
This email may contain privileged and/or confidential information that is intended solely for the use of the addressee. If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information.
There are risks associated with the use of electronic transmission. The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission.
************************************
</PRE><BR>_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip </DIV><PRE>************************************
This email may contain privileged and/or confidential information that is intended solely for the use of the addressee. If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information.
There are risks associated with the use of electronic transmission. The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission.
************************************
</PRE><pre>************************************
This email may contain privileged and/or confidential information that is intended solely for the use of the addressee. If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information.
There are risks associated with the use of electronic transmission. The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission.
************************************
</pre></BODY></HTML>