[cisco-voip] Any Way to Change a Passcode on a Unity Mailbox and Then Change it Back?.....or.......

[Miller, Steve]

On the old Nortel Meridian mailboxes it was possible to allow someone to
access the voice mailbox by disabling the passcode, making the message
play automatically and then re-arm it with the passcode afterwards. Is
there anything like that in Unity?  We are having some system problems
with certain users and it would be nice to do an acid test.  
 

Steve Miller
Telecom Engineer
Dickstein Shapiro LLP
1825 Eye Street NW | Washington, DC 20006
Tel (202) 420-3370 Fax (202)-330-5607
millers at dicksteinshapiro.com <mailto:millers at dicksteinshapiro.com>  

 

________________________________

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ed Leatherman
Sent: Thursday, March 22, 2007 9:03 PM
To: Robert Kulagowski
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] What controls how quickly Unity does a MWI
resync?


i've never seen Unity use more than 2 ports for MWI, usually only 1. no
idea why. It goes thru each account and dials out to the phone to set
the lamp to whatever it thinks it needs to be.


On 3/22/07, Robert Kulagowski <bob at smalltime.com> wrote: 

	Unity 4.2(1), 72 ports, configured for UM, all ports are
configured for
	dialout MWI, port 72 is the only one configured as _only_ MWI.
MWI got 
	out of sync last night due to Exchange maintenance, so this
morning we
	hit the resync button.
	
	So far, it's been running an hour, and it's still about 20
minutes
	behind "real time".
	
	What factors go into how long it takes Unity to perform a
resync?  Is
	there a list maintained by Unity that tells it which lights to
turn on
	and off, and it's just slowly making its way through the list?
If
	there's a list, then how can I find out where in the list it
currently is?
	
	Or is it hitting each mailbox, checking for new messages, and
then
	deciding which ones have new VM?
	
	In the past, it seems like Unity takes a long time and it only
uses port 
	72 rather than all ports.  Looking at port status monitor shows
that the
	server isn't super-busy; the highest utilized port I've seen has
been
	port #8.  CPU utilization is low.
	
	However, if we watch long enough, we'll see MWI dialout at about
one 
	every 5 seconds (for about an hour), and then all of a sudden
Unity will
	use 70 ports all at the same time, "catch up", and then it's
done.
	
	Why isn't is using all 50-60 ports right from the beginning? 
	
	
	_______________________________________________
	cisco-voip mailing list
	cisco-voip at puck.nether.net
	https://puck.nether.net/mailman/listinfo/cisco-voip
	




-- 
Ed Leatherman
Senior Voice Engineer
West Virginia University
Telecommunications and Network Operations 

--------------------------------------------------------
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 at dicksteinshapiro.com

Dickstein Shapiro LLP
http://www.DicksteinShapiro.com
==============================================================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20070322/be03e2ff/attachment.html