TimeoutException in JTAPI

[ashish.nijai]

I have added some devices as CTI devices, mainly IP Communicators

These devices can call, answer call and perform all telephony commands.

When i started to monitor these devices, I am getting TimeoutException.

I am monitoring these devices as super provider.

Dont know how to solve the issue.

Please help...

[mpotluri]

Ashish,

  What API call is getting this exception? Can you attach JTAPI log from the application start time?

[ashish.nijai]

All log files generated by JTAPI are empty.

So I am adding excerpt of application log files here:

2014-07-24 14:42:24 INFO  Dialer:717 - Provider name: 192.168.52.207

2014-07-24 14:42:54 ERROR Dialer:145 - Error at registering terminal/addresses:Terminal SEP101F740EEA25tryCreateTerminal caught CCNException  :com.cisco.cti.client.TimeoutException

2014-07-24 14:42:55 INFO  MyProviderObserver:51 - Address:3434 created

2014-07-24 14:42:55 INFO  DialerThread:22 - Thread started for 3434

2014-07-24 14:42:55 INFO  MyProviderObserver:58 - CiscoTerminal:SEPF47F35A3598D in service.

2014-07-24 14:43:25 ERROR Dialer:145 - Error at registering terminal/addresses:Terminal SEPFACEFACEFACEtryCreateTerminal caught CCNException  :com.cisco.cti.client.TimeoutException

2014-07-24 14:43:55 ERROR Dialer:145 - Error at registering terminal/addresses:Terminal SEP101F740EEA2EtryCreateTerminal caught CCNException  :com.cisco.cti.client.TimeoutException

[mpotluri]

TimeoutException typically indicates that CTIManager service did not get and send the required info about this device. Try restarting the CTIManager service and make sure that IPcommunicator is registered to one of the nodes in its device pool.

JTAPI logs are controlled by jtapi.ini file which should be in the same directory as jtapi.jar.  Run jtprefs app and enable all tracing and this should create the ini file. Copy the ini file with traces enabled (all lines in the file with CAPS should have 1) to the folder where you have jtapi.jar if application is not using the default class path.

If timeout is happening in CTIManager, you have to collect the JTAPI and CTIManager logs and approach Cisco for debugging the issue.

[ashish.nijai]

I used jtprefs app and enable all tracing. But it is creating empty log files.

IP Communicator is registered as CTI device in CUCM.

[mpotluri]

Did you restart the app after enabling the trace levels? Can you attach the jtapi.ini file?

[ashish.nijai]

I changed name of device from SEPabcdefgh to SEPABCDEFGH in CUCM.
After that I can monitor that device.

What's reason for it?

[ashish.nijai]

I am getting same error again.

Please find log files attached.

[mpotluri]

What type of phone is SEP101F740EEA2E? Is the 'Allow Control of Device from CTI' check box on Device config page enabled?

You probably need to collect CTIManager service logs as well and raise a case with Cisco developer services.

[ashish.nijai]

Type of SEP101F740EEA2E phone is  Cisco IP Communicator.

'Allow Control of Device from CTI' is enabled for  SEP101F740EEA2E.

Please help me about  how to raise case with Cisco developer services.

[mpotluri]

https://developer.cisco.com/site/collaboration/management/axl/community-and-support/open-a-support-case/

[ashish.nijai]

This link is for opening support case for AXL.

Please give link for opening case for JTAPI.

[mpotluri]

https://developer.cisco.com/site/collaboration/call-control/jtapi/wiki/case-opening-steps/index.gsp

[ashish.nijai]

Thanks...