Jtapi Trigger Error "Could not update the user on the CallManager."

Unanswered Question

Has anyone encountered this error IPCC Express v 4.0.4 sr1 b029, CCM 4.2, trying to add jtapi trigger via the ?Appadmin? page to an existing application which already has 2 other triggers associated to it. Error: ?* Could not update the user on the CallManager. ?, I ?ve already updated the jtapi user password and run an sync, still same issue, even tried it with different extensions, I can add CTI route points and users all day long, and associate them to the jtapi_1/2 user with out any issues !!!???

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
smahbub Wed, 02/14/2007 - 07:04

To resolve this issue for the first condition, perform these steps:

Launch ADSIEdit to look directly at the attributes in the AD for the user in question.

Navigate to the CN=user1,OU=evt,OU=avvid,DC=irvine,DC=com entry. Right click the object, and choose Properties. Under Select a property to view, select the ciscoatGUID. Take a backup of the value present for the ciscoatGUID attribute for this user by saving the ciscoatGUID value into a notepad so that it can be put back, if required.

Remove the value present for the ciscoAtGUID attribute, from these three entries in the AD server:

CN=user1-profile,OU=profiles,OU=CCN,OU=Cisco,DC=irvine,DC=com

CN=user1-CCNProfile,OU=profiles,OU=CCN,OU=Cisco,DC=irvine,DC=com

CN=user1,OU=evt,OU=avvid Unit,DC=irvine,DC=com

Try to associate a device to the user1 user from the Cisco CallManager pages.

To resolve the second condition, perform these steps:

Launch ADSIEdit to directly look at the attributes in the AD for the user in question.

Navigate to the CN=user1,OU=evt,OU=avvid,DC=irvine,DC=com entry. Right click the object, and choose Properties. Under Select a property to view, select the ciscoatGUID.

Clear the current value present for the ciscoAtGUID attribute.

Select the ciscoatUserProfile attribute for the same user, and clear it as well.

Select the ciscoatUserProfileString attribute for the same user, and clear it.

(Optional) For housekeeping, delete the orphan profile entries for the user from the Cisco OU, like OU=profiles,OU=CCN,OU=Cisco,DC=irvine,DC=com.

For example, if olduser1 had been renamed to user1, the entries in the Cisco OU beginning with user1 or olduser1 could be deleted. The new ones are recreated when the new device association is done. Refer to these examples:

CN=olduser1-profile-{00229191414072004},OU=profiles,OU=CCN,OU=Cisco,DC=irvine,DC=com

CN=olduser1-CCNProfile-{00229191414072004},OU=profiles,OU=CCN,OU=Cisco,DC=irvine,DC=com

CN=user1-CCNProfile-{00229191414072004},OU=profiles,OU=CCN,OU=Cisco,DC=irvine,DC=com

Try to associate a device to the user1 user from the Cisco CallManager Administrator pages.

Note: The resolution steps for condition 2 also resolve the first condition, by removing all the Cisco CallManager-specific information regarding this user in the AD.

This problem can also be resolved by upgrading the Cisco CallManager to any one these versions:

003.003(004.134)

004.001(002.079)

004.001(002.080)

04.0(02a)ES21

xavigo_cisco Tue, 03/27/2007 - 03:48

Just guessing if you're deployment is Corporate Directory-integrated (AD/Lotus) and the jtapi_user's description is "CiscoPrivateUser" to hide it from Corp Dir listing. IPCC needs it to be visible to update it.

If hiding it is a requirement you can manually do the same as IPCC does, that is, associating the Route Points, CTI ports with the jtapi user or, alternatively "unhide" it, do your changes and "hide" it again.

Same goes for rmjtapi_user, if you're using it.

Hope that helps

Actions

This Discussion