[cisco-voip] Message Notifications for E-mail via Unity Connection

Tue Jun 19 22:23:49 EDT 2012

Under your Unified Messaging service configuration, is the setting for email messages to relay those messages? If so, you might have some success changing to “Accept and Relay”. You might end up having to send an email directly to Unity Connection in that instance, such as to the username at hostname or something like that.

I don’t have a good way to test that theory at the moment.

Thanks,

James Buchanan| UC Technology Manager | Presidio South | Presidio Networked Solutions
12 Cadillac Dr Ste 130 Brentwood, TN 37027 | jbuchanan at presidio.com<mailto:jbuchanan at presidio.com>
D: 615-866-5729 | F:615-866-5781  www.presidio.com<http://www.presidio.com/>

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Kim, Hyoun
Sent: Tuesday, June 19, 2012 3:40 PM
To: Lelio Fulgenzi
Cc: cisco-voip at puck.nether.net (cisco-voip at puck.nether.net)
Subject: Re: [cisco-voip] Message Notifications for E-mail via Unity Connection

Hey Lelio,

Long time no talk.  Unfortunately after testing thoroughly, even the “All Messages” setting within the Device Notification under the user in Unity Connection didn’t do anything with regular email messages.  The only thing that seemed to trigger any type of call response like the former was just voicemail messages (because “All Messages were selected)”.

In your opinion, is there any 3rd party software we could use to tie into Exchange or CUCM/Unity Connection to perform the function I’m looking for?

Thanks again for the quick response.

Hyoun Kim
Network Engineer
Network Infrastructure
OHL

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.

From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca]<mailto:[mailto:lelio at uoguelph.ca]>
Sent: Tuesday, June 19, 2012 3:32 PM
To: Kim, Hyoun
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net> (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>)
Subject: Re: [cisco-voip] Message Notifications for E-mail via Unity Connection

Since Unity Connection was considered primarily a VM only solution, I'm guessing they left the email notification part out. :(

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.

---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
                              - LFJ (with apologies to Mr. Popeil)
________________________________
From: "Hyoun Kim" <hkim at ohl.com<mailto:hkim at ohl.com>>
To: "cisco-voip at puck.nether.net (cisco-voip at puck.nether.net)<mailto:cisco-voip at puck.nether.net%20(cisco-voip at puck.nether.net)>" <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Sent: Tuesday, June 19, 2012 4:18:18 PM
Subject: [cisco-voip] Message Notifications for E-mail via Unity Connection

Hi all,

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.

After doing the COBRAS backup & restore, we found that everything was working just like the original Unity cluster except one configuration: Message Notification.

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:

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.

So for example, say Windows Team had the email WindowsOncall at example.com<mailto:WindowsOncall at example.com>.  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 WindowsOncall at example.com<mailto:WindowsOncall at example.com> 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.

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 *call* people that something’s going down/wrong is no longer available.

1.       Does anyone know why the Email Messages option is missing in Cisco Unity Connection?

2.       Other than the traditional way of oncall (passing around an oncall pager or cell phone), what other solutions are available (3rd party welcome).

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.

Thanks in advance for any replies & assistance.

Hyoun Kim
Network Engineer
Network Infrastructure
OHL

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.

______________________________________________________

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.

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

______________________________________________________

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.
This message w/attachments (message) is intended solely for the use of the intended recipient and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments.  Please be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120619/5f542213/attachment.html>