cancel
Showing results for 
Search instead for 
Did you mean: 
cancel

'Cti request timed out' using call.conference()

838
Views
0
Helpful
0
Comments
This document was generated from CDN thread

Created by: Matt Stromske on 08-08-2011 12:13:48 PM
Hello,
  When attempting to conference calls together using call.conference(), I see the following exception:
 

com.cisco.jtapi.PlatformExceptionImpl: Cti request timed out
at com.cisco.jtapi.CallImpl.conference(CallImpl.java:1718)
at com.singlewire.plugin.ccp.conferencecontroller.ConferenceController.talkingEvent(ConferenceController.java:467)
at com.singlewire.plugin.ccp.conferencecontroller.ConferenceController.callChangedEvent(ConferenceController.java:146)
at com.cisco.jtapi.ObserverProxy.deliverEvents(ObserverProxy.java:188)
at com.cisco.jtapi.ObserverThread.messageReceived(ObserverThread.java:38)
at com.cisco.cti.util.MessageThread.deliver(MessageThread.java:358)
at com.cisco.cti.util.MessageThread.deliverAll(MessageThread.java:337)
at com.cisco.cti.util.MessageThread.run(MessageThread.java:282)


I'm using Cisco Jtapi version 8.6(0.96000)-9 Release.


What is happening here?  Is the timing configurable?


Thanks,
Matt

Subject: RE: 'Cti request timed out' using call.conference()
Replied by: Joseph Moskie on 08-08-2011 02:09:49 PM
This exception means that the CTI layer underneath JTAPI did not respond to JTAPI's request for a conference in time.

By default, the JTAPI timeout for CTI requests is 15 seconds.

This is configurable in two ways:
  1. Editing this line in jtapi.ini: JtapiPostConditionTimeout=15
  2. Invoking the following method during the run: CiscoJtapiProperties.setJtapiPostConditionTimeout(int seconds)

The minimum is 10 seconds and the maximum is 20 seconds, so there's not much play there.

This exception could result from load on the CUCM server, or some sort of connectivity issue with the CUCM server in general.