This document was generated from CDN thread
Created by: Reinhard Schloeglhofer on 05-03-2013 06:01:12 AM
Hello, I have developed an application which needs to set a call variable which is received from a customer service after the established call event. The CTIOS log shows the following entry: Trace: CRITICAL: ServiceQueuePostThread caught exception while processing a request[eSetCallDataRequest], GetLastError() returned 0. This is the Java code: Arguments callData = currentcall.GetCallData(); callData.SetValue(CtiOs_IKeywordIDs.CTIOS_CALLVARIABLE7, value); errorcode = currentcall.SetCallData(callData); errcode is always 1 (OK) but 0 (FAILED) in the CTIOS log. Does anyone have an idea why the setting of a call variable fails ? Thanks in advance Best regards Reinhard
Subject: RE: New Message from Reinhard Schloeglhofer in Computer Telephony Integrati
Replied by: David Lender on 05-03-2013 07:51:49 AM
Are you receiving either a SetCallDataConf or a onControlFailureConf? What is in your CTIOS client log? The CTIOS Server log? Is currentcall set correctly? If so, try logging callData arguments array to verify the get is working correctly.
Subject: RE: New Message from Reinhard Schloeglhofer in Computer Telephony Integrati
Replied by: Reinhard Schloeglhofer on 05-03-2013 10:44:56 AM
Hi David, I have now attached the different logs and the source code. The setCallDataConf or ControlFailureConf are not received. The dumped call data are ok (see CallVariable7)
Subject: RE: New Message from Reinhard Schloeglhofer in Computer Telephony Integrati
Replied by: David Lender on 05-03-2013 11:02:03 AM
Your application is using a monitor (filter) mode connection. Monitor mode connections are for receiving events only. You are not allowed to control calls or agents or set call data from a monitor mode session.
Subject: RE: Setting call variables in CTIOS application in monitor mode
Replied by: Reinhard Schloeglhofer on 06-03-2013 12:41:51 AM
Thank you for this information. I did not find anything about this restriction in the CTIOS documentation. But from the wording point of view it is clear now. I think i will need to use supervisor mode.
