<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1505" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><SPAN class=315544313-28072005><FONT face=Arial color=#0000ff size=2>to go
to an alternate destination when the voicemail port is unregistered use the 'not
available' option in the hunt list/line group configuration.</FONT></SPAN></DIV>
<DIV><SPAN class=315544313-28072005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=315544313-28072005><FONT face=Arial color=#0000ff
size=2>/Wes</FONT></SPAN></DIV>
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B>
cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net]<B>On Behalf Of </B>Lelio
Fulgenzi<BR><B>Sent:</B> Thursday, July 28, 2005 9:21 AM<BR><B>To:</B>
cisco-voip@puck.nether.net<BR><B>Subject:</B> Re: [cisco-voip] CCM behavior on
downed VM ports<BR><BR></FONT></DIV>
<DIV>we see similar mwi out of sync issues on maintenance, and we too issue an
mwi resync, however, ours takes no more than 15 minutes to begin after i press
the button and no more than 15 minutes to complete. we have about 2500
subscribers.</DIV>
<DIV> </DIV>
<DIV>on your other question, we have our vm ports to ring n/a to a backup
message saying voicemail is unavailable on an old CRS box. i'm not aware of a
way to not forward to voicemail when voicemail is down.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>--------------------------------------------------------------------------------<BR>Lelio
Fulgenzi, B.A.<BR>Network Analyst (CCS) * University of Guelph * Guelph, Ontario
N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<BR>"I had a coffee and Coke at lunch today...and now, I've got more jitter than
an<BR>IP phone on a long haul 10base2
connection"
LFJ</DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=BillS@tns.its.psu.edu href="mailto:BillS@tns.its.psu.edu">Simon,
Bill</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=cisco-voip@puck.nether.net
href="mailto:'cisco-voip@puck.nether.net'">'cisco-voip@puck.nether.net'</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Thursday, July 28, 2005 9:10
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> RE: [cisco-voip] CCM behavior on
downed VM ports</DIV>
<DIV><BR></DIV>Just to clarify, I'm talking about Unity 4.0(3) integrated with
CallManager<BR>4.0(2).<BR><BR>-----Original Message-----<BR>From: Simon, Bill
[mailto:BillS@tns.its.psu.edu] <BR>Sent: Thursday, July 28, 2005 9:08
AM<BR>To: <A
href="mailto:'cisco-voip@puck.nether.net'">'cisco-voip@puck.nether.net'</A><BR>Subject:
[cisco-voip] CCM behavior on downed VM ports<BR><BR>Two unrelated
questions:<BR><BR>1. Is there a way to modify the behavior of
call-forwarding to voicemail<BR>when the voicemail ports are
unregistered? For example, this morning I was<BR>performing some
maintenance on Unity and during that time, the VM ports
were<BR>unregistered. Callers forwarded to voicemail on no-answer were
greeted with<BR>a reorder tone. I'd rather that, if the VM ports are
unregistered, no<BR>attempt is made to forward them there -- just let it
continue ringing the<BR>phone. Possible?<BR><BR>2. Roughly 3 out
of 4 times that we do maintenance on Unity requiring a<BR>reboot, once the
system comes back up, there is some problem with<BR>message-waiting indicators
being out of sync. This morning as I tested a<BR>mailbox I noticed the
problem again. The only way we've been able to clear<BR>this issue is by
going into the telephony integration manager and forcing a<BR>MWI
resync. However, this takes an unbearably long time with our system
of<BR>about 5000 subscribers. Has anyone else experienced these sorts of
MWI<BR>issues? Is there any way to make the resync go faster?
(Currently I just<BR>enable as many ports as possible to do MWI Dialout but
the process still<BR>takes upward of 1.5 hours -- during which time no MWIs
are issued on new<BR>messages or turned off when messages are checked, and
subscribers call in to<BR>report
trouble)<BR><BR><BR>Thanks<BR>Bill<BR>_______________________________________________<BR>cisco-voip
mailing list<BR><A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><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><A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR></BLOCKQUOTE></BODY></HTML>