http://developer.cisco.com/c/message_boards/find_category?p_l_id=&mbCategoryId=1053310 2013-06-20T04:39:41Z 2013-06-20T04:39:41Z David Lender http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=15760063 2013-05-31T14:20:34Z 2013-05-31T14:20:34Z

As you noted, CTIOS doesn’t give you IVR or CVP events, only CTI Events via Callmanager. Regarding membership, the point is that if there is an issue at a customer site and there is a custom CTI Server or CTIOS app installed, the TAC will need to work with Developer Services to determine if any issue is with the custom app or not. This requires a CDN membership. For information on joining CDN, see http://developer.cisco.com/web/join-the-network

David Lender 2013-05-31T14:20:34Z Gerard O'Rourke http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=15754583 2013-05-31T08:45:18Z 2013-05-31T08:45:18Z

Note: to add to above. I did set the below registry value for CTI OS server [HKLM\Cisco Systems\CTIOS\Server\CallObject\MinimizeEventArgs = 0].   [color=#1f497d][url=http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cust_contact/contact_center/ctios/ctios9_0/developer/guide/UCCE_BK_C3995718_00_cti-os-developers-guide-ucce_chapter_0110.html]http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cust_contact/contact_center/ctios/ctios9_0/developer/guide/UCCE_BK_C3995718_00_cti-os-developers-guide-ucce_chapter_0110.html[/url][/color] [color=#1f497d]Gerry [/color]

Gerard O'Rourke 2013-05-31T08:45:18Z Gerard O'Rourke http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=15754557 2013-05-31T08:43:39Z 2013-05-31T08:43:39Z

David, We would just like to know the details / costs in case we do need to build a CTI monior client. We need to capture a call hangup during a call transfer from CVP. CVP Comprehensive mode does not support this today (a pity). i.e. ICM script returns Label to CVP. CVP routes the call, but we have no way to know if / when the call terminates and we need this for a particular bespoke app / fuctionality. Looking at the CTI logs below - you can see a call hangup from CVP (note the TrunkGroup=100) , which means this is the incoming leg of a call into CVP. This is the event we need to "catch". The issue we are having is that we were not able to receieve these Call events on a CTI OS Monitor client. The CTI OS logs also do not seems to log these events. Do you know if this is by design or if there is any way to get these event types from the CTI OS server (which would be the perferred route)? Gerry   -- log file from CTI Server showing call termination event for CVP inbound leg--- 15:20:16:383 cg1A-ctisvr Trace: CALL_DATA_UPDATE: CID=35.(s) Dest=35.(s) Active=N Periph=5001 ECCsize=270 15:20:16:383 cg1A-ctisvr Trace:  CallType=1(ACD_IN) CPDisposition=0(INVALID) TrunkGroup=100  15:20:16:383 cg1A-ctisvr Trace:  RouterCallKey=150564 30650114 CampaignID=-1 QueryRuleID=-1 15:20:16:383 cg1A-ctisvr Trace:  DNIS: ANI: CED: Dialed=11100 15:20:16:383 cg1A-ctisvr Trace:  UserToUser= Wrapup= 15:20:16:383 cg1A-ctisvr Trace:  CustPhone#= CustAccount#= 15:20:16:383 cg1A-ctisvr Trace:  PV1=INSPERIX-CS:5000 PV2=RouterCallDay:150564 PV3=RouterCallKey:30650114 PV4=RouterCallKeySeqNum:0 PV5= 15:20:16:383 cg1A-ctisvr Trace:  PV6= PV7= PV8=BT_Support:BT_Support_Precision PV9= PV10= 15:20:16:383 cg1A-ctisvr Trace:  SrcAgentExt=(CS_CONNECT) DestAgentExt=(CS_CONNECT) 15:20:16:384 cg1A-ctisvr Trace:   15:20:16:384 cg1A-ctisvr Trace: CALL TERMINATED: CallID=35.(s) Periph=5001

Gerard O'Rourke 2013-05-31T08:43:39Z David Lender http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=15729221 2013-05-30T17:25:34Z 2013-05-30T17:25:34Z

The article expired quite a while back. We are editing the getting started page to reflect this. The membership requirement still exists but there is no official documentation other than the statement on the Getting Started page. Do you have any specific questions about the requirement? I can refer them to the Product Manager.

David Lender 2013-05-30T17:25:34Z Gerard O'Rourke http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=15727593 2013-05-30T16:39:26Z 2013-05-30T16:39:26Z

David, Thanks for response. Any ideas why the getting Started Page has an invalid link for Contact Center Developer Support Services requirement? [url=http://developer.cisco.com/web/ctisp/getStarted]http://developer.cisco.com/web/ctisp/getStarted[/url] "Note that all customers and partners wishing to deploy custom CTI integrations using CTI Server Protocol are required to have a valid Developer Services contract. For furtner information see [url=http://www.imakenews.com/ciscotcc/e_article000724599.cfm?x=b8LlDbK,b4wfw2pw][color=#2970a6]Contact Center Developer Support Services requirement.[/color][/url] " Gerry

Gerard O'Rourke 2013-05-30T16:39:26Z David Lender http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=15727137 2013-05-30T16:09:40Z 2013-05-30T16:09:40Z

Gerry, Cisco does not provide sample source code for CTI Server applications and does not provide the source for CTITEST. Only the protocol specification is provided. David

David Lender 2013-05-30T16:09:40Z Gerard O'Rourke http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=15725012 2013-05-30T15:16:18Z 2013-05-30T15:16:18Z

Hi, The CTI OS client installer comes with the source code for a number of sample client for CTI OS. It even includes with a tool CTITEST.exe which is a CTI client. Is there equvalent sample source code samples released for a CTI monitor client /  CTI Bridge Application? Gerry

Gerard O'Rourke 2013-05-30T15:16:18Z Andrey Fandeev http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=15409797 2013-05-20T09:03:43Z 2013-05-20T09:03:43Z

The CTI Server Simulator is part of CTIOS Client SDK installation. You can find it in "C:\Program Files\Cisco Systems\CTIOS Client\CTIOS Tools" folder after CTIOS SDK installation. This CTI Server simulator works with CTI protool (GED-188) version 8.0.

Andrey Fandeev 2013-05-20T09:03:43Z David Lender http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=14374063 2013-04-17T20:30:28Z 2013-04-17T20:30:28Z

I have not heard of CtiSim. There is no simulator for CTI Server available for download.

David Lender 2013-04-17T20:30:28Z David Seeba http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=14363630 2013-04-17T18:53:52Z 2013-04-17T18:53:52Z

I've seen some references to a CtiSim executable that simulates the CTI Protocol. This would allow me to get started on CTI without having to interface directly with UCCE (at least until we have some basic functionality). I've only seen references to this in older documentation. Is this still available? If so, where would one find it to download? Thanks!

David Seeba 2013-04-17T18:53:52Z David Lender http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=14010508 2013-04-08T19:04:25Z 2013-04-08T19:04:25Z

I do not know how you log an agent into the hardphone unless you have the IPPhoneControlService from Custom Engineering. UCCE does not support logging in an agent from a hardphone. If it is a TDM ACD then the SYSTEM events are not generated. If its extension mobility and you are just logging into an extension, I do not know what events you can expect when the phone is logged in or out via Extension mobility I will have to escalate that question.

David Lender 2013-04-08T19:04:25Z Petrus Buiquy http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=14004946 2013-04-08T18:27:59Z 2013-04-08T18:27:59Z

Yes I log in and out of the hard phone and observe what we see in the log. I did not use CTI at all. We just want to see what kind of events would be generated if agent logs in/out of the hard phone.

Petrus Buiquy 2013-04-08T18:27:59Z David Lender http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=13999596 2013-04-08T17:52:30Z 2013-04-08T17:52:30Z

When you say you log out of the phone do you mean with Extension Mobility? Logging an agent out using CTI Server to set Agent State to LOGOUT should not result in a System Event with Id = SYS_INSTRUMENT_OUT_OF_SERVICE. I believe logging out of the hardphone using Extension Mobility will. The other time you will get SYS_INSTRUMENT_BACK_IN_SERVICE is after the hardphone phone has been reset.

David Lender 2013-04-08T17:52:30Z David Lender http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=14000505 2013-04-08T17:11:13Z 2013-04-08T17:11:13Z

Is this for UCCE or a TDM ACD? I suggest you open a Service Request and attach a full set of logs (JGW or PIM, OPC, CTI Server) so that I can escalate it as I do not know why you are not receiving the SYS_INSTRUMENT_BACK_IN_SERVICE SystemEventID.

David Lender 2013-04-08T17:11:13Z David Lender http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=13993121 2013-04-08T14:21:30Z 2013-04-08T14:21:30Z

Yes you can use protocol 6 with ICM 8.5 You specify the version you want to use in the OPEN_REQ.

David Lender 2013-04-08T14:21:30Z Goran Selthofer http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=13958252 2013-04-06T13:53:31Z 2013-04-06T13:53:31Z

David, what about Protocol 6? Is that supported with ICM 8.5 ? or the same as for 7 stands for 6 as well ?

Goran Selthofer 2013-04-06T13:53:31Z David Lender http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=12877140 2013-03-11T15:40:58Z 2013-03-11T15:40:58Z

I refer you to the CTI Server Protocol guide section on Call Identification which states A valid CTI Server application can make no assumption about the content or format of a ConnectionDeviceID. CTI Server uses the CSTA method of identifying calls. A numeric ConnectionCallID identifies a call; each connection of a device to that call is identified by a ConnectionDeviceID string and an enumerated ConnectionDeviceIDType value (see Figure 3-3). All call related messages identify the ConnectionCallID as well as the ConnectionDeviceIDType and ConnectionDeviceID of the call connection that is the subject of the event. A ConnectionDeviceID uniquely identifies a call connection. However, it cannot directly identify the connected device; use other event message fields for that purpose. In some cases, the ConnectionDeviceID may simply be the ID of the connected device, the connected deviceID with additional identifying data included, or a string that does not contain the deviceID at all. A valid CTI Server application can make no assumption about the content or format of a ConnectionDeviceID. Occasionally, both the ConnectionDeviceID and the numeric ConnectionCallID are required in order to properly identify the subject call. This occurs when the ACD uses the ConnectionCallID value from an ACD call as the ConnectionCallID value for any related consultative calls. This poses two particularly significant requirements for applications: they must be able to keep track of two calls with the same numeric ConnectionCallID value, and they must be able to decide which of the two calls is being referenced by any given call event message. These requirements are relatively easy to implement by keeping track of the ConnectionDeviceIDs associated with each call. The call that has a ConnectionDeviceID that matches the ConnectionDeviceID provided in the call event message is the call that is the subject of the event. The only difficult case is determining which call is the subject when a new call connection is created. For this case, the following rule applies: When more than one call with the same ConnectionCallID value exists, the connection being created by a CALL_ESTABLISHED_ EVENT shall apply to the call that does not yet have a destination connection established

David Lender 2013-03-11T15:40:58Z Dale Gantous http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=12876100 2013-03-11T14:56:48Z 2013-03-11T14:56:48Z

You only specify a ConnectionDeviceID if you start a monitor for a call. If you want to monitor a device, you specify a DeviceID.   It would be highly useful to know which ConnectionDeviceIDs in call events refer to the device being monitored (as opposed to the other devices involved in the call). This is what I'm trying to figure out. Any ideas?

Dale Gantous 2013-03-11T14:56:48Z David Lender http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=12873622 2013-03-11T14:41:58Z 2013-03-11T14:41:58Z

You can specify the ConnectionDeviceID in the MONITOR_START_REQ. I know of no way to determine which connectiondeviceid refers to the monitored device.

David Lender 2013-03-11T14:41:58Z Dale Gantous http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=12811129 2013-03-08T21:27:59Z 2013-03-08T21:27:59Z

When creating a peripheral monitor on a device, how can one determine the ConnectionDeviceID (and ConnectionDeviceIDType) that refers to the device being monitored?   According to the documentation, the ConnectionDeviceID is not necessarily the same as the DeviceID.   We need to know which ConnectionDeviceID refers to the monitored device (as opposed to other devices involved in the call) in order to make sense of all the call messages being monitored for the particular device.   I was hoping one of the SNAPSHOT_ or QUERY_ calls would give us this information, but I don't see it.   Thanks for any help...

Dale Gantous 2013-03-08T21:27:59Z