/mcpOnly the conference controller (the agent who initiates the conference) can add parties to that conference. For example, Agent 1 is on a call with a customer. Agent 1 consults with Agent 2 and then conferences Agent 2 into the call. Agent 2 then consults with Agent 3. If Agent 2 tries to add Agent 3 to the conference, the request fails. Note Finesse maintains a copy of the call variables (including call peripheral variables and ECC variables) for each call in the system. When Unified CCE or Unified CCX sets the call variables to values that are not NULL (through CTI events, such as CALL_DATA_UPDATE_EVENT), the call variables maintained by Finesse are updated with these values. In this way, Finesse ensures that a client always receives the latest data for call variables sent by Unified CCE/Unified CCX. Because an empty string is considered a valid value, when call values are set to empty strings, Finesse updates its version of the same call variables to empty strings and then updates the clients. An agent or supervisor who signs in after being on an active conference call with other devices (which are not associated with any other agent or supervisor) may experience unpredictable behavior with the Finesse Desktop due to incorrect Dialog notification payloads. These limitations also encompass failover scenarios where failover occurs while the agent or supervisor is participating in a conference call. For example, an agent is on a conference call when the Finesse server fails. When that agent is redirected to the other Finesse server, that agent could see unpredictable behavior on the desktop. Examples of unpredictable behavior include, but are not limited to, the following: • The desktop does not reflect all participants in a conference call. • The desktop does not reflect that the signed-in agent or supervisor is in an active call. • Dialog updates contain inconsistent payloads. Despite these caveats, users may continue to perform usual operations on their phones. Desktop behavior will return to usual after the agent or supervisor drops off the conference call. Note https://<FQDN>/finesse/api/Dialog/<dialogId> URI: https://finesse1.xyz.com/finesse/api/Dialog/54321 Example URI: Agents can use this API. An agent must be a participant in the dialog and the agent's extension must match the targetMediaAddress. Security Constraints: PUT HTTP Method: Application/XML Content Type: XML Input/Output Format: Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 94 Cisco Finesse Desktop APIs Dialog—Make a Consult Call Request