« Back to Cisco JTAPI Questions

CiscoTerminal.getDeviceState() does not return current terminal status

Combination View Flat View Tree View
Threads [ Previous | Next ]
toggle
Hi to all.
I develeoped an application that monitor and control phones and CTI Portti implement a Telephone Console.
My test plant is based on CUCM<strong style="font-family: Arial, Helvetica, sans-serif; font-size: 11px;"> 8.5.1.10000-26, on a single server. 
In production, my client has a CUCM 8.6.2.20000 in cluster. In test environment it works fine.
In production environment I found a bug that invalidates all my work: CiscoTerminal.getDeviceState() does not return current terminal status, it always says Idle State  despite there are calls in progress.
I found the following bug: http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtu92322
It seems my problem. Anyone else has had the same problem ? I have to update the CUCM ?  My client is not happy to install a new version, but if it is the only solution I'll do it.
 
 
 

It definitely sounds like you are hitting that bug.  I suggesting advising the customer that the issue appears to match CSCtu92322, a fix for which is available in UCM Engineering Special patch 8.6.(2.21010-1) or later.  The customer would need to open a case with Cisco TAC to request this patch and any deployment assistance.
As upgrading can be a significant effort/risk for the customer, we generally like to confirm a defect before recommending an upgrade.  If you have a CDN Developer Support contract, you can open a case with our team and we can confirm the defect.  http://developer.cisco.com/web/jtapi/wikidocs/-/wiki/Main/JTAPI+Case+Opening+Steps

Thanks for your response.
My client has upgraded the CUCM with 8.6.2.21900-5 version. 
The bug seems to be resolved, but there is still an error:
With IPPhones it works well, but with CTI Ports it works only after a reset of the device, that is: when we restart our server and after we have registered the CTI Ports, the getDeviceState() still does not returnj the current terminal status. We have to reset all CTI Ports (manually) to get the right device Status.
This is a problem, because we have 3 nodes in cluster for our server that controls CTI ports one at a time and we can't reset CTI Ports after only one node have to be restarted.
 
Any idea ? We are thinkling to open a case with CDN, but my client is waiting for an answer as soon as possible,
Thanks.

Certainly doesn't sound like the intended behaviour, and I can't think of any valid reasons or configurations that could cause it (is the JTAPI client library matched with the UCM version now installed?)  Recommend opening a CDN DS case.

JTapi version matches with UCM version. The problem with CTI Ports still remains.
We have found a  workaround to resolve this (we find some calls on the DN), so we don't use getDeviceState no more.

I am currently out of town and will be back to HK on 18/11. My response will be delayed due to limited internet access and timezone difference. Please drop me an email for any issues or call me for any urgency.

I am currently out of town and will be back to HK on 18/11. My response will be delayed due to limited internet access and timezone difference. Please drop me an email for any issues or call me for any urgency.