Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

IPCC express JTAPI

dear all

When i add jtapi subsystem and give ip address of JTAPI provider and users it gives an error:

ERROR WHILE UPDATING THE JTAPI PROVIDER

please help

2 REPLIES
Silver

Re: IPCC express JTAPI

Do you have the CTI Manager service running on the server you're attempting to make a JTAPI Provider?

In CRS 4.x and later, it should create the JTAPI and RM JTAPI users, but it may prompt for CCM 'administrator' credentials to add the users. If you have MLA enabled, this really means the 'ccmadministrator' user or a user with similar privileges.

Cisco Employee

Re: IPCC express JTAPI

Please check you have enabled AXL updates on the Call Manager side:

A) For CUCM 4.x

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/4_1/install/p

lugins/plug413.htm#wp54764

and setup a directory administrator user (say, “DCD ADMIN”) that does not have write access to the Users ou, the following steps need to be followed to allow CRS 4.0 to create JTAPI/RMJTAPI users and triggers via CRS Appadmin.

1. ****Enable AXL updates to be performed on all CTI Managers

Step 1 Browse to C:\dcdsrvr\config, and open the file, UMDirectoryConfiguration.ini, in Notepad.

Step 2 In the UMDirectoryConfiguration.ini file, locate the key, UserDirAccess.

Step 3 Change the UserDirectAccess value to true.

Step 4 In Notepad, choose File > Save to save the file.

Step 5 Close the UMDirectoryConfiguration.ini file.

Step 6 Choose Start > Run.

Step 7 Enter regedit in the Open field and click OK.

Step 8 Browse to \\HKEY_LOCAL_MACHINE\Software\Cisco Systems, Inc.\Directory

Configuration within the registry.

Step 9 In the right pane, double-click the DirAccess registry key.

Step 10 Delete the false registry entry and enter true as the new registry entry.

Step 11 Restart the IIS Admin Service and its dependent services by choosing Start >

Programs > Administrative Tools> Services.

Step 12 Right-click IIS Admin Service and then choose Restart.

Step 13 A dialog box prompts you to restart dependent services. These services may differ

depending on your configuration. Click Yes.

Step 14 Restart the dependent services.

2. Configuring JTAPI user in CRS appadmin

Go to the Subsystems->JTAPI page and try to add a JTAPI provider (you will be required

to enter a user prefix). It should come back with a pop up giving you a list of users it

could not create and will ask you to click “OK “ only after you create the user and "enable CTI Application Use". Go ahead and create the users(as specified below) with the same password you provided on the JTAPI page and enable the CTI Application use in the User Config page of CM. Click “OK” on the CRS appadmin page. The user should get created successfully. Restart the Engine. Now, try to create CTI Portgroup and triggers.

3. Configuring RMJTAPI user in CRS appadmin

Create the RMJTAPI user in Active Directory

Add a new user(s) with the format

you only need to create one RMJTAPI user, even if you have 2 engine nodes in your

cluster).

****Give the DCD ADMIN account write permission to only this user in the Users ou (by using the Security tab in the properties of this user, through ADSI edit)

Now , go to Subsystems->RmCm on the CRS Appadmin page and enter the same userid and

password for RMJTAPI user (that you just created in AD). It will come back with a message saying that the user exists and ask if you want to use that user. Select “YES”. The page should return successfully. Restart the Engine.

B) For CUCM 5.x, 6.x from ControlCenter please confirm that the AXL Web Service is running.

Finally in CUCM 5.x and 6.x you are using a HTTP post operation when trying to perform those changes:

Can you confirm that there is no special characters in the password field? The reason for this is there are some special/reserved characters, like #,$,@ etc., in HTTP which cannot be used as such.

If you need use those in the password field then you need to follow the URL encoding scheme (RFC 2396 ). That is the special character must be encoded to an equivalent "%[ASCII Hex Value]" while sending any AXL Request.

For example, a password "c#isco" should be written as "c%23isco" for the password field while running the AXLSQLToolkit command where 23 is the ASCII equivalent HEX value for character "#".

The list of all characters that can be located on the keyboard and their

corresponding ASCII hex value. Please also noted that the password cannot start with a blank.

Regards,

Riccardo

307
Views
0
Helpful
2
Replies
CreatePlease login to create content