SETUP AND CONFIGURATION - CALLMANAGER
TSP USER ACCOUNT
This is the account we
use to proxy all phone activity through.
Recommendation:
The account should not
be associated with a primary extension number
Required:
Additional
documentation
http://support.iqnsi.com/documents/pbx_cisco/configure_TSP/
PREPAIRING FOR THE VISTAPOINT SERVER INSTALL - CISCO
Required:
o No
pre-existing installation of SQL
Our database will be unable to register
and the VistaPoint Notes service will fail |TT#
o 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#
CISCO TSP
If you upgrade your
Call 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 Call Manager always.
Download location example: http://ccm1/ccmadmin/install.asp (ccm1 is the Cisco Call 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 Call Manager.
VERIFICATION OF THE
TSP
INSTALLING THE VISTAPOINT SERVER SOFTWARE
Decompress the contents of “Server.zip”
1. RUN “Setup.exe”
Checkmark the following
ü
VISTAPOINT
This is by default the only check box that is enabled.
VP: PCE, DATABASE and LICENSING services
ü
CISCOSIM
This needs to be installed and configured to get call control
functioning. Typically this gets installed on the VISTAPOINT
If the Cisco TSP is not installed the installer will notify you
OPTIONAL COMPONENTS (REQUIRES IIS BE
INSTALLED)
ü One-Click Install
ü Client Web Installations
ü VistaPoint Enterprise Directory
LCS INTIGRATION
ü 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
2. When the license dialogue displays fill out the information and enter in your Product Key
Instantly
applies the license values to the machine
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.
Begins
a 30 Day Evaluation of the software
Additional Help = how to license
3. REBOOT WHEN PROMPTED
4. When logging in you will need to enter in a “Admin” password and a “Tenant Admin” password (these need to be unique, do not use the same password for each)
5. Install the VistaPoint Desktop companion OR Console (this will be used to verify the TAPI functionality of the CiscoSIM and will allow you to administer the system)
6. Launch the client application
7. Enter in your extension number
8. Enter in the IP Address or hostname of the VP Server (if the client is installed on the server this step will be skipped)
You should only see parking and route point numbers until the CiscoSIM is configured
CONFIGURING THE SERVICES
Although it is not
required, it is recommended that you install either the Desktop Companion or
the Console Companion on the server. This can be done from either the Client.zip or through your web browser if you installed the
One-Click\Web Install components (see additional documentation).
CISCO SIM
1. Right Click on the CISCOSIM tray icon and open “Device Settings” under the CallManager options.
·
Enter in and “Administration level” account
username and password. Typically we just enter in “Administrator” and the
password for that account on the CallManager machine.
·
Click on “Save and retrieve data” and you should see all your phones in the
Desktop application a few moments later (it may take a couple minutes depending
on how many devices are being monitored).
2. Right Click on the CISCOSIM tray icon and open “Directory Settings” under the CallManager options. This is where you can identify your directory source (match name and department information to extension numbers)
· EXAMPLE (Call Manager Directory)
§
§ 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)
§
§ 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 CISCOSIM