cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3170
Views
5
Helpful
16
Replies

finesse 11.6 with UCCE - update call variable issue

cukouncukoun
Level 1
Level 1

Hi all,

we are experiencing issue with CTI call variable issue from Finesse desktop. Updating of standard CallVariables1-10 and custom ECC variables working without any issue BUT we are not able to update customerAccountNumber and customerPhoneNumber variables from Finesse. These variables are normally used by dialer on outbound calls and we are able to update them without any issues from CTIOS desktop but not from finesse :-(

When we tried to update them from Finesse, Finesse decline this due to some unknown (Invalid input) reasons:

0003244291: 10.105.170.103: Feb 12 2018 10:20:33.398 +0100: %CCBU_http-apr-8082-exec-14-6-REQUEST_START: %[method_name=PUT][parameter_name={  }][resource_name=/Dialog/16851191][usr=12345]: Request start

0003244292: 10.105.170.103: Feb 12 2018 10:20:33.404 +0100: %CCBU_http-apr-8082-exec-14-6-API_REQUEST: %[REQUEST_URL=Dialog/16851191][agent_id=12345][requestId=null][request_method=dialog.PUT][request_parameters= requestedAction:UPDATE_CALL_DATA mediaProperties:  Call Variables Collection: [ name:callVariable8 value:0604294289,  name:callVariable10 value:636540240277510000.58648,  name:user.ECC_CallRecID value:ECC636540240277510000.58648,  name:customerAccountNumber value:AAAAA] mediaId:1]: Request from client to webservice api

0003244293: 10.105.170.103: Feb 12 2018 10:20:33.404 +0100: %CCBU_http-apr-8082-exec-14-4-RUNTIME_ERROR: %[ERROR_DESCRIPTION=com.cisco.ccbu.finesse.cti.service.dialog.CCEDialogCtiService][exception=RuntimeException][noname=com.cisco.ccbu.finesse.api.exception.InvalidInputException]: Runtime error

0003244294: 10.105.170.103: Feb 12 2018 10:20:33.406 +0100: %CCBU_http-apr-8082-exec-14-4-EXCEPTION_INFO: %[build_date=Jan 01, 1970 1:00 AM][build_type=rel][exception=com.cisco.ccbu.finesse.api.exception.InvalidInputException

    at com.cisco.ccbu.finesse.cti.service.dialog.DialogValidator.validateCallVariable(DialogValidator.java:399)

    at com.cisco.ccbu.finesse.cti.service.dialog.DialogValidator.validateCallVariables(DialogValidator.java:363)

    at com.cisco.ccbu.finesse.cti.service.dialog.DialogValidator.validatePUTMediaProperties(DialogValidator.java:241)

    at com.cisco.ccbu.finesse.cti.service.dialog.DialogValidator.validatePUTRequest(DialogValidator.java:165)

    at com.cisco.ccbu.finesse.cti.service.dialog.DialogValidator.validateDialogObject(DialogValidator.java:109)

    at com.cisco.ccbu.finesse.cti.service.dialog.DialogCtiService.validate(DialogCtiService.java:215)

    at com.cisco.ccbu.finesse.cti.service.AbstractCtiService.validate(AbstractCtiService.java:80)

    at com.cisco.ccbu.finesse.api.queuemanager.QueueManager.handleRequestImpl(QueueManager.java:137)

    at com.cisco.ccbu.finesse.api.queuemanager.QueueManager.handleRequest(QueueManager.java:90)

    at com.cisco.ccbu.finesse.api.dialog.DialogService.update(DialogService.java:146)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

    at java.lang.reflect.Method.invoke(Method.java:606)

So my questions is how Finesse server know which normal and ECC variables are available (configured on the UCCE) so which variables can be used on the call? Because on the logs we see that API request from desktop was declined directly by Finesse and no request was sent to CTI server.Based on this Finesse server needs to know which variables are available.

Thanks

Tomas

16 Replies 16

Hi Denise,

thanks for your time and cooperation :-). I tried to view this bugID but I'm getting answer that bug with this id does not exist so its probably not visible publically...:-(

But as you mentioned that this is enhancement request it means that it take a long time than it will be in finesse or is there option that it could be soon.

Thanks

Tomas

Hi Tomas,

Yeah I don't think these bugs get populated to the public this quickly.

The speed of fixing this bug is up to the Finesse PO. The Finesse PO was already in the loop for this discussion and this was the conclusion the team made for this issue. They will evaluate the effort of this enhancement and see if it can fit into the upcoming release.

Thanx,

Denise