Cisco Systems Active Voice Repartee Unity R2 4 Installation Guide

							CHAPTER 4: Setting up the integration93
eIn the navigation bar, click “Call transfer” to go to 
Subscribers > Subscribers > Call Transfer for Example 
Subscriber.
fConfirm that incoming calls are set to transfer to Example 
Subscriber’s extension.
gSelect a transfer type. If the phone system does not forward 
calls to the subscriber’s greeting, use “Supervise transfer.” 
hSelect the number of rings to wait before Unity recalls a call.
iIf you made a change, click the Save icon.
Continued
f
g
h
i 
						

							UNITY INSTALLATION GUIDE94
Testing the 
Continued
integration
To test the voice messaging ports
aFrom a test extension, call each port. Refer to the System > 
Ports page for the extension of each port, if necessary. Con-
firm that each port answers.
bPress a touchtone key as a Unity conversation prompt plays. 
The prompt should stop. If it does not, see “Unity does not 
respond to touchtones,” in Chapter 3 of the Unity T rouble-
shooting Guide.
To test release transfers
If you are not using release transfers, skip this test.
aDisconnect a line from Unity and connect it to a test phone 
(Phone 1). This may require a line splitter or a breakout box. 
For information on setting up the test, see “Troubleshooting 
preparation,” in Chapter 1 of the Unity T roubleshooting 
Guide.
bFrom an extension that is connected to the phone system 
but that will not be connected to Unity (Phone 2), dial the 
access code necessary to get an outside line, then call 
Phone 1.
cAnswer Phone 1.
dOn Phone 1, flash the hookswitch, or press the “Flash” 
button.
eOn Phone 1, dial a third extension, (Phone 3). If the phone 
system requires an override digit to force ringing, dial it.
fHang up Phone 1.
gAnswer Phone 3.
If the transfer succeeds (if Phone 2 is connected to Phone 3), 
release transfers work. Reconnect lines to the Unity server.
If the transfer fails, see “Release transfers are not being per-
formed correctly,” in Chapter 3 of the Unity Troubleshooting 
Guide. 
						

							CHAPTER 4: Setting up the integration95
To test supervised transfers
If you are not using supervised transfers, skip this test.
aDisconnect a line from Unity and connect it to a test phone 
(Phone 1). This may require a line splitter or a breakout box. 
For information on setting up the test, see “Troubleshooting 
preparation,” in Chapter 1 of the Unity T roubleshooting 
Guide.
bFrom an extension that is connected to the phone system 
but that will not be connected to Unity (Phone 2), dial the 
access code necessary to get an outside line, then call 
Phone 1.
cAnswer Phone 1.
dOn Phone 1, flash the hookswitch, or press the “Flash” 
button.
eOn Phone 1, dial a third extension, (Phone 3). If the phone 
system requires an override digit to force ringing, dial it.
fIf you hear the ringback tone, answer Phone 3 and hang up 
Phone 1.
If the transfer succeeds (if Phone 2 is connected to Phone 3), 
supervised transfers work. Reconnect lines to the Unity 
server.
If the transfer fails, see “Supervised transfers are not being 
performed correctly,” in Chapter 3 of the Unity Troubleshoot-
ing Guide.
To test external number access
Dial an external number from the test extension. You 
should reach the number. If you do not, the problem is with 
the phone system.
Continued 
						

							UNITY INSTALLATION GUIDE96
Testing the 
Continued
integration
To view port status
In the final four test procedures, use the Status Monitor to deter-
mine whether Unity’s ports are handling calls correctly.
NOTE:The Status Monitor requires Internet Explorer version 5 or 
later.
aOn the Unity server, double-click the desktop shortcut to 
the Status Monitor.
bClick the Port Status icon. 
b 
						

							CHAPTER 4: Setting up the integration97
To test whether Unity detects hangups
aCall Unity from an external line. You should hear the open-
ing greeting and see in the Status Monitor that Unity is 
answering with the opening greeting.
bHang up. The call should disappear from the Status 
Monitor. 
If the call does not disappear, and if the Unity server con-
tains Dialogic voice boards, run the Learn Tones utility and 
select the CO disconnect option. For information, see “The 
Learn Tones utility,” in Chapter 9 of the Unity Troubleshoot-
ing Guide.
cCall Unity again, this time from an internal line. You should 
hear the opening greeting and see in the Status Monitor that 
Unity is answering with the opening greeting.
dHang up. The call should disappear from the Status 
Monitor. 
If the call does not disappear, and if the Unity server contains 
Dialogic voice boards, run the Learn Tones utility and select the 
dial tone option. For information, see “The Learn Tones utility,” 
in Chapter 9 of the Unity Troubleshooting Guide.
To test call forward to personal greeting and message 
waiting indication
aCall Unity from an external line. You should hear the open-
ing greeting and see in the Status Monitor that Unity is 
answering with the opening greeting.
bWhen the automated attendant asks for an extension, enter 
the extension for Example Subscriber. The Status Monitor 
should indicate that the call is being transferred, and the 
phone should ring. Do not answer it.
cListen for the prerecorded Example Subscriber greeting.
dLeave a message that is at least 5 seconds long.
eConfirm that the message waiting indicator (MWI) on the 
phone assigned to Example Subscriber is on.
If the MWI is not on, see Chapter 5 of the Unity T rouble-
shooting Guide.
Continued 
						

							UNITY INSTALLATION GUIDE98
Testing the 
Continued
integration
fRetrieve the message and confirm that the message waiting 
indicator is off.
If the MWI is not off, see Chapter 5 of the Unity T rouble-
shooting Guide.
To test the hunt group
aBusy the first voice messaging port.
bFrom an external line, call the test extension. The first avail-
able port should take the call.
cBusy the next port, and repeat stepb.
dRepeat stepc until all the ports have been busied. When all 
the ports are busied, the phone system should do whatever 
you programmed it to do when all lines are busy. If some-
thing else happens, check the phone system programming.
To test identified subscriber messaging
Call the test extension from another extension. The Status 
Monitor should identify the extension from which you are 
calling. 
If the extension is not identified, either the phone system 
does not support identified subscriber messaging or there is 
a problem with the phone system.
Next section
TURNKEY SYSTEM
All configurationsWhat’s next, page 113
COMPONENT SYSTEM
All configurationsWhat’s next, page 113 
						

							
CHAPTER 5
Upgrading hardware 
and software5
In this chapter...
Upgrading a Unity or ActiveFax server ................................................................ 100
Adding or removing languages.............................................................................. 111
System key upgrades.................................................................................................. 112 
						

							UNITY INSTALLATION GUIDE100
Upgrading a 
Unity or 
ActiveFax 
serverThis section contains procedures that you do if you are:
Upgrading Unity and ActiveFax software on the Unity server 
from version 2.3 to version 2.4
Moving ActiveFax from the Unity server to a separate fax 
server.
Adding or changing voice boards in the Unity server.
Adding or changing fax boards in the Unity or ActiveFax 
server.
Do the procedures that apply to your situation, and do them in 
the order listed.
Included in this section are procedures to remove different 
brands of voice board software. Do the procedure(s) that apply to 
your voice board brand(s).
CAUTION:You must uninstall voice board software before you 
upgrade to Unity 2.4, or the upgrade will fail.
If you only want to add or remove languages after you have 
upgraded to Unity version 2.4, see “Adding or removing lan-
guages,” on page 111.
Backing up the Unity server
Back up the Unity server in case the upgrade process fails and 
you need to restore the Unity server to its original state. Use 
whatever process you normally use to back up the entire con-
tents of the Unity server.
Removing Dialogic voice board software
Do the following two procedures if the Unity server contains Dia-
logic voice boards, and if you are:
Upgrading Unity software to version 2.4.
Adding or changing voice boards, even if you are adding 
boards of the same type.  
						

							CHAPTER 5: Upgrading hardware and software101
To determine the current setting for the Dialogic quiet 
parameter
When the Dialogic quiet parameter has been set to a value other 
than the default, the setting will be lost when you remove the 
Dialogic software. Write down the current value of the quiet 
parameter so you can restore that value after you reinstall the 
software.
aShut down Unity if it is running.
bOn the Windows Start menu, click Programs > Dialogic Sys-
tem Software > Dialogic Configuration Manager to start the 
DCM. 
The tree-structured list contains an entry for each Dialogic 
board installed in the server.
cOn the Service menu, click “Stop service.”
dDouble-click any voice board in the tree list. The Properties 
dialog box for the board appears.
eClick the Misc tab.
fUnder “Parameter,” note and write down the value of 
“ParameterFile.”
gClick “OK.”
To remove Dialogic software
aShut down Unity if it is running.
bOn the Windows Start menu, click Programs > Dialogic Sys-
tem Software > Dialogic Configuration Manager–DCM.
cOn the Service menu, click “Stop service.”
dClose the DCM.
eOn the Windows Start menu, click Settings > Control Panel.
fDouble-click “Telephony.” The Dialing Properties dialog box 
appears.
gClick the Telephony Drivers tab.
Continued 
						

							UNITY INSTALLATION GUIDE102
Upgrading a Unity or 
Continued
ActiveFax server
hClick “Dialogic generation 2 service provider for NT.”
If you are using D/160SC voice boards and VoiceBridge 
2000 feature-set boards, this option will say “DSE Service 
provider.”
iClick “Remove.”
jClick “Close” to close the Dialing Properties dialog box.
kIn Control Panel, double-click “Multimedia.” The Multimedia 
Properties dialog box appears.
lClick the Devices tab.
mExpand “Audio devices.”
nClick “Audio for Dialogic WAVE Driver 1.x” or “Audio for 
dlgwave.dll.”
oClick “Remove.”
pWhen prompted to restart, click “Don’t restart now.”
qClick “OK” to close the Multimedia Properties dialog box.
rClose Control Panel.
sOn the Windows Start menu, click Programs > Dialogic Sys-
tem Software > Uninstall.
tFollow the on-screen instructions for the Dialogic software 
uninstall.
uWhen the dialog box asks whether you want to delete shared 
files, click “No to all.”
vIf you are using D/160SC voice boards and VoiceBridge 
2000 feature-set boards, at the end of the uninstall, do not 
restart. Instead, skip to the next procedure, “To remove 
Voice Technologies Group software.”
Otherwise, click “Reboot.” (The Dialogic-triggered restart 
may not restart the system; in this case, manually restart.)
wAfter restarting, log on.
xWith Windows Explorer, browse to the directory where Unity 
is installed (C:\CommServer by default) and delete the 
TSPSetup directory.
NOTE:If you have already upgraded to Unity version 2.4, 
this directory does not exist.