UCCX 7.0(1)SR1 Cisco JTAPI client versions are inconsistent

Unanswered Question
Apr 6th, 2009

I just found an error in the call center system that Cisco JTAPI client versions are inconsistent. Please go to Cisco JTAPI resync in the Unified CM Telephony SYstem.


Customer rebooted the UCCX servers on Friday due to errors.


This was a new deployment of UCCX 7.0(1)SR1 in HA and CallManager 7.0(2) cluster. Everything worked great for 5 days then customer noticed partial service in AppAdmin and a JTAPI error and rebooted.


No changes were made in CallManager or UCCX, wondering if this is a bug in UCCX 7.0(1)SR1 ?




  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (3 ratings)
Loading.
iftikharsyed_2 Fri, 04/10/2009 - 03:48

Hi,

This issue has been adressed on this forum many times.


Try this,


1. Download JTAP Client from Call manager Plugins and install it on IPCC.

2. Create c:\winnt and copy java folder there.


Now resync Hope it will resolve your issue.



Plz Rate helpful posts.


Regards,

Ifftkhar Ahmed



Jason Aarons Fri, 04/10/2009 - 04:03

So it was in sync for several days, nothing changed in CallManager. There shouldn't be any reason to download the JTAPI client and resync.


I was looking more for a bug id than steps to fix it.

Chris Deren Fri, 04/10/2009 - 06:17

Was CM originally installed as 7.0.2 or was it upgraded from 7.0.1 or previous version?

If it was upgraded then the resynch needed to take place, if it was not then it definitely sounds like a bug. I've done couple UCCX 7.0.1 installs lately and have not run into this.


HTH,


Chris

Jason Aarons Fri, 04/10/2009 - 08:50

CallManager 4x used DMA 7.0(2) then ran Communication Manager 7.0(2) install. No RTMT or Cisco Unified Reporting Database errors, and "utils dbreplication status" had all nodes -2 (completed replication).


We then ran UCCX 7.0(1) setup.exe and built the two HA nodes, applied SR1.


UCCX ran clean no issues for 10 days, then started complaining about JTAPI errors.

ashrus7809 Thu, 03/18/2010 - 14:36

Hi,


re-sync the jtapi and restart thr CRS server , it will solve the issue..


Rgds,


Ashraf

Actions

This Discussion