This may be a very stupid question but I am trying to install Unity 2.45 in an IP Integration, but I am having trouble finding the multi-media drivers. I was supposed to install the CiscoTSP.exe from Disk 1 of CM, but it was not on there, so I installed AVCiscoTsp.exe from Disk 1 of Unity. It installs fine, but does not create a directory of C:\ProgramFiles\Cisco\WaveDrivers as the install book requires for installation of the media drivers on page 20 of the integration guide. Does anyone know where they are located? Thanks in advance....Jamie<br><br>
If you're using the AVCiscoTSP to connect to your call manager, you should be fine... no need to check for that directory. You just need to make sure the TSP is setup correctly.
The TSP from the CM disks is a different TAPI driver, you should really be using the AvCiscoTSP on our CD which uses the Skinny protocol to talk with CM... much lighter and more functional.
Just in case you don't have updated docs handy, here's a cut/past (badly formatted) from the Acrobat doc for the CM configuration section for Unity:
Perform the following procedures in the order given. If you are upgrading from Cisco CallManager version 2.4 to 3.0, you must remove the old TAPI service provider before you install the new one. See Upgrading from Cisco 2.4 to Cisco 3.0, on page 19.
To install the AV-Cisco TAPI service provider and wave driver NOTE: Unity 2.4.5 or later must be installed before you install the AV-Cisco TAPI service provider and wave driver. a On the Unity server, shut down Unity. b Insert Unity Disc 1 into the CD-ROM drive on the Unity server. c Browse to the Cisco directory. d Run Setup.exe. e Follow the on-screen instructions. f When you are prompted to restart the server, remove the Unity disc from the CD-ROM drive, and restart the server. g Continue with the next procedure.
To configure the AV-Cisco TAPI service provider a Log on to Windows NT/2000, and the AV-Cisco TAPI Service Provider dialog box appears. NOTE: The AV-Cisco TAPI Service Provider dialog box only appears automatically the first time you log on after installing the AV-Cisco TAPI service provider and wave driver. To change settings later, see Changing AV-Cisco TAPI service provider settings, on page 16. b Click Add, and the Add CallManager IP Address dialog box appears. c Type the IP address of the Cisco CallManager server that is connected to Unity, and click OK. d In the AV-Cisco TAPI Service Provider Settings dialog box, enter values as shown in the following table. e Click OK to close the AV-Cisco TAPI Service Provider Set-tings dialog box. f Continue with the next procedure. Field Value Primary CallManager IP address The IP address of the Cisco CallManager server that Unity will usually receive calls from. Number of voice ports The number of Cisco CallManager uOne ports that are connected to Unity. Device name prefix The prefix that you used for Device name when you created uOne ports in Cisco CallManager Administration. See To add uOne ports to Cisco CallManager, on page 6. MessageWaitingOnDN The extension that you specified, in Cisco CallManager Administra-tion, for turning MWIs on. See To specify MWI and voice-mail exten-sions, on page 7. MessageWaitingOffDN The extension that you specified, in Cisco CallManager Administration, for turning MWIs off. See To specify MWI and voice-mail extensions, on page 7. CallManager failover IP addresses The IP addresses of backup Cisco CallManager servers, if any. Backup CallManager servers must be in the same cluster as the primary CallManager server. CallManager device list A display-only list of the names of the uOne ports that Unity looks for on the current Cisco CallManager server. This list is constructed by appending numbers starting with 1 to the value of Device name prefix. CAUTION: If the names in this list do not exactly match the names of the uOne ports in Cisco CallManager Administration, calls will not be cor-rectly transferred to Unity..CHAPTER 1: Cisco CallManager integration 11
To test the AV-Cisco TAPI service provider a If the AV-Cisco TAPI Service Provider dialog box is already displayed, skip to step g . Otherwise, continue with step b . b On the Unity server, log on to Windows NT/2000 as an administrator. c Click Start > Settings > Control Panel. d In Windows NT, double-click Telephony. The Dialing Prop-erties dialog box appears. or In Windows 2000, double-click Phone and Modem Options. The Phone and Modem Options dialog box appears. e In Windows NT, click the Telephony Drivers tab. or In Windows 2000, click the Advanced tab. f Click AV-Cisco TAPI Service Provider, and click Config-ure. The AV-Cisco TAPI Service Provider dialog box appears. g Click Test, and the settings you specified in step d of the procedure To configure the AV-Cisco TAPI service provider, on page 10 are checked against the current settings in Cisco CallManager Administration. If the test succeeds, a message box displays the message The test completed successfully. If the test fails, one of the error messages shown in the following table appears. Trou-bleshoot the problem as described in the Comments col-umn, and repeat this step until the test succeeds. Then continue with step h . h Click OK to close the AV-Cisco TAPI Service Provider dialog box. The following message appears: This computer needs to be rebooted to update the wave driver. i Click OK. j In Windows NT, click Close to close the Dialing Properties dialog box. or In Windows 2000, click Close to close the Phone and Modem Options dialog box. k Shut down and restart the Unity server. Error message Comments Pinging CallManager server () 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 you specified in Primary CallManager IP address. Confirm that this address is valid. If the value is correct, or if the problem persists after you change the value, troubleshoot the prob- lem as you would a network connectivity problem. The voice device named does not respond to registration requests. Ensure that the device has been created in the CallManager database and that the device name prefix is correct. Confirm that the values in CallManager Device List (see step d of the procedure To configure the AV-Cisco TAPI ser- vice provider, on page 10) match the names of the uOne ports that you created (see To add uOne ports to Cisco Call- Manager, on page 6). If not, change Device name prefix or the names of the uOne ports, as necessary. Could not connect to the CallManager. Verify that all Cisco services are started on the Call- Manager server. The IP address that you specified in Primary CallManager IP address is a valid address, but Cisco CallManager services are not running on that computer, possibly because CallMa- nager is not installed on the server with that IP address. Confirm that this address is correct and that the CallManager services are running.. To confirm that the integration is enabled a On the Unity server, start Unity. b In Internet Explorer, go to the Unity Administrator (http:///saweb). c Go to System > Licensing > Licensed Features. d In the Integration box, confirm that the setting is TAPI. If the setting is any other value, contact your sales representative. e Go to System > Switch. Confirm that the settings match those in the following table. If the settings are incorrect, integration features may not be enabled. f Close the Unity Administrator. g Shut down and restart the Unity server. Switch settings Switch parameter Required settings Manufacturer Cisco Model CallManager Switch PBX software version 3.01 or later Integration TAPI
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...