VistaPoint Enterprise Installation Checklist for UCM Call Manager
Important Installation Note
To ensure proper operation of the VistaPoint Enterprise Software, verify that the following items are in place prior to starting the installation.
Support for multiple CiscoTSPs
In the Cisco TAPI solution, the TAPI application and the CiscoTSP get installed on the same machine. The Cisco TAPI application and the CiscoTSP do not directly interface with each other. A layer written by Microsoft sits between the TAPI application and the CiscoTSP. This layer, known as TAPISRV, allows the installation of multiple TSPs on the same machine, and it hides that fact from the Cisco TAPI application. The application communicates with TAPISRV, and TAPISRV takes care of communicating with the correct CiscoTSP.
Ensure that each CiscoTSP is configured with a different username and password that you administer in the Directory. Configure each user in the Directory so devices that are associated with each user do not overlap. Each CiscoTSP in the multiple CiscoTSP system does not communicate with each other. Each Cisco TSP in the multiple CiscoTSP system creates a separate CTI connection to the CTI Manager.
Note: Multiple CiscoTSPs help in scalability and higher performance.
Cisco Integration Checklist
Software Required
- UCM 5.0 or later (contact support@iqnsi.com if you wish to get software compatible with older UCM versions)
- Computer-telephony integration enabled for a TSP login account.
- For the TSP login account, devices must be enabled and associated with each of the lines you wish to monitor.
- Cisco TAPI Service Provider (TSP).
- You will need the following VistaPoint software;
- VistaPoint Cisco SIM license for each CCM or CCM Cluster. This SIM must be installed on the same computer running the CCM TSP.
- VistaPoint Server software (downloaded from FTP server)
- VistaPoint Client software (downloaded from FTP server)
- NOTE: If you have different versions of the Cisco TSP in your enterprise, you will need a separate SIM and computer for each.
Hardware Required – Customer Provided
- Cisco MCS (Media Convergence Server) to run .
- Dedicated Server PC, to run VistaPoint Enterprise Server Components, Cisco TSP and up to three VistaPoint Cisco SIMs. One Cisco SIM can support one and/or Cluster). Add one additional Cisco SIM for each additional and/or Cluster.
Notes on Cisco Integration
VistaPoint Enterprise is fully integrated with the UCM to provide third-party call control and presence. However, there are a few limitations / nuances that exist in the CCM TSP that limit VistaPoint Enterprise capabilities. They are listed here:
- Shared Lines - The Cisco TSP with Cisco 3.3(3) software does not support shared lines. Shared lines are supported with UCM 4.0 or higher.
- Soft phones - The Cisco TSP does not support the ability to monitor soft phones until CCM 4.1(2).
- UPDATE: The IP Communicator softphone (SCCP based) can be fully controlled via TAPI, just like any other SCCP based phone. The Cisco Softphone (TAPI
based) can be controlled via the Cisco TSP beginning with CCM 4.1(2), by using the 'CTI Port Third Party Monitoring' feature functionality. iQ NetSolutions is in the process of verifying Soft Phone functionality at this time.
- Load Limitations - There are load-related limitations, including restrictions on how many TAPI monitors are supported by your UCM. Consult with your Cisco documentation for more information.
- Partitions – UCM 4.0+ TAPI implementation does not support multiple instances of the same DN (with different partitions). See Service Bulletin CSB060223001.
- CCM 4.X: When using integrated MLA authentication and not the default Windows authentication please insure the user account used in the CiscoSIM device configuration is a Super User within the CCM system.
Additional Limitations
- The Cisco TSP does not provide information for the second appearance of a single DN on an IP phone prior to v4.0 of CM. So the second appearance of a DN on a phone (in a second partition) will not show any call activity.
- If you are using Extension Mobility, either disable the “Multiple Logins Allowed” option, or notify users that logging into more than one phone simultaneously will prevent VistaPoint Enterprise from working properly with their phone.
Cisco Devices Supported
The following devices are supported by the Cisco TSP ver 4.2(1)
- 30 SP+ (This device has spurious offhook problems, not recommended.)
- 12 SP+ (This device has spurious offhook problems, not recommended.)
- 12 SP (This device has spurious offhook problems, not recommended.)
- 7902
- 7905
- 7910
- 7911
- 7912
- 7914
- 7920
- 7935
- 7936
- 7940
- 7941
- 7960
- 7961
- 7970
- 7971
- CTI Route Points
- CTI Ports
- VG248 Analog Devices
- ATA186 Analog Devices
Note: on Cisco Unified Communications Manager 6.x
7931 is special phone model which has programmable line keys and hardware based hold, redial & transfer buttons. This is conditionally supported in the latest release of Cisco TSP, which means only monitoring / controlling the 7931 phone is available when the device is configured as non-rollover mode.
CiscoTSP will not support 7931 configured with rollover mode enabled
http://support.iqnsi.com/documents/pbx_cisco/7931_phone_configuration/
In a Nutshell...
In a nutshell this is what we require in its entirety
- Services enabled on the UCM (specifically AXL and Soap services in addition to the callmanager core service)
- TSP Application user account in the UCM
- All presence switches enabled for that user (we only really need subscription and notification switches)
- The user is a part of the CTI user groups (I will just put the user in all the CTI groups)
- The user is a member of the standard super users group (I do this so that I can use this same account for device configuration in the SIM)
- The user is given control of all the phones wished to be see and control in our product
- The phones are all configured and a part of a common CSS
- The users are associated to the monitored phones and Firstname, Lastname, Department and DN is present
- The TSP is loaded on the VP server and is verified as functioning (you see your phone “SEP” devices in msdialer)
- The SIM is configured under device settings correct IP address to the UCM, port, user and password
- The SIM is configured under directory settings to use AXL (single check box)
- This checkbox requires\assumes the information exists for the users\phone (item 8) and publishes anything that matches the DN
 |
View\Print this page
click to continue: Cisco-Part1
|