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

Upgraded Callmanager to 4.1.3sr3 and ICD agents cannot go active

Upgraded PUB and SUB from 4.0.1 to 4.1.3sr3 and now my ICD clients cannot go active. They can log in but get the error "Request to change agent state failed. Unable to change agent state.

5 REPLIES
Hall of Fame Super Red

Re: Upgraded Callmanager to 4.1.3sr3 and ICD agents cannot go ac

Hi Roy,

A couple of questions;

a) are the ICD extensions associated with the RMUser in the directory?

b) Have you tried updating the RM JTAPI Provider and restarted the CRA Engine?

Let us know how you make out.

Hope this helps!

Rob

Please remember to rate helpful posts........

New Member

Re: Upgraded Callmanager to 4.1.3sr3 and ICD agents cannot go ac

My ICD extensions are associated with the RMUser in the directory.

I have updated the RM JTAPI Provider and restarted the CRA Engine.

The clients can log in they just cant go active.

Re: Upgraded Callmanager to 4.1.3sr3 and ICD agents cannot go ac

Definitely download JTAPI plugin or run the update tool to make sure your JTAPI versions are synced.

Re: Upgraded Callmanager to 4.1.3sr3 and ICD agents cannot go ac

Did you run the JTAPI update utility as indicated in the following link?

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_installation_guide_chapter09186a00803f5c3c.html#wp1044748

Hope this helps. If so, please rate the post.

Brandon

New Member

Re: Upgraded Callmanager to 4.1.3sr3 and ICD agents cannot go ac

Did that sync tool resolve it? I am having the same issue, but it's only with one or two clients (out of 200).

Anybody else have other ideas?

If you solved it, what did you do?

Thanks!

147
Views
0
Helpful
5
Replies