QUICK START GUIDE

PART 1 SETUP AND CONFIGURATION - Unified Communications Manager

Complete these 4 steps before you install the VistaPoint software (as seen in PART 2)
http://www.iqnetsolutions.com/html/cisco_install_help.html

This will prepare the VistaPoint ties needed for our application to do its job

CREATE TSP USER ACCOUNT

Create a user account for the VistaPoint Server to make use of.
We Recommendation USER ID be something like “VISTATSP” so it can be identified quickly. This account should not be associated with a primary extension number

Enable these switches on that account

Enable CTI Application Use (yes)
Call Park Retrieval Allowed (yes)
Device Association (all phones you wish to see and make use of)

Additional documentation
http://support.iqnsi.com/documents/pbx_cisco/configure_TSP/

Download and Install Cisco TSP

If you upgrade your Unified Communications Manager you will need to update\upgrade the Cisco TSP on the VistaPoint server as well, it needs to match what is running on the Unified Communications Manager always.

Download location example: http://ccm1/ccmadmin/install.asp (ccm1 is the Cisco Unified Communications Manager) The plug-in name is “Cisco Telephony Service Provider” Of course you will need to replace the value “ccm1” with the hostname or IP address of your own Unified Communications Manager.

Download and install the Cisco TSP from your own Unified Communications Manager, when it asks if you wish to install multiple instances of the TSP select “no”. Select “no” prompted to reboot
Configure the TSP by opening up the Phone and Modem options (located in the MS control panel) select the “advanced” tab and configure the “cisco_tsp.tsp”.
Reboot

VERIFICATION OF THE TSP

Open up MS Dialer (startmenu>run>dialer)
Select the menu item “edit>options>Line used for phone calls” this should list “all” your Cisco phones

PART 2 INSTALLING THE VISTAPOINT SERVER SOFTWARE

Configuring the VistaPoint software (you should have already complete PART 1)
http://www.iqnetsolutions.com/html/vp_server_install_ccm.html

VISTAPOINT SERVER (PC) - link

Required

No preexisting installation of SQL
Our database will be unable to register and the VistaPoint Notes service will fail |TT#
You can not install the server components under terminal services
Our database will be unable to register and the VistaPoint Notes service will fail |TT#

Decompress the contents of “Server.zip”
RUN “Setup.exe”
Select your components and click on “ok”

Checkmark the following

VISTAPOINT ENTERPRISE SERVER
This is by default the only check box that is enabled. VP: PCE, DATABASE and LICENSING services
CISCO SIM
This needs to be installed and configured to get call control functioning. Typically this gets installed on the VISTAPOINT ENTERPRISE SERVER but there are some configurations that may require this to be installed on a secondary machine. If the Cisco TSP is not installed the installer will notify you

OPTIONAL COMPONENTS

* One-Click Install (Requires IIS)
* Client Web Installations (Requires IIS)
If you installed the optional components you can configure the IQ web server in IIS.
The client installer path is http://localhost/iq/installs/index.htm
* VistaPoint Enterprise Directory (Requires IIS and site license)
* CstaAPI (LCS GATEWAY)
Install this to enable call control for COMMUNICATOR clients
* SIPSIM
Install this to integrate LCS and VISTAPOINT
Click here for configuration help after you have configured your VistaPoint Server

After the files have been installed and when the license dialogue displays fill out the information and enter in your Product Key if you do not have a product key leave these fields blank
Selecting “Internet Licensing” Instantly applies the license values to the machine
Alternatively Select “Email Licensing”
This will save a file you can then email to iqlicense@iqnsi.com.
Our license server will automatically send you a decryption key to un-lock the software so long as the product key is valid and has not already been used.
Selecting “Cancel” because you do not have a valid product key will Begins a 30 Day Evaluation of the software. It is important not to tamper with the system clock while running under a demo because doing so will invalidate your demo system until you purchase a software key
Additional Help
REBOOT WHEN PROMPTED
When logging in you will need to enter in a “Admin” and “Tenant Admin” password (these need to be unique, do not use the same password for each)
Install the VistaPoint Desktop companion OR Console (this will be used to verify the TAPI functionality of the CISCO SIM and will allow you to administer the system)
You do not need to install the .NET Framework (cancel this when prompted)
Launch the client application
Enter in your extension number
Enter in the IP Address or hostname of the VP Server (if the client is installed on the server this step will be skipped)

In The Running Client - You should only see parking and route point numbers until the CISCO SIM is configured

CONFIGURING THE SERVICES

CISCO SIM

Right Click on the CISCO SIM tray icon and open “Device Settings” under the Unified Communications Manager options and enter in an “Administration level” account username and password. Typically we just enter in “Administrator” and the password for that account.
Click on “Save and retrieve data”

In The Running Client - you should see all your phones a few moments later (it may take a couple minutes depending on how many devices are being monitored).

Right Click on the CISCO SIM tray icon and open “Directory Settings” under the Unified Communications Manager options. This is where you can identify your directory source (matches name and department information to extension numbers)

EXAMPLE (Unified Communications Manager Directory)

LDAP PORT = 8404
Naming Context = o=cisco.com
Full DN user = CN=Directory Manager,o=cisco.com
Note: All other field defaults are correct; just enter the p/w for the Directory Manager.

EXAMPLE (My own Active Directory)

LDAP PORT = 389
Naming Context = dc=iqnsi, dc=com
Full DN user = cn=Brian Buttner, ou=support, dc=iqnsi, dc=com
Object class for user search = users
Department attribute = department (if you wish to pull from a different field just match the correct attribute name)
Use an LDAP user phone instead of a cisco specific (Enabled) and my attribute = ipPhone
Note: This is where in active directory it looks for the Cisco extension number to match extension number to user
Click on “Save and retrieve data” you should see all your phones get populated with the First name, Last name and Department information a few moments later (it may take a couple minutes depending on how many devices are being monitored).

VERIFICATION OF THE CISCO SIM

You should now have full call control and feature sets should all be working.
All real time events should be showing up etc… as seen in one of our desktop clients (Desktop Companion or Console Companion).

You should now use your desktop application to create global groups and populate them with BLF cells (see documentation help F1 in you client)