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. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

IPCC 3.1 -> 4.02 upgrade issues

Upgraded CCM from 3.3.3 to 4.1 That went fine no issues.

Upgraded the IPCC from 3.1 to 4.02 now agents can't login. Getting LDAP error. Also, none of the CTI ports are registered with CCM...The subsystem service shows stopped but all subsystems are configed correctly. (Jtapi, RM, etc.) Jtapi versions are the same etc. DC directory and LDAP appear to be setup correctly.(correct passwords etc.)

Are there any known issues etc.... Where could the problem be?

thanks

1 REPLY

Re: IPCC 3.1 -> 4.02 upgrade issues

When I had the problem of the JTAPI subsystem not starting, it ended up being a bogus HTTP trigger in Active Directory. I didn't have any HTTP triggers configured, but one showed up after the upgrade. The solution was to delete the HTTP trigger. I'm not sure if this issue is specific to AD or could also occur with DC directory. If you are working with TAC, have them refer to case# 602121725.

Hope this helps.

Brandon

110
Views
0
Helpful
1
Replies