<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>Since Unity Connection was considered primarily a VM only solution<span>, I'm guessing they left the email notification part out. :(<br><br>If you're creating dummy extensions that no one dials, then you should be able to check 'all messages' and continue with the status quo. Not ideal, but you should be able to get it working.<br><br><span name="x"></span>---<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 (ANNU)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)<br><span name="x"></span><br></span><br><hr id="zwchr"><b>From: </b>"Hyoun Kim" <hkim@ohl.com><br><b>To: </b>"cisco-voip@puck.nether.net (cisco-voip@puck.nether.net)" <cisco-voip@puck.nether.net><br><b>Sent: </b>Tuesday, June 19, 2012 4:18:18 PM<br><b>Subject: </b>[cisco-voip] Message Notifications for E-mail via Unity Connection<br><br>
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:1031564842;
mso-list-type:hybrid;
mso-list-template-ids:-990476496 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="Section1">
<p class="MsoNormal">Hi all,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Sorry for this long email, but I need professional opinions on an issue we’re having with Message Notification and also opinions of what options I have. After battling constant issues with Unity 7.0.2 over the past several months, our
Unity cluster finally died (MAPI connection failed and never recovered)and after a 26.5 straight hours of a Cisco TAC call (we went through 5 different engineers, rotating shifts), we pulled the plug and had an emergency overnight purchase & build of a Cisco
Unity Connection 8.6.2 cluster from our IT equipment vendor.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">After doing the COBRAS backup & restore, we found that everything was working just like the original Unity cluster except one configuration: Message Notification.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Our previous setup in Unity 7.0.2 utilized Message Notification for our company-wide On-Call system. The functionality of our on-call system was set up by previous employees, but I found it to be rather crude. It’s setup as follows:</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">We created several non-published Exchange mailboxes for each department within IT. In Unity, we tied a unique (nonpublished) extension to the Exchange account and then utilized another unique extension for on-call. Within message notification
in Unity, we monitored the exchange account for “EMAILS ONLY”. The point of this setup is so that any of our monitoring devices that had alerts setup to email that unpublished Exchange mailbox and Unity would see that, then trigger the message notification,
which then would call the person on call to alert them of the emergency.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">So for example, say Windows Team had the email <a href="mailto:WindowsOncall@example.com" target="_blank">
WindowsOncall@example.com</a>. We had a Unity extension for 1234 tied to that email. At the same time, extension 7890 was created on CUCM and a forward-all was set to dial that person’s cell phone. By using message notification on Unity, say Orion Solarwinds
had an alert that a server died. That alert would email <a href="mailto:WindowsOncall@example.com" target="_blank">
WindowsOncall@example.com</a> and because extension 7890 was the phone number configured, it would call that number every time that email received an email. This is how all 28 different IT departments utilized an oncall-rotation.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">After swapping to Unity Connection 8.6.2, we found that the Notification Devices only lists the following as available for notification: “All Voice Messages”, “Dispatch Messages”, “Fax Messages”. The regular Email Messages option is missing.
We’ve tried to rig it similar to the old Unity but nothing is working. Upper management is upset because now their age-old way of just being able to email specific emails to *<b>call</b>* people that something’s going down/wrong is no longer available.</p>
<p class="MsoNormal"> </p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span>Does anyone know why the Email Messages option is missing in Cisco Unity Connection?</p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span>Other than the traditional way of oncall (passing around an oncall pager or cell phone), what other solutions are available (3<sup>rd</sup> party welcome).</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Most importantly, they want the ability to call (not SMS) the on-call phones. They feel that people are much more responsive to actual calls than text messages.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Thanks in advance for any replies & assistance.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Hyoun Kim</span></b></p>
<p class="MsoNormal"><i><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Network Engineer</span></i></p>
<p class="MsoNormal"><i><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Network Infrastructure</span></i></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">OHL</span></b></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""> </span></p>
<p class="MsoNormal"><i><span style="font-size:8.0pt;font-family:"Arial","sans-serif";
color:black">This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it
is addressed. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient’s designees is strictly prohibited. If you are not the intended recipient or their designee, please notify the sender immediately
by return e-mail and delete all copies.</span></i><span style="font-size:10.0pt;font-family:"Arial","sans-serif""></span></p>
<p class="MsoNormal"> </p>
</div>
<br clear="all">
______________________________________________________<br>
<br>
This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you are not the intended recipient or their designee, please notify the sender immediately by return e-mail and delete all copies.<br>
<br>_______________________________________________<br>cisco-voip mailing list<br>cisco-voip@puck.nether.net<br>https://puck.nether.net/mailman/listinfo/cisco-voip<br></div></body></html>