<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2800.1522" name=GENERATOR></HEAD>
<BODY>
<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></BODY></HTML>