Blogs

Showing 1 result.

Forums

« Back to CTI Server Protocol Questions

SNAPSHOT_DEVICE_REQ UCCE 8

Combination View Flat View Tree View
Threads [ Previous | Next ]
SNAPSHOT_DEVICE_REQ UCCE 8
Answer
3/28/11 3:04 PM
I am now receiving an error to my SNAPSHOT_DEVICE_REQ request with UCCE 8 (GED-188 v14).
 
I get the following error my request:
 

09:44:22.156|x|||SENT: SNAPSHOT_DEVICE_REQ 00 00 00 05 00 00 13 88 00 4c 06 05 32 30 30 31 00
09:44:22.172|d|||SNAPSHOT_DEVICE_REQ
FIXED PART:
  InvokeID:5
  PeripheralID:5000
  SnapshotDeviceType:76
FLOATING PART:
  AGENT_INSTRUMENT_TAG:2001
 
09:44:22.203|x|||RECV: CONTROL_FAILURE_CONF 00 00 00 05 00 0c 00 00 27 99
09:44:22.203|d|||CONTROL_FAILURE_CONF
FIXED PART:
  InvokeID:5
  FailureCode:12
  PeripheralErrorCode:10137
FLOATING PART:

 
09:44:17.765|w|||The device identifier is invalid.
 
I tried with SnapshotDeviceType: -1 and I have the same result.
I also tried to set the ConfigMsgMask to 0x8 in my OPEN_REQ and I still have the same problem.
 
Can someone help me with this?
Flag

RE: SNAPSHOT_DEVICE_REQ UCCE 8
Answer
3/28/11 6:35 PM as a reply to Donald Hamel.
I get this error only when there is no agent login on the device. When an agent is login I get SNAPSHOT_CALL_CONF as expected. This is a new behaviour I did not see with version 9 of GED-188.

I also noticed that message SNAPSHOT_CALL_CONF has one 32 bits fixed field just after CalledPartyDisposition. This field is not documented.
Flag

RE: SNAPSHOT_DEVICE_REQ UCCE 8
Answer
12/12/12 8:55 PM as a reply to Donald Hamel.
Donald Hamel:
I also noticed that message SNAPSHOT_CALL_CONF has one 32 bits fixed field just after CalledPartyDisposition. This field is not documented.

 
I noticed that "surprise" field too (as it obviously messes up trying to parse the subsequent floating fields). It seems to be the PeripheralID based on the values I've seen in it. Why it is here I have no idea. Have not seen it in any other _CONF message. Also happens in Protocol V13.
Flag

Collateral


No files available