Marjie Ennis Floyd http://developer.cisco.com/web/ged-125/wiki?p_p_auth=Hi33QpMw&p_p_id=36&p_p_lifecycle=0&p_r_p_185834411_nodeId=803275&p_r_p_185834411_title=&Wiki+Home 2012-09-25T13:10:00Z 2012-09-25T13:10:00Z

=== This is the home page for the Contact Center Enterprise/Hosted/ICM IVR PG (GED-125) Wiki space. ===

Marjie Ennis Floyd 2012-09-25T13:10:00Z David Nguyen http://developer.cisco.com/web/ged-125/wiki?p_p_auth=Hi33QpMw&p_p_id=36&p_p_lifecycle=0&p_r_p_185834411_nodeId=803275&p_r_p_185834411_title=&Frequently+Asked+Questions 2010-05-02T02:19:56Z 2010-05-02T02:19:56Z

<<TableOfContents>> === How should my application read binary data over a TCP/IP socket? === Your application should perform an 8 byte read... then go back and read the rest of the message based on length of message from header. === How many bytes of data are available in the standard 10 call variables? === For CTI Server interface, the "40 byte call variables" actually means 39 character bytes and a null terminator. This is contrasted with the ICM VRU interface where a 40 byte call variable means 40 bytes plus terminator. Beginning with ICM version 7.1(1) and later, defect CSCsb61534 was fixed to allow CTI Server to handle 40 bytes plus null terminator. CTIOS has not yet been updated with this fix and the C API will not handle 40 bytes plus null terminator. Only those applications writing their own socket level messaging will be able to handle 40 bytes plus null terminator. If you specify CTI Server protocol version 8 or earlier, only 39 bytes plus null terminator will be used. There is an Engineering Special ES28 available against 7.1(3) to fix an issue where 40 bytes plus null terminator is delivered causing the CAPI not to function correctly. === How do I perform authentication when I open a session (security)? === While the protocol provides for it, session authentication is not currently implemented by the CTI Server. === What happens if I specify an open request with extension only? === AgentID is returned in the open confirmation response if agent logged into hardphone. (non-IPCC implementation only). === Sometimes I receive events in a different order than I expected. Why is that? === CTI Server provides Asynchronous Event ordering. This means the events arrive in no particular order. For example, if you send a make call request, your application could get the begin call event before receiving the make call confirmation event.

David Nguyen 2010-05-02T02:19:56Z