<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1522" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Can you explain your problem a little more? Do you
mean when you call the extension and then it is forwarded to voicemail that you
get the opening greeting? If you haven't already, you should be forwarding each
phone to the individual Unity server on which the voicemailbox exists. So you
will have to two voicemail pilots in this case.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>It is possible to have the same voicemail pilot
pointing to two different Unity servers, but then you would need different
partitions and calling search spaces. Also, if one client were ever to visit the
other site, you would need a seperate pilot to access their voicemail box on the
other Unity.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>We have three Unity servers operating with one
cluster and everything is working fine, so it is possible.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Let us know.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Lelio</FONT></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=PRuttman@foley.com href="mailto:PRuttman@foley.com">Ruttman, Peter
G.</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> Saturday, October 29, 2005 10:40
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> [cisco-voip] direct to VM route
RP & Unity Digital network</DIV>
<DIV><BR></DIV>
<DIV><FONT face=Arial size=2><SPAN class=185493014-29102005>Hi
Folks,</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=185493014-29102005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=185493014-29102005>We are putting in
a new remote office that has two building that are connected by T1s. We
have exchange at both locations so we felt we better but Unity in both
locations as well. For Callmanager we have a centralized model that runs
out of our datacenters so we were going to treat these two building as if they
were the same for things like partitions, CSS, device pools, etc. We
have run into one snag now with unity. We have enabled digital
networking and from the primary unity server in the larger office you can dial
the number of subscribers on the other unity server as well as look them up in
the directory. The problem is that we have a route point in the form of
*[office 3 digit code]XXXX. So for this office it would be
*102xxxx. Since we only have one set of partitions and CSSs we can only
point this route point to one of the two unity servers so I pointed it to the
primary one out there (the larger building). When you type the
pattern in a phone it goes to the primary unity server. If the
subscriber is actually on the primary unity then you get the subscriber's
unity greeting. If the subscriber is on the other unity server you get
the main greeting. Of course, you can type the number again and it will
go to the other server but that isn't what we are looking for. Does
anyone have any suggestions other then setting up additional partitions and
CSSs to fix this problem for us?</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=185493014-29102005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN
class=185493014-29102005>Pete</SPAN></FONT></DIV><BR>The preceding email
message may be confidential or protected by the attorney-client privilege. It
is not intended for transmission to, or receipt by, any unauthorized persons.
If you have received this message in error, please (i) do not read it, (ii)
reply to the sender that you received the message in error, and (iii) erase or
destroy the message. Legal advice contained in the preceding message is solely
for the benefit of the Foley & Lardner LLP client(s) represented by the
Firm in the particular matter that is the subject of this message, and may not
be relied upon by any other party. <BR><BR><BR>Internal Revenue Service
regulations require that certain types of written advice include a disclaimer.
To the extent the preceding message contains advice relating to a Federal tax
issue, unless expressly stated otherwise the advice is not intended or written
to be used, and it cannot be used by the recipient or any other taxpayer, for
the purpose of avoiding Federal tax penalties, and was not written to support
the promotion or marketing of any transaction or matter discussed herein.<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>