<!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.2900.3562" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>It seems strange that Cisco would choose to use the
port usage as a trigger, rather than a heartbeat or something. Minimally, since
the backup system has SCCP ports, it could go into a "sanity check" mode as soon
as it receives a call on one of it's ports. Before it triggers failover, it
calls the ports on the primary system and sends some DTMF tones. If it gets the
correct reply, it stays in passive mode.</FONT></DIV>
<DIV> </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=msaskin@gmail.com href="mailto:msaskin@gmail.com">Matthew Saskin</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=erickbee@gmail.com
href="mailto:erickbee@gmail.com">Erick Bergquist</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</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> Wednesday, July 15, 2009 10:33
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [cisco-voip] Port 2 has
detected an incoming call. This systemis in inactive mode and is configured to
fail over in thiscondition. Fail over to this system will occur,and the call
will be answered.</DIV>
<DIV><BR></DIV>There are also a few defects out there (CSCsc62073 is a feature
request I believe) where even though all primary unity ports aren't busy if
they don't respond for any particular reason the call will hunt across all
entries in a line group and move on the next line group (secondary unity
server). If the call failures are caused by a condition such as location
out of bandwidth, and not by the unity server not answering, this could lead
to an unnecessary failover if bandwidth becomes available and the call is
allowed to route once the system is routing it through the secondary line
group. <BR><BR>"Fix" for this scenario is an adjustment to the "stop
routing on out of bandwidth flag" service parameter. Default is false,
setting it to true will "fix" this scenario.<BR><BR>As odd as it seems, I've
seen it affect quite a number of my customers.<BR><BR>-matt<BR><BR>
<DIV class=gmail_quote>On Tue, Jul 14, 2009 at 11:02 PM, Erick Bergquist <SPAN
dir=ltr><<A
href="mailto:erickbee@gmail.com">erickbee@gmail.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">You
need to put all your voicemail ports in a partition that no CSS<BR>has
access to, and just make sure the voicemail pilot # and associated<BR>hunt
pilot is in a partition phone DNs/etc have access to with another<BR>CSS.
There are no changes that need to be made in Unity.<BR><BR>I usually just
put the voicemail ports in a partition called<BR>VoicemailPorts (or
similar).<BR><BR>I recently did this on a 6.1.x system to fix this problem,
and when I<BR>went under the VM port setup to change the partition the Line
group<BR>updated itself so I didn't have to change the line groups
afterward<BR>either.<BR><BR>The only time one needs to dial a VM port DN
directly is for some<BR>advanced troubleshooting scenario and you can put a
CSS on a test<BR>phone to do that if that need ever comes up.<BR>
<DIV>
<DIV></DIV>
<DIV class=h5><BR><BR>On Tue, Jul 14, 2009 at 3:13 PM,
Miller,<BR>Steve<<A
href="mailto:MillerS@dicksteinshapiro.com">MillerS@dicksteinshapiro.com</A>>
wrote:<BR>> A call seems to have arrived at a time when it would be
impossible for the<BR>> Primary Unity system to be busy. How do I
prevent this call from hitting<BR>> the secondary and forcing a failover
as it did?<BR>><BR>><BR>> Steve Miller<BR>> Telecom
Engineer<BR>> Dickstein Shapiro LLP<BR>> 1825 Eye Street NW |
Washington, DC 20006<BR>> Tel (202) 420-3370| Fax (202) 330-5607<BR>>
<A
href="mailto:MillerS@dicksteinshapiro.com">MillerS@dicksteinshapiro.com</A><BR>><BR>><BR>><BR>>
--------------------------------------------------------<BR>> This e-mail
message and any attached files are confidential and are intended<BR>>
solely for the use of the addressee(s)<BR>> named above. This
communication may contain material protected by<BR>> attorney-client,
work product, or other<BR>> privileges. If you are not the intended
recipient or person responsible for<BR>> delivering this
confidential<BR>> communication to the intended recipient, you have
received this<BR>> communication in error, and any review, use,<BR>>
dissemination, forwarding, printing, copying, or other distribution of
this<BR>> e-mail message and any attached files<BR>> is strictly
prohibited. Dickstein Shapiro reserves the right to monitor any<BR>>
communication that is created,<BR>> received, or sent on its network.
If you have received this confidential<BR>> communication in error,
please notify the<BR>> sender immediately by reply e-mail message and
permanently delete the<BR>> original message.<BR>><BR>> To reply to
our email administrator directly, send an email to<BR>> <A
href="mailto:postmaster@dicksteinshapiro.com">postmaster@dicksteinshapiro.com</A><BR>><BR>>
Dickstein Shapiro LLP<BR>> <A href="http://www.DicksteinShapiro.com"
target=_blank>http://www.DicksteinShapiro.com</A><BR>><BR>>
==============================================================================<BR>><BR></DIV></DIV>>
_______________________________________________<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"
target=_blank>https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>><BR>><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"
target=_blank>https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR></BLOCKQUOTE></DIV><BR>
<P>
<HR>
<P></P>_______________________________________________<BR>cisco-voip mailing
list<BR>cisco-voip@puck.nether.net<BR>https://puck.nether.net/mailman/listinfo/cisco-voip<BR></BLOCKQUOTE></BODY></HTML>