Provisioning Jtapi Call Control Groups - Cisco CRS-1 - Carrier Routing System Router Administration Manual

Provisioning the JTAPI Subsystem

Provisioning JTAPI Call Control Groups

Step 1
Cisco Customer Response Solutions Administration Guide, Release 4.1(1)
3-8
– Enter your Unified CM Login User ID and Password and click Logon.
Note If the User ID (<userprefix>_<nodeid>) already exists in the Unified
CM, then Cisco CRS will return an error saying, "JTAPI Provider
cannot be configured successfully."
To remedy this problem, either specify a new user prefix or delete the
users from the Unified CM and try again.
Cisco CRS displays the following message:
•
"JTAPI Provider has been configured successfully. Please restart the CRS
Engine."
– Use the CRS Control Center to Restart the CRS Engine.
For point 2: When the user enters user prefix say jtapiuser for a single CRS
Engine node cluster, CRS will try to create jtapiuser_1 in the jtapi provider. But
if jtapiuser_1 already exists for some reason, then CRS will return error saying
that the JTAPI provider cannot be configured. If you receive the
cannot be configured
the Unified CM. If so delete that user ID in the Unified CM or use a different user
ID.
You are now ready to provision JTAPI call control groups.
The CRS system uses JTAPI call control groups to pool together a series of CTI
ports, which the system uses to serve calls as they arrive at the CRS server. You
can create multiple JTAPI call control groups in order to share and limit the
resources to be used by specific applications.
To configure a JTAPI call control group, complete the following steps.
Procedure
From the CRS Administration menu bar, choose Subsystems > JTAPI.
Chapter 3
error, verify if the user ID already exists with the _1 in
Provisioning Telephony and Media
JTAPI provider