8 Replies Latest reply: Nov 16, 2017 2:42 PM by pavelekshin RSS

Finesse SSO agent fails to complete login due to CTI Server error

Erik Ergen

Has anybody experienced this issue where SSO enabled agent logs in with an extension, Finesse sends API request to CTI server to set agent state, CTI server chokes on the message complaining about:

 

17:12:08:300 cg1A-ctisvr Invalid Enterprise CTI message received from session: 4 (client Finesse at (10.86.140.80:53613)), type: SET_AGENT_STATE_REQ, error: E_CTI_INVALID_TAG_FOR_MSG_TYPE, field: ClientID.

17:12:08:301 cg1A-ctisvr Trace: #################################################

17:12:08:301 cg1A-ctisvr Trace: ###!!!Invalid Message INGORE and CONTINUE !!!###

17:12:08:301 cg1A-ctisvr Trace: #################################################

17:12:08:301 cg1A-ctisvr Session 4: 00 00 00 2e 00 00 00 26 00 00 00 0d 00 00 13 88 | .......&........

17:12:08:301 cg1A-ctisvr Session 4: 00 00 00 00 00 00 c3 54 01 00 00 00 00 06 05 31 | .......T.......1

17:12:08:301 cg1A-ctisvr Session 4: 30 30 30 00 05 09 34 37 34 38 33 36 34 38 00 31 | 000...47483648.1

17:12:08:301 cg1A-ctisvr Session 4: 01 00 01 02 00 01                               | ......          

 

There seems to be a protocol mismatch.  Finesse connects with version 16:

 

17:11:25:742 cg1A-ctisvr Session 4: Opening from client Finesse at (10.86.140.80:53613)

17:11:25:742 cg1A-ctisvr Trace: *** Created ClientCB 4 Finesse

17:11:25:742 cg1A-ctisvr Trace: CTIApplication::ProcessOpenRequest - sessionID 4 from Finesse at (10.86.140.80:53613), version 16

17:11:25:743 cg1A-ctisvr Trace: CTIApplication::OpenValidAgent from sessionID 4 (Finesse) - ACCEPTED (1 ms)

 

 

Is this the right CTI version in 11.5?