<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=white lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>If they are non-contiguous I would setup
new partitions, and CSSes. It’s hard to believe in a multi site environment
you don’t have multiple CSSes. It would make life easier down the road.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Scott<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Lelio Fulgenzi<br>
<b><span style='font-weight:bold'>Sent:</span></b> Saturday, October 29, 2005
5:52 PM<br>
<b><span style='font-weight:bold'>To:</span></b> cisco-voip@puck.nether.net<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [cisco-voip] direct
to VM route RP & Unity Digital network</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>I see now. Well, just as you have to forward the phone
to the correct Unity server, you have to direct the *XXX calls to the correct
Unity server. If your extension range is unique, which I assume it is because
everyone is using the same partitions and calling search spaces, then you
can simply route specific patterns or ranges to the correct voicemail server.
So, *[0-4]XXX to one server and *[5-9]XXX to the other server. Now, if you have
non-contiguous ranges at each location, well, this gets a little more difficult
as you will begin to have one offs. You won't need any extra partitions or
calling search spaces, just let everyone dial the route points.</span></font><o:p></o:p></p>
</div>
<blockquote style='border:none;border-left:solid black 1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>
<div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>----- Original Message ----- <o:p></o:p></span></font></p>
</div>
<div style='font-color:black'>
<p class=MsoNormal style='background:#E4E4E4'><b><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial;font-weight:bold'>From:</span></font></b><font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'> <a
href="mailto:PRuttman@foley.com" title="PRuttman@foley.com">Ruttman, Peter G.</a>
<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><b><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial;font-weight:bold'>To:</span></font></b><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'> <a
href="mailto:cisco-voip@puck.nether.net" title="cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><b><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial;font-weight:bold'>Sent:</span></font></b><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'> Saturday, October
29, 2005 6:16 PM<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><b><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial;font-weight:bold'>Subject:</span></font></b><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'> RE: [cisco-voip]
direct to VM route RP & Unity Digital network<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>If you call the extensions everything works because I have the voice
mail profiles pointing to the proper pilot points for the proper unity
servers. The issue is with our requirement for the direct to VM route
point. A user can type * and the 7-digit phone number to and go directly
to voice mail which bypasses the ringing of the person's phone. The RP
has a voice mail profile associated with it and since we currently only are
using a single scheme for partitions and CSSs I have no way of addressing both
unity servers so I just point it to one of them. I was hoping that I
could convince the unity server that would get the calls to forward on any
calls for subscribers that are not in its local database to forward them on to
the other server via digital networking but it isn't working. I know that
portions of digital networking are working because you can go to the automated
attendant and dial the extension of a subscriber on the other unity server and
it will transfer ove!<br>
r to the other unity server. I can also server the global directory
on either server as well. Perhaps there is no way to do what I want without building
separating partitions and CSSs for each building so I can have two separate RPs
for the voicemail transfers but it is a lot of extra configuration for one
feature. Any thoughts?<br>
<br>
________________________________<br>
<br>
From: Lelio Fulgenzi [mailto:lelio@uoguelph.ca]<br>
Sent: Sat 10/29/2005 12:50 PM<br>
To: Ruttman, Peter G.; <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
Subject: Re: [cisco-voip] direct to VM route RP & Unity Digital network<br>
<br>
<br>
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.<br>
<br>
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.<br>
<br>
We have three Unity servers operating with one cluster and everything is
working fine, so it is possible.<br>
<br>
Let us know.<br>
<br>
Lelio<br>
<br>
----- Original Message ----- <br>
From: Ruttman, Peter G. <<a href="mailto:PRuttman@foley.com">mailto:PRuttman@foley.com</a>>
<br>
To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a> <br>
Sent: Saturday, October 29, 2005 10:40 AM<br>
Subject: [cisco-voip] direct to VM route RP & Unity Digital network<br>
<br>
Hi Folks,<br>
<br>
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!<br>
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?<br>
<br>
Pete<br>
<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>
<br>
<br>
<br>
________________________________<br>
<br>
<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">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br>
<br>
<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>
<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">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></span></font></p>
</blockquote>
</div>
</body>
</html>