cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
182
Views
0
Helpful
0
Replies

UCCE CTI server sends FAILURE_CONF to OPEN_REQ

gerkovger
Level 1
Level 1

Hi!

I am trying to reach a sandbox UCCE CTI server, using protocol version 24.

Most of the times the session gets open after a few OPEN_REQ messages: OPEN_CONF arrives with valid fields.

Sometimes, however, I don't get an OPEN_CONF, but a FAILURE_CONF arrives with the status: E_CTI_INVALID_MESSAGE_LENGTH. This behavior persists for a couple of hours and then everything goes back to normal.

I checked the logs on the sandbox's Diagnostic Framework Portico and realized that the invalid field the FAILURE_CONF refers to comes from an OPEN_CONF message, which for me is puzzling, because the client did not send an OPEN_CONF message, obviously.

How can the client get a failure message with a faulty field in a message the server sends back to the client?

The log with the FAILURE_CONF (from the DFP):

14:59:15:310 cg1a-ctisvr Trace: *** Created ClientCB 11 <agent_name>
14:59:15:310 cg1a-ctisvr Trace: CTIApplication::ProcessOpenRequest - sessionID 11 from <agent_name> at (192.168.x.y:32798), version 22
14:59:15:310 cg1a-ctisvr Trace: CTIApplication::OpenValidAgent from sessionID 11 (<agent_name>) - ACCEPTED (0 ms)
14:59:45:647 cg1a-ctisvr Trace: Decode length error: element "PGStatus", FieldLength -1, MaxBytes 0
14:59:45:647 cg1a-ctisvr Invalid Enterprise CTI message received from session: 11 (client <agent_name> at (192.168.x.y:32798)), type: OPEN_CONF, error: E_CTI_INVALID_MESSAGE_LENGTH, field: PGStatus.
14:59:45:647 cg1a-ctisvr Trace: #################################################
14:59:45:647 cg1a-ctisvr Trace: ###!!!Invalid Message INGORE and CONTINUE !!!###
14:59:45:647 cg1a-ctisvr Trace: #################################################
14:59:45:647 cg1a-ctisvr Session 11: 00 00 00 0c 00 00 00 04 00 00 00 05 00 00 00 01 | ................
14:59:45:647 cg1a-ctisvr Session 11: 00 00 00 0c | ....
15:00:00:379 cg1a-ctisvr ICM central controller time adjusted by: -1 second(s) to: 14:00:00 UTC.
15:00:00:379 cg1a-ctisvr Trace: CTIApplication::ProcessTimeNotificationEvent - Time=14:00:00 UTC NewHalfHour=TRUE
15:00:00:927 cg1a-ctisvr CTIServer: ACTIVE, 3, CTI client connection(s), 0 call(s) in progress, PG status: NORMAL.
15:00:00:927 cg1a-ctisvr Period connection(s): 1 Period call(s): 0 (0.00 calls/sec)
15:00:00:927 cg1a-ctisvr Period EnterpriseCTI traffic: 4340 messages (2.41 msgs/sec)
15:00:00:927 cg1a-ctisvr 270044 bytes / 1800 seconds (150.02 bytes/sec)
15:00:00:927 cg1a-ctisvr 1801 heartbeats (1.00 hb/sec)
15:00:00:927 cg1a-ctisvr 0.04ms average queue time/msg
15:00:00:927 cg1a-ctisvr 0.02ms average CPU time/msg (0.00% busy)
15:00:45:657 cg1a-ctisvr Trace: Decode length error: element "PGStatus", FieldLength -1, MaxBytes 0
15:00:45:657 cg1a-ctisvr Invalid Enterprise CTI message received from session: 11 (client <agent_name> at (192.168.x.y:32798)), type: OPEN_CONF, error: E_CTI_INVALID_MESSAGE_LENGTH, field: PGStatus.
15:00:45:657 cg1a-ctisvr Trace: #################################################
15:00:45:657 cg1a-ctisvr Trace: ###!!!Invalid Message INGORE and CONTINUE !!!###
15:00:45:657 cg1a-ctisvr Trace: #################################################
15:00:45:657 cg1a-ctisvr Session 11: 00 00 00 0c 00 00 00 04 00 00 00 05 00 00 00 03 | ................
15:00:45:657 cg1a-ctisvr Session 11: 00 00 00 0c | ....

0 Replies 0