<!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.1479" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>Unfortunately, Unity operates with an explicit transfer
configuration. It will only transfer to DNs that it knows about, either a
mailbox or a call handler or an internet subscriber. To transfer to any number,
you would need to create one of the above for <EM>each</EM> number possible. We
elected to go with Internet subscribers since mailboxes take up a licence and
you can not search by name on a call handler.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Now, that being said, Unity now does offer a system transfer
application which will allow you to select any number to transfer to, however,
it's not searched by default. You have to send a caller to this application
first - not likely to work well.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>The other option you might want to consider is using the
CallManager autoattendant script. By doing so, you get all the features of any
route patterns in your dial plan to be accessible. Also, external calls will
ring as external (double-ring) since they are no longer transferred as internal
calls by Unity.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>With v4.1 you have internal/external forwarding rules which I
have not tested with Unity AA, but I suspect do not work.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Depending on time committments and product stability, I may
spend some time re-evaluating using Cisco rather than Unity AA.</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=Scott.Voll@wesd.org href="mailto:Scott.Voll@wesd.org">Voll, Scott</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> Wednesday, February 02, 2005 12:09
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> [cisco-voip] Auto
Attendant</DIV>
<DIV><BR></DIV>I need help finding a solution.<BR><BR>I have CM 3.3.4sr2,
Unity 4.0.4 and CRS 3.1.3sr3 and will be upgrading<BR>to CM 4.1.2 and CRS
3.5.2. I currently am integrated with AD 2003. I<BR>also have a
legacy PBX connected to my VoIP network. I have ~150 users<BR>on CM and
Unity and ~400 users on a PBX and it's Vmail system. <BR><BR>What can I
use to give me a fully functional Auto Attendant? I can't<BR>use the old
Vmail system as ~150 users are not on it. I can't use Unity<BR>because
~400 users are not on it. I opened a TAC case to get the AA<BR>script in
CRS to work and now it works but only works if the user has a<BR>device (ip
Phone) associated with them.<BR><BR>I don't understand why I can't get
something to work. That's how<BR>Attendant console works. It looks
at the Active Directory Phone number<BR>and transfers whether its on CM or
PBX.<BR><BR>Anyone have any
ideas?<BR><BR>TIA<BR><BR>Scott<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></BLOCKQUOTE></BODY></HTML>