<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1">
<TITLE>Re: [cisco-voip] Message Waiting Indication Fixes?</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Thanks! How do I restart the service? Do I de_activate then re-activate?<BR>
<BR>
Steve Miller<BR>
Telecom Engineer<BR>
Dickstein Shapiro LLP<BR>
1825 Eye Street NW | Washington, DC 20006<BR>
Tel (202) 420-3370<BR>
Fax (202)-330-5607<BR>
millers@dicksteinshapiro.com<BR>
<BR>
----- Original Message -----<BR>
From: Pat Hayes <pat-cv@wcyv.com><BR>
To: Ocampo, Walter <WOCAMPO@broward.org><BR>
Cc: Peterson_Erik@aac.com <Peterson_Erik@aac.com>; cisco-voip@puck.nether.net <cisco-voip@puck.nether.net>; Miller, Steve<BR>
Sent: Wed Jun 27 18:34:59 2007<BR>
Subject: Re: [cisco-voip] Message Waiting Indication Fixes?<BR>
<BR>
A good tip indeed, but the $UCInbox view applies to Domino integrations<BR>
and the original poster said they have an Exchange integration.<BR>
<BR>
Steve - I'd suggest you check your app log. When a resync starts and<BR>
finishes, it writes an informational (not error or warning) message from<BR>
CiscoUnity_Notifier to the event log. Filter on those to find what has<BR>
been going on.<BR>
<BR>
MWI will be out of sync for at least some people until the resync<BR>
finishes. So, if you filter as per above and see that the last message<BR>
indicated it was starting a resync, things are going to be messed up<BR>
until you can get it to finish.<BR>
<BR>
One last thing - I've seen the resync process take waaay longer than<BR>
normal after an exchange outage. If you had one of those, I'd suggest<BR>
restarting the AvMsgStoreMonitorSvc (which, will kick off another<BR>
resync...but in theory, it'll be much faster :-) ).<BR>
<BR>
HTH,<BR>
Pat<BR>
<BR>
-------- Original Message --------<BR>
From: "Ocampo, Walter" <WOCAMPO@broward.org><BR>
To: Peterson_Erik@aac.com, cisco-voip@puck.nether.net<BR>
Subject: Re:[cisco-voip] Message Waiting Indication Fixes?<BR>
Date: 6/27/2007 4:47 PM<BR>
<BR>
> This is a tip from Cisco Unity Deployment and solutions guide.<BR>
><BR>
> A useful troubleshooting tip if unity reports incorrect voice messages counts or MWI lamps does not activate as expected is to look in the ($UCInbox) and see the messages appearing. If a message appear in the regular inbox but not the ($UCInbox), that message likely does not have the UCInbox field present. Moreover, the router task concludes that the recipient is not DUC-enable.<BR>
><BR>
> Regards,<BR>
><BR>
> Walter Ocampo<BR>
> System Network Analyst<BR>
> Office of Information Technology<BR>
> 540 S.E 3rd. Ave, Suite 300<BR>
> Fort Lauderdale, FL 33301<BR>
> (954) 357 8041 Cell (954) 632 8228<BR>
> wocampo@broward.org<BR>
> <BR>
><BR>
> -----Original Message-----<BR>
> From: cisco-voip-bounces@puck.nether.net [<A HREF="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</A>] On Behalf Of Peterson_Erik@aac.com<BR>
> Sent: Wednesday, June 27, 2007 4:26 PM<BR>
> To: cisco-voip@puck.nether.net<BR>
> Subject: Re: [cisco-voip] Message Waiting Indication Fixes?<BR>
><BR>
> Also, check in the Telephony Integration Manager for how many ports are<BR>
> set to do MWI dial out.<BR>
> _______________________________________________<BR>
> cisco-voip mailing list<BR>
> cisco-voip@puck.nether.net<BR>
> <A HREF="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>
> _______________________________________________<BR>
> cisco-voip mailing list<BR>
> cisco-voip@puck.nether.net<BR>
> <A HREF="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>
<BR>
</FONT>
</P>
<P><pre wrap>--------------------------------------------------------
This e-mail message and any attached files are confidential
and are intended solely for the use of the addressee(s)
named above. This communication may contain material
protected by attorney-client, work product, or other
privileges. If you are not the intended recipient or person
responsible for delivering this confidential communication
to the intended recipient, you have received this
communication in error, and any review, use, dissemination,
forwarding, printing, copying, or other distribution of
this e-mail message and any attached files is strictly
prohibited. Dickstein Shapiro reserves the right to monitor
any communication that is created, received, or sent on its
network. If you have received this confidential
communication in error, please notify the sender
immediately by reply e-mail message and permanently delete
the original message.
To reply to our email administrator directly, send an email
to postmaster@dicksteinshapiro.com
Dickstein Shapiro LLP
http://www.DicksteinShapiro.com
==============================================================================
</pre></P></BODY>
</HTML>