Avaya Orchestration Designer/Dialog Designer (Archive - Oct 2013 and earlier) - CTI Dial - Dial - Bad Fetch after 15 seconds... - 0

Login

Sign in using your

By continuing to use DevConnect Program Services you agree to our latest Registered Member Terms

Email *

Password *

Remember me

Forgot password?

Go to Avaya SSO ID Login
Register

Author	Message
27/06/2011 09:42:20	Subject: CTI Dial - Dial - Bad Fetch after 15 seconds... #1
sivasubramanian2 Joined: Jul 30, 2010 Messages: 4 Offline	Team, We are having an issue with the CTI Connector Dial. We are not getting response for Dial within 15 seconds and hence the application is proceeding with BadFetch flow. Details: **** DD : 5.0.0.1603 Voice Portal : 5.1 Application Flow: ********* 1. Call Agent(using CCXML) 2. Play him the customer details(Using DD app) 3. Based on his confirmation, call customer customer and join them.(using CTI Held, Call and Join). Issue: * We are having the issue while dialing the customer. And hence Bad Fetch error is thrown. Please find below the CTIConnector Logs. Please advice. Thanks, M. Sivasubramanian. CTI Connector Logs: *************** 27/06/2011 16:51:31 DEBUG - CTIConnectorManager.setTServerWait: TServer wait time is 4 27/06/2011 16:51:31 DEBUG - CTIConnectorManager.init: initing CTI connector. Verbosity set at 3 27/06/2011 16:51:31 DEBUG - CTIConnectorManager.init: CTI Version is 05.00.16.02 27/06/2011 16:51:31 DEBUG - CTIConnectorManager.CheckObserverTimeoutSet: Observer timeout interval found: 50 27/06/2011 16:51:31 DEBUG - CTIConnectorManager.getConnectionString: No entry for TServer in configuration file 27/06/2011 16:51:31 DEBUG - CTIConnectorManager.initProvider: Look for TServer config in DD application configuration (new method to 4.0) 27/06/2011 16:51:31 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: getting provider:AVAYA#S8720#CSTA#AES 27/06/2011 16:51:41 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: provider obtained 27/06/2011 16:51:41 DEBUG - CTIConnectorManager.initProvider: provider vendor version is 8 27/06/2011 16:51:41 DEBUG - CTIConnectorManager.initProvider: setup named licensing. 27/06/2011 16:51:41 WARN - CTIConnectorManager.initProvider: problem with requestPrivileges; the version of AES may not support Named Licensing. (Exception - com.avaya.jtapi.tsapi.TsapiPlatformException: Unexpected requestPrivileges TSAPI failure: com.avaya.jtapi.tsapi.TsapiPlatformException: requestPrivileges failure: com.avaya.jtapi.tsapi.TsapiPlatformException: ACS Error: 120) 27/06/2011 16:51:41 DEBUG - CTIConnectorManager.initProvider: shutdown and re-initilize provider. 27/06/2011 16:51:46 DEBUG - CTICallObserver.CTICallObserver:added 54990 observer 27/06/2011 16:51:48 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:51:51 DEBUG - CTICallObserver.CTICallObserver:added 54992 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 54994 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 54995 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 54996 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 54993 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 54997 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 54998 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 54999 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 58100 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 58101 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 58102 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 58103 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 58104 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 58105 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 58106 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 58107 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 58108 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 58109 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 58110 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 58111 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 58112 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 58113 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 58114 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 58115 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 58116 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 58117 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 58118 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 58119 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 58002 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 58003 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 58001 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 54991 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 58032 observer 27/06/2011 16:51:52 DEBUG - CTICallObserver.CTICallObserver:added 58031 observer 27/06/2011 16:51:59 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:52:07 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:52:15 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:52:23 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:52:31 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:52:39 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:52:47 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:52:55 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:53:03 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:53:11 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:53:19 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:53:27 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension 58031 is 7 27/06/2011 16:53:27 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 0 is 101 for call 5789 27/06/2011 16:53:27 DEBUG - CTICallObserver.callChangedEvent58031: got Connection Active Event 27/06/2011 16:53:27 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 1 is 106 for call 5789 27/06/2011 16:53:27 DEBUG - CTICallObserver.callChangedEvent58031: got Connection Created Event for id:5789 27/06/2011 16:53:27 DEBUG - CTICallObserver.addCall 58031: call id is 5789 27/06/2011 16:53:27 DEBUG - CTICallObserver.addCall 58031: ucid is 09999057891309173640 27/06/2011 16:53:27 DEBUG - CTICallObserver.addCall 58031: setting 5789 to state: initiated 27/06/2011 16:53:27 DEBUG - CallInfoData.CallInfoData:58031: callid 5789 27/06/2011 16:53:27 DEBUG - CallInfoData.CallInfoData:58031: ani 27/06/2011 16:53:27 DEBUG - CallInfoData.CallInfoData:58031: dnis 27/06/2011 16:53:27 DEBUG - CallInfoData.CallInfoData:58031: ucid 09999057891309173640 27/06/2011 16:53:27 DEBUG - CallInfoData.CallInfoData:58031: uui 27/06/2011 16:53:27 DEBUG - CTICallObserver.addCall 58031: added call to list 27/06/2011 16:53:27 DEBUG - CTICallObserver.addCall 58031:cache is:false 27/06/2011 16:53:27 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 2 is 105 for call 5789 27/06/2011 16:53:27 DEBUG - CTICallObserver.callChangedEvent58031: got Connection Connected Event 27/06/2011 16:53:27 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 3 is 208 for call 5789 27/06/2011 16:53:27 DEBUG - CTICallObserver.callChangedEvent:58031: got an unknown event 208 27/06/2011 16:53:27 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 4 is 116 for call 5789 27/06/2011 16:53:27 DEBUG - CTICallObserver.callChangedEvent58031: got Terminal Connection Created Event 27/06/2011 16:53:27 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 5 is 115 for call 5789 27/06/2011 16:53:27 DEBUG - CTICallObserver.callChangedEvent58031: got Terminal Connection Active Event 27/06/2011 16:53:27 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 6 is 219 for call 5789 27/06/2011 16:53:27 DEBUG - CTICallObserver.callChangedEvent:58031: got Terminal Connection Talking Event 27/06/2011 16:53:27 DEBUG - CTICallObserver.callChangedEvent:58031: found 1 connections 27/06/2011 16:53:27 DEBUG - CTICallObserver.callChangedEvent:58031: Found connections object, but not 2 active connections. May be using FastConnect 27/06/2011 16:53:27 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:53:27 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension 58031 is 1 27/06/2011 16:53:27 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 0 is 206 for call 5789 27/06/2011 16:53:27 DEBUG - CTICallObserver.callChangedEvent:58031: got Call Control Connection Established Event 27/06/2011 16:53:27 DEBUG - CTICallObserver.callChangedEvent:58031: found 1 connections 27/06/2011 16:53:27 DEBUG - CTICallObserver.callChangedEvent:58031: Found connections object, but not 2 active connections. May be using FastConnect 27/06/2011 16:53:29 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension 58031 is 6 27/06/2011 16:53:29 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 0 is 106 for call 5789 27/06/2011 16:53:29 DEBUG - CTICallObserver.callChangedEvent58031: got Connection Created Event for id:5789 27/06/2011 16:53:29 DEBUG - CTICallObserver.addCall 58031: call id is 5789 is already added, returning call data 27/06/2011 16:53:29 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 1 is 116 for call 5789 27/06/2011 16:53:29 DEBUG - CTICallObserver.callChangedEvent58031: got Terminal Connection Created Event 27/06/2011 16:53:29 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 2 is 104 for call 5789 27/06/2011 16:53:29 DEBUG - CTICallObserver.callChangedEvent58031: got Connection Alerting Event 27/06/2011 16:53:29 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 3 is 203 for call 5789 27/06/2011 16:53:29 DEBUG - CTICallObserver.callChangedEvent:58031: got Call Control alerting Event 27/06/2011 16:53:29 DEBUG - CTICallObserver.updateCallState 58031: setting call:5789 to state:ringing 27/06/2011 16:53:29 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 4 is 119 for call 5789 27/06/2011 16:53:29 DEBUG - CTICallObserver.callChangedEvent58031: got Terminal Connection Ringing Event 27/06/2011 16:53:29 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 5 is 218 for call 5789 27/06/2011 16:53:29 DEBUG - CTICallObserver.callChangedEvent58031: got Call Control Terminal Ringing Event 27/06/2011 16:53:30 DEBUG - No callid found in CTIEnd 27/06/2011 16:53:30 ERROR - No observer on extension:58044 27/06/2011 16:53:31 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension 58031 is 4 27/06/2011 16:53:31 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 0 is 105 for call 5789 27/06/2011 16:53:31 DEBUG - CTICallObserver.callChangedEvent58031: got Connection Connected Event 27/06/2011 16:53:31 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 1 is 206 for call 5789 27/06/2011 16:53:31 DEBUG - CTICallObserver.callChangedEvent:58031: got Call Control Connection Established Event 27/06/2011 16:53:31 DEBUG - CTICallObserver.callChangedEvent:58031: found 2 connections 27/06/2011 16:53:31 DEBUG - CTICallObserver.callChangedEvent:58031: state of connection 0 is 51 27/06/2011 16:53:31 DEBUG - CTICallObserver.callChangedEvent:58031: state of connection 1 is 51 27/06/2011 16:53:31 DEBUG - CTICallObserver.callChangedEvent:58031: established both connections of call 27/06/2011 16:53:31 DEBUG - CTICallObserver.updateCallState 58031: setting call:5789 to state:established 27/06/2011 16:53:31 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 2 is 115 for call 5789 27/06/2011 16:53:31 DEBUG - CTICallObserver.callChangedEvent58031: got Terminal Connection Active Event 27/06/2011 16:53:31 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 3 is 219 for call 5789 27/06/2011 16:53:31 DEBUG - CTICallObserver.callChangedEvent:58031: got Terminal Connection Talking Event 27/06/2011 16:53:31 DEBUG - CTICallObserver.callChangedEvent:58031: found 2 connections 27/06/2011 16:53:31 DEBUG - CTICallObserver.callChangedEvent:58031: state of connection 0 is 51 27/06/2011 16:53:31 DEBUG - CTICallObserver.callChangedEvent:58031: state of connection 1 is 51 27/06/2011 16:53:31 DEBUG - CTICallObserver.callChangedEvent:58031: established both connections of call 27/06/2011 16:53:31 DEBUG - CTICallObserver.updateCallState 58031: setting call:5789 to state:established 27/06/2011 16:53:35 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:53:43 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:53:51 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:54:00 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:54:01 DEBUG - CTICallObserver.addCallToCache:caching call:5789 27/06/2011 16:54:01 DEBUG - CTICallObserver.getCallInfo: app is interested in call, setting MRCA:5789 27/06/2011 16:54:01 DEBUG - CallInfo.doGetCallInfo: Got call info for extension 58031 27/06/2011 16:54:01 DEBUG - Hold.doHold:58031 putting on hold ext:58031 27/06/2011 16:54:01 DEBUG - CTICallObserver.addApplicationObserver: adding an app observer to extension:58031 27/06/2011 16:54:01 DEBUG - Hold.doHold 58031: Placing terminal connection 0 on hold... 27/06/2011 16:54:01 DEBUG - Hold.doHold 58031: Waiting.... 27/06/2011 16:54:01 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension 58031 is 1 27/06/2011 16:54:01 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 0 is 216 for call 5789 27/06/2011 16:54:01 DEBUG - CTICallObserver.callChangedEvent:58031: got Terminal Connection Held Event 27/06/2011 16:54:01 DEBUG - CTICallObserver.updateCallState 58031: setting call:5789 to state:held 27/06/2011 16:54:01 DEBUG - CTICallObserver.updateCallState 58031: setting cached call:5789 to state:held 27/06/2011 16:54:01 DEBUG - CTICallObserver.notifyApplicationObserver: Notifying 58031 about call event 27/06/2011 16:54:01 DEBUG - Hold.doHold 58031: Terminal connection 0 placed on hold 27/06/2011 16:54:01 DEBUG - Hold.doHold 58031: Done placing connections on hold 27/06/2011 16:54:01 DEBUG - CTICallObserver.removeApplicationObserver: removing an app observer from extension:58031 27/06/2011 16:54:01 DEBUG - Dial.doDial: Making call to 99841397284 from:58031 with ringmax:6 and UUI:5789 27/06/2011 16:54:01 DEBUG - CTICallObserver.addApplicationObserver: adding an app observer to extension:58031 27/06/2011 16:54:01 DEBUG - CTICallOperation.makeCall: Attempting to Connect from 58031 to 99841397284... 27/06/2011 16:54:01 DEBUG - CTICallOperation.makeCall 58031: Connecting with UUI 5789... 27/06/2011 16:54:01 DEBUG - CTICallOperation.makeCall 58031: UUI is ASCII:true 27/06/2011 16:54:01 DEBUG - CTICallOperation.makeCall: using Connect 27/06/2011 16:54:02 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension 58031 is 7 27/06/2011 16:54:02 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 0 is 101 for call 5791 27/06/2011 16:54:02 DEBUG - CTICallObserver.callChangedEvent58031: got Connection Active Event 27/06/2011 16:54:02 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 1 is 106 for call 5791 27/06/2011 16:54:02 DEBUG - CTICallObserver.callChangedEvent58031: got Connection Created Event for id:5791 27/06/2011 16:54:02 DEBUG - CTICallObserver.addCall 58031: call id is 5791 27/06/2011 16:54:02 DEBUG - CTICallObserver.addCall 58031: ucid is 09999057911309173674 27/06/2011 16:54:02 DEBUG - CTICallObserver.addCall 58031: setting 5791 to state: initiated 27/06/2011 16:54:02 DEBUG - CallInfoData.CallInfoData:58031: callid 5791 27/06/2011 16:54:02 DEBUG - CallInfoData.CallInfoData:58031: ani 58031 27/06/2011 16:54:02 DEBUG - CallInfoData.CallInfoData:58031: dnis 99841397284 27/06/2011 16:54:02 DEBUG - CallInfoData.CallInfoData:58031: ucid 09999057911309173674 27/06/2011 16:54:02 DEBUG - CallInfoData.CallInfoData:58031: uui 27/06/2011 16:54:02 DEBUG - CTICallObserver.addCall 58031: added call to list 27/06/2011 16:54:02 DEBUG - CTICallObserver.addCall 58031:cache is:true 27/06/2011 16:54:02 DEBUG - CTICallObserver.addCallToCache:caching call:5791 27/06/2011 16:54:02 DEBUG - CTICallObserver.notifyApplicationObserver: Notifying 58031 about call event 27/06/2011 16:54:02 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 2 is 105 for call 5791 27/06/2011 16:54:02 DEBUG - CTICallObserver.callChangedEvent58031: got Connection Connected Event 27/06/2011 16:54:02 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 3 is 208 for call 5791 27/06/2011 16:54:02 DEBUG - CTICallObserver.callChangedEvent:58031: got an unknown event 208 27/06/2011 16:54:02 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 4 is 116 for call 5791 27/06/2011 16:54:02 DEBUG - CTICallObserver.callChangedEvent58031: got Terminal Connection Created Event 27/06/2011 16:54:02 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 5 is 115 for call 5791 27/06/2011 16:54:02 DEBUG - CTICallObserver.callChangedEvent58031: got Terminal Connection Active Event 27/06/2011 16:54:02 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 6 is 219 for call 5791 27/06/2011 16:54:02 DEBUG - CTICallObserver.callChangedEvent:58031: got Terminal Connection Talking Event 27/06/2011 16:54:02 DEBUG - CTICallObserver.callChangedEvent:58031: found 1 connections 27/06/2011 16:54:02 DEBUG - CTICallObserver.callChangedEvent:58031: Found connections object, but not 2 active connections. May be using FastConnect 27/06/2011 16:54:02 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension 58031 is 1 27/06/2011 16:54:02 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 0 is 206 for call 5791 27/06/2011 16:54:02 DEBUG - CTICallObserver.callChangedEvent:58031: got Call Control Connection Established Event 27/06/2011 16:54:02 DEBUG - CTICallObserver.callChangedEvent:58031: found 1 connections 27/06/2011 16:54:02 DEBUG - CTICallObserver.callChangedEvent:58031: Found connections object, but not 2 active connections. May be using FastConnect 27/06/2011 16:54:08 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:54:16 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:54:16 DEBUG - Retrieve.doRetrieve: retrieving ext:58031 27/06/2011 16:54:16 DEBUG - Retrieve.doRetrieve: Terminal connection 0 state is HELD 27/06/2011 16:54:16 DEBUG - Retrieve.doRetrieve: Attempting to unhold... 27/06/2011 16:54:16 DEBUG - CTICallObserver.updateCallState 58031: setting call:5789 to state:established 27/06/2011 16:54:16 DEBUG - CTICallObserver.updateCallState 58031: setting cached call:5789 to state:established 27/06/2011 16:54:16 DEBUG - Retrieve.doRetrieve: after hold, new state in retrieve is TALKING 27/06/2011 16:54:16 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension 58031 is 6 27/06/2011 16:54:16 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 0 is 117 for call 5791 27/06/2011 16:54:16 DEBUG - CTICallObserver.callChangedEvent:58031: got an unknown event 117 27/06/2011 16:54:16 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 1 is 215 for call 5791 27/06/2011 16:54:16 DEBUG - CTICallObserver.callChangedEvent:58031: got an unknown event 215 27/06/2011 16:54:16 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 2 is 107 for call 5791 27/06/2011 16:54:16 DEBUG - CTICallObserver.callChangedEvent:58031: got Connection Disconnected Event 107 27/06/2011 16:54:16 DEBUG - CTICallObserver.notifyApplicationObserver: Notifying 58031 about call event 27/06/2011 16:54:16 DEBUG - CTICallOperation.applicationCallEvent 58031: call was terminated 27/06/2011 16:54:17 DEBUG - CTICallOperation.makeCall 58031: Returned from connect call... 27/06/2011 16:54:17 DEBUG - CTICallOperation.makeCall 58031: new call id is 5791 27/06/2011 16:54:17 DEBUG - CTICallOperation.makeCall 58031: Connection is null, disconnected new call 27/06/2011 16:54:17 DEBUG - CTICallOperation.makeCall 58031: Waiting on mutex 27/06/2011 16:54:17 DEBUG - CTIConnectorManager.dropCall: Call state of call 5791 is INVALID 27/06/2011 16:54:17 DEBUG - Dial.StopCallTimer: Could find no timer to cancel for callid:5791 27/06/2011 16:54:17 DEBUG - Mutex.setWait: wait is false 27/06/2011 16:54:17 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 3 is 205 for call 5791 27/06/2011 16:54:17 DEBUG - CTICallObserver.callChangedEvent:58031: got Connection Disconnected Event 205 27/06/2011 16:54:17 DEBUG - CTICallObserver.notifyApplicationObserver: Notifying 58031 about call event 27/06/2011 16:54:17 DEBUG - CTICallOperation.applicationCallEvent 58031: call was terminated 27/06/2011 16:54:17 DEBUG - CTIConnectorManager.dropCall: Call state of call 5791 is INVALID 27/06/2011 16:54:17 DEBUG - Dial.StopCallTimer: Could find no timer to cancel for callid:5791 27/06/2011 16:54:17 DEBUG - Mutex.setWait: wait is false 27/06/2011 16:54:17 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 4 is 103 for call 5791 27/06/2011 16:54:17 DEBUG - CTICallObserver.callChangedEvent:58031: got Call Observation Ended Event 27/06/2011 16:54:17 DEBUG - CTICallObserver.removeCall:removing call:5791 from ext:58031 27/06/2011 16:54:17 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 5 is 219 for call 5789 27/06/2011 16:54:17 DEBUG - CTICallObserver.callChangedEvent:58031: got Terminal Connection Talking Event 27/06/2011 16:54:17 DEBUG - CTICallObserver.callChangedEvent:58031: found 2 connections 27/06/2011 16:54:17 DEBUG - CTICallObserver.callChangedEvent:58031: state of connection 0 is 51 27/06/2011 16:54:17 DEBUG - CTICallObserver.callChangedEvent:58031: state of connection 1 is 51 27/06/2011 16:54:17 DEBUG - CTICallObserver.callChangedEvent:58031: established both connections of call 27/06/2011 16:54:17 DEBUG - CTICallObserver.updateCallState 58031: setting call:5789 to state:established 27/06/2011 16:54:17 DEBUG - CTICallObserver.updateCallState 58031: setting cached call:5789 to state:established 27/06/2011 16:54:17 DEBUG - CTICallObserver.notifyApplicationObserver: Notifying 58031 about call event 27/06/2011 16:54:17 DEBUG - CTICallOperation.applicationCallEvent 58031: events are not for the dialed call, returning 27/06/2011 16:54:17 DEBUG - CTICallOperation.makeCall 58031: Thread on mutex + resumed 27/06/2011 16:54:17 DEBUG - CTICallObserver.removeApplicationObserver: removing an app observer from extension:58031 27/06/2011 16:54:17 DEBUG - Dial.doDial 58031: Call ID for newly dialed call:5791 27/06/2011 16:54:21 DEBUG - CTIConnectorManager.dropCall: Call state of call 5791 is INVALID 27/06/2011 16:54:21 DEBUG - CTICallObserver.updateCallState 58031: setting call:5791 to state:disconnected 27/06/2011 16:54:21 DEBUG - CTICallObserver.updateCallState 58031: setting cached call:5791 to state:disconnected 27/06/2011 16:54:21 DEBUG - CTIConnectorManager.dropCall: Call state of call 5789 is ACTIVE 27/06/2011 16:54:21 DEBUG - CTIConnectorManager.dropCall: Address is 58031... 27/06/2011 16:54:21 DEBUG - CTIConnectorManager.dropCall: Connection 0 state is CONNECTED 27/06/2011 16:54:21 DEBUG - CTIConnectorManager.dropCall: Connection 0 for address 58031 27/06/2011 16:54:21 DEBUG - CTIConnectorManager.dropCall: Connection 1 state is CONNECTED 27/06/2011 16:54:21 DEBUG - CTIConnectorManager.dropCall: Connection 1 for address 240 27/06/2011 16:54:21 DEBUG - CTIConnectorManager.dropCall: Disconnecting connection for address 58031... 27/06/2011 16:54:21 DEBUG - CTICallObserver.doDisconnect:no UUI during disconnect for cid:com.avaya.sce.cticonnector.servlet.server.CallInfoData@14cecee 27/06/2011 16:54:21 DEBUG - CTIConnectorManager.dropCall: Call com.avaya.jtapi.tsapi.ci@1243618 dropped 27/06/2011 16:54:21 DEBUG - CTICallObserver.updateCallState 58031: setting call:5789 to state:disconnected 27/06/2011 16:54:21 DEBUG - CTICallObserver.updateCallState 58031: setting cached call:5789 to state:disconnected 27/06/2011 16:54:21 DEBUG - Ending call on extension 58031 27/06/2011 16:54:21 DEBUG - CTICallObserver.removeAllCalls: Callid: id on extension:58031 is 5789 MRCA:5789 27/06/2011 16:54:21 DEBUG - CTICallObserver.removeAllCallsFromCache:clearing out MRCA 27/06/2011 16:54:21 DEBUG - CTICallObserver.removeAllCallsFromCache:removed all calls from extension:58031 27/06/2011 16:54:21 DEBUG - CTICallObserver.removeAllCallsFromCache:removed all calls from cache at extension:58031 27/06/2011 16:54:21 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension 58031 is 4 27/06/2011 16:54:21 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 0 is 117 for call 5789 27/06/2011 16:54:21 DEBUG - CTICallObserver.callChangedEvent:58031: got an unknown event 117 27/06/2011 16:54:21 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 1 is 215 for call 5789 27/06/2011 16:54:21 DEBUG - CTICallObserver.callChangedEvent:58031: got an unknown event 215 27/06/2011 16:54:21 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 2 is 107 for call 5789 27/06/2011 16:54:21 DEBUG - CTICallObserver.callChangedEvent:58031: got Connection Disconnected Event 107 27/06/2011 16:54:21 DEBUG - CTICallObserver.callChangedEvent:58031: got disconnect, but no cticall found. 27/06/2011 16:54:21 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 3 is 205 for call 5789 27/06/2011 16:54:21 DEBUG - CTICallObserver.callChangedEvent:58031: got Connection Disconnected Event 205 27/06/2011 16:54:21 DEBUG - CTICallObserver.callChangedEvent:58031: got disconnect, but no cticall found. 27/06/2011 16:54:21 DEBUG - CTICallObserver.callChangedEvent: Number of events on extension 58031 is 1 27/06/2011 16:54:21 DEBUG - CTICallObserver.callChangedEvent 58031: Event: 0 is 103 for call 5789 27/06/2011 16:54:21 DEBUG - CTICallObserver.callChangedEvent:58031: got Call Observation Ended Event 27/06/2011 16:54:24 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:54:32 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:54:40 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:54:48 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:54:56 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:55:04 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:55:12 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:55:20 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:55:28 DEBUG - ProviderMonitor: Checking:ServionAES for availability 27/06/2011 16:55:36 DEBUG - ProviderMonitor: Checking:ServionAES for availability
	Profile PM

27/06/2011 10:29:55	Subject: Re: CTI Dial - Dial - Bad Fetch after 15 seconds... #2
NeilGoldsmith Joined: Nov 6, 2013 Messages: 902 Offline	The first thing I'm noticing is a very long delay from the time the AES reports the initial call arrives until VP processes it. You can see from the top of your log that the AES establishes the call a full 30 seconds before the app expresses interest in the call. Do you have CTI set to auto invoke CallInfo (the default setting)? You should investigate this as the call should hit the AES and VP at about the same time. As far as the dial operation, I don't see the dial ringing or going to queue or anything of that nature. It doesn't show 2 connections on the call. In order to investigate this further, you will need to generate a JTAPI log by editing your tsapi.pro and setting debug level = 7 (restart Tomcat). Rerun the test, then turn off the JTAPI log or it will grow very fast very quickly. The JTAPI log is called tsapi_log.txt. You will need to get JTAPI support involved to investigate this. They should also investigate why you have such a long delay when the call arrives. INITIAL CALL ARRIVING: 27/06/2011 16:53:31 DEBUG - CTICallObserver.callChangedEvent:58031: established both connections of call 27/06/2011 16:53:31 DEBUG - CTICallObserver.updateCallState 58031: setting call:5789 to state:established 27/06/2011 16:54:01 DEBUG - CTICallObserver.addCallToCache:caching call:5789 27/06/2011 16:54:01 DEBUG - CTICallObserver.getCallInfo: app is interested in call, setting MRCA:5789
NeilGoldsmith Joined: Nov 6, 2013 Messages: 902 Offline	Profile PM

28/06/2011 06:07:52	Subject: Re: CTI Dial - Dial - Bad Fetch after 15 seconds... #3
sivasubramanian2 Joined: Jul 30, 2010 Messages: 4 Offline	Team, I have the JTAPI logs, but the size is around 2MB and hence unable to submit via the Forum. Please let me know the mail Id for which I can send the logs. Please advice. Thanks, M. Sivasubramanian.
	Profile PM

28/06/2011 10:18:26	Subject: Re: CTI Dial - Dial - Bad Fetch after 15 seconds... #4
NeilGoldsmith Joined: Nov 6, 2013 Messages: 902 Offline	You need to open a case with Avaya JTAPI/AES support and they will instruct you how to send the logs.
NeilGoldsmith Joined: Nov 6, 2013 Messages: 902 Offline	Profile PM

Go to: