Jtapi Provider Configuration; Jtapi Provider Migration - Cisco CRS-1 - Carrier Routing System Router Administration Manual

Chapter 15 The Subsystems Menu

JTAPI Provider Configuration

Caution

JTAPI Provider Migration

Use the JTAPI Provider Configuration web page to enter the location of your
JTAPI provider, user ID, and password.
Some Active Directory setups may prevent the Call Manager directory
administrator from creating new JTAPI providers in a multi-server configuration.
If this setup applies to you, be sure to delete preexisting JTAPI providers before
creating new JTAPI providers. For example, if the JTAPI provider prefix is jtapi
and you have a two-server configuration (node_id1 and node_id2), then you must
delete both jtapi_<node_id1> and jtapi_<node_id2>. If you do not verify and
delete preexisting JTAPI providers, the JTAPI subsystem issues an error and will
not allow you to create JTAPI providers from the Cisco CRS JTAPI Provider
Configuration web page.
To access this configuration area, click the JTAPI Provider hyperlink on the
navigation bar of any JTAPI Configuration web page.
Related Topic
Configuring a JTAPI Provider, page 3-6
If you need to migrate to a new Unified CM (or Unified CM cluster), enter the new
Unified CM hostname/IP address, user prefix and password. If CRS is able to
contact the new Unified CM, it will present three options:
Remove all the JTAPI Information (JTAPI Users, JTAPI Port Groups, JTAPI
•
Triggers) from the current Unified CM and create all new JTAPI Information
in the new Unified CM.
If you choose this option and any of the JTAPI users or triggers already exist
on the new Unified CM, the migration process stops and a message displays
indicating the reason. However, if any of the CTI Ports in a PG already exist
in the new Unified CM, the migration will proceed, as it will not use the
existing CTI Port and will try to use the next available CTI Port number.
Cisco Customer Response Solutions Administration Guide, Release 4.1(1)
The JTAPI Menu Option
15-3