UNIVERGE UM8500 I
NTEGRATION
G
UIDE
38
To test the TAPI service provider
1
If the Cisco Unity-CM TSP dialog box is already displayed, skip to step
Otherwise, continue with step 2.
2
On the messaging system server, log on to Windows as an administrator.
3
On the Windows taskbar, click
Start
>
Control Panel
.
4
Double-click
Phone and Modem Options
. The Phone and Modem
Options dialog box appears.
5
Click the
Advanced
tab.
6
Click
Cisco Unity-CM TSP
, and click
Configure
. The Cisco Unity-CM TSP
dialog box appears.
7
Click
Test
, and the settings specified in step
” on page 37 are checked against the current settings
in Cisco CallManager Administrator.
If the test succeeds, a message box displays the message “Test completed
successfully.” If the test fails, one of the error messages shown in the following
table appears. Troubleshoot the problems as described in the “Comments”
column, then repeat this step until the test is successful. Continue with step
.
8
Click
OK
to close the Cisco Unity-CM TSP dialog box. The following message
appears:
This computer needs to be rebooted to update the wave driver.
9
Click
OK
.
10
click
Close
to close the Phone and Modem Options dialog box.
11
Shut down and restart the messaging system server.
Error message
Comments
Pinging CallManager server
<IP address> failed. Make sure
the IP address is valid, the server
is running, and the network
connection is working.
No computers on the network have the IP address that specified in
“Primary CallManager IP address.” Confirm that this address is valid. If
the value is correct, or if the problem persists after the value is changed,
troubleshoot the problem as a network connectivity problem.
The voice device named <device
name> does not respond to
registration requests. Ensure that
the device is created in the
CallManager database and that the
device name prefix is correct.
Confirm that the values in
CallManager Device List
of the
To configure the TAPI service provider
” on page 37, matches
the names of the uOne or voice mail ports created, see “
ports to CallManager version 3.05
to CallManager version 3.2 and later
” on page 34. If not, change the
Device name prefix
of the names of the ports, as necessary.
Could not connect to the
CallManager. Verify that all Cisco
services are started on the
CallManager server.
The IP address specified in
Primary CallManager IP address
is a
valid address, but CallManager services are not running on that computer,
possibly because CallManager is not installed on the server with that IP
address. Confirm that this address is correct and that the CallManager
services are running.
Summary of Contents for UNIVERGE UM8500
Page 1: ......
Page 28: ...UNIVERGE UM8500 INTEGRATION GUIDE 18 ...
Page 62: ...UNIVERGE UM8500 INTEGRATION GUIDE 52 ...
Page 68: ...UNIVERGE UM8500 INTEGRATION GUIDE 58 ...
Page 94: ...UNIVERGE UM8500 INTEGRATION GUIDE 84 ...
Page 104: ...UNIVERGE UM8500 INTEGRATION GUIDE 94 ...
Page 114: ...UNIVERGE UM8500 INTEGRATION GUIDE 104 ...
Page 120: ...UNIVERGE UM8500 INTEGRATION GUIDE 110 ...
Page 126: ...UNIVERGE UM8500 INTEGRATION GUIDE 116 ...
Page 146: ...UNIVERGE UM8500 INTEGRATION GUIDE 136 ...
Page 164: ...UNIVERGE UM8500 INTEGRATION GUIDE 154 For a SPADLIC A trunk board ...
Page 172: ...UNIVERGE UM8500 INTEGRATION GUIDE 162 ...
Page 188: ...UNIVERGE UM8500 INTEGRATION GUIDE 178 ...
Page 193: ...NEC NEAX 2400 OR NEC SV7000 WITH LAN MCI 183 For a SPADLIC A trunk board ...
Page 222: ...UNIVERGE UM8500 INTEGRATION GUIDE 212 ...
Page 230: ...UNIVERGE UM8500 INTEGRATION GUIDE 220 ...
Page 276: ...UNIVERGE UM8500 INTEGRATION GUIDE 266 ...
Page 290: ...UNIVERGE UM8500 INTEGRATION GUIDE 280 ...
Page 302: ...UNIVERGE UM8500 INTEGRATION GUIDE 292 ...
Page 312: ...UNIVERGE UM8500 INTEGRATION GUIDE 302 ...
Page 336: ...UNIVERGE UM8500 INTEGRATION GUIDE 326 ...
Page 342: ...UNIVERGE UM8500 INTEGRATION GUIDE 332 ...