Created by: Dale Gantous on 13-02-2013 10:09:16 AM SET_AGENT_STATE_REQ and AGENT_STATE_EVENT both have a parameter called EventReasonCode, described as "A peripheral-specific code indicating the reason for the state change." A reason code can be set to be required for going to NOT_READY or LOGOUT state, and if set this way then when running the Agent Desktop you are prompted with a list of reason codes (e.g. default seems to be 1 to 4) to choose from. Also, if set, then calling SET_AGENT_STATE_REQ to go to NOT_READY or LOGOUT will be rejected if the EventReasonCode parameter is not from this list. Where is this list of reason codes defined/configured, and how is this list of valid values obtained programatically via the CTI Server Protocol? Thanks...
Subject: RE: New Message from Dale Gantous in CTI Server Protocol (GED-188) - CTI Se Replied by: David Lender on 13-02-2013 11:17:26 AM Reason codes are Configured using the UCCE Configuration Tool. There is no method to retrieve these values via CTI Server Protocol.
Subject: RE: New Message from Dale Gantous in CTI Server Protocol (GED-188) - CTI Se Replied by: David Lender on 13-02-2013 02:46:26 PM The CTIOS Agent Desktop does not use these values. The CTIOS Agent desktop retrieves the Reason Codes from the CTIOS Server registry in the downloadsettings event. Here is the configuration of ReasonCodes:
I am not sure what CAD does. The ICM Configured reason codes are for reporting only. Theres no mechanism in either CTI Server protocol or CTIOS to receive the reason codes from the ICM database.
Subject: RE: EventReasonCodes Replied by: Dale Gantous on 13-02-2013 02:36:45 PM Thanks, so how does the Agent Desktop obtain these values to populate its dialog box?
Subject: RE: EventReasonCodes Replied by: Dale Gantous on 14-02-2013 03:08:21 PM So, the Agent Desktop, running on a client machine, is directly reading the registry on the server machine where the CTI Server is running?
Subject: RE: EventReasonCodes Replied by: Dale Gantous on 14-02-2013 03:40:50 PM Thanks for the info.
Subject: RE: New Message from Dale Gantous in CTI Server Protocol (GED-188) - CTI Se Replied by: David Lender on 14-02-2013 03:20:26 PM No, the registry settings are sent by CTIOS Server to the client in an arguments array of the particular CTIOS Cil you are using. These settings are sent in response to a Session.RequestDesktopSettings method request from the CTIOS Cil based client application, in this case, the CTIOS Agent Desktop.
When sending a request to the API, there needs to be authentication, and the documents show that this password is stored on the XML as plain text, what options do we have to encrypt this password so it's not showing in plain text?
I am running UCCX 11.6 and would like to populate Custom Call Variables with data. Even if the call does not get routed to a UCCX Agent. Example.... I have a menu and Option 3 routes calls out of UCCX to a shared DN. When the caller selects this Option I ...
I"m having an issue where inbound calls rerouted back to PSTNT failling. Call flow:- ITSP—SIP—CUBE1—SIP—CUCM—CFWD All—SIP—CUBE1—ITSP. The PSTN calling Party receives a long pause, with no ring back, then receives a fast busy. &n...
We are developing our own phone device to support Device Management in Broadworks. And need to know how to add a new device profile type in the Broadworks Sandbox environment. System admin access needed. What procedure is used for this?
Hi there, Agent 1 makes call to Agent 2 and then Agent 2 Consult the call to Agent 3. This whole process of Consult call is working.The problem is coming for Transfer after the Consult.I am passing the original call ID(cal...