Versions Compared

Old Version 1

changes.mady.by.user CTI

Saved on

compared with

New Version 2

changes.mady.by.user CTI

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Target release

3.0.56

Target release date

07 Mar

Status

Status
colourGreenPurple
titleCompletedIn PROGRESS

Epic

Jira Legacy
serverJira
columnIdscolumnsissuekeykey,summary,issuetypetype,created,updated,duedatedue,assignee,reporter,priority,status,resolution
columnscolumnIdskeyissuekey,summary,typeissuetype,created,updated,dueduedate,assignee,reporter,priority,status,resolution
serverId131d473b-dd43-389a-9dac-6f501204581b
keyMCC-695779

Document status

Status
colourGreen
titleCompleted

Document owner

Haseeb TahirYulmas Gulzar

Developers

Jazeb SherazSharjeel Akram

QA

Haseeb TahirYulmas Gulzar

Release Summary

Feature

Description

PhoneCallActivity in No ANI Match

In case of no match, the CTI Connector will create the PhoneCallActivity on the RINGING Event without the association of the contact. It will then pop up the Phone Call Activity in front of the agent. We have to set the value to "phonecall" in the config.js file so that in case of no match, an anonymous activity (not linked to any CRM account/contact/lead) will be created.

We have fixed the Security Vulnerabilities

We have fixed the security vulnerabilities in JS CTI 3.0.6

Open Issues

Jira Legacy
serverJira
columnskey,summary,type,status
columnIdsissuekey,summary,issuetype,status
maximumIssues50
jqlQueryproject = MCC AND issuetype in (Bug, "Story Bug") AND status in (Open, In-Progress, QA-Ready, Re-opened, In-Review, In-QA) AND resolution = Unresolved AND affectedVersion in (releasedVersions(), JS_V2.1, JS_V2.2, JS_V3.0, JS_V3.0.1, JS_3.0.4, JS_3.0.5) AND labels = cti_board ORDER BY priority DESC, updated DESC
serverId131d473b-dd43-389a-9dac-6f501204581b

...

Release Test Highlights

Info

Tested with:

  • UCCE 12.6, UCCX 12.5.1

  • Microsoft Dynamics CRM (cloud) CIF 1.0 & 2.0

  • Microsoft Dynamics On-Premise soution (UCI & Classic UI)

  • Stand-alone CTI Toolbar

Testing Machine Hardware Specs:

...

Browser Compatibility

Browser

Version

Compatibility

Firefox

122Version 125.0.1 3 (3264-bit)

Status
colourGreen
titleCOMPATIBLE

Google Chrome

122Version 124.0.62616367.96 91 (Official Build) (6432-bit)

Status
colourGreen
titleCOMPATIBLE

Recommended Browser: FireFox Google Chrome

/wiki/spaces/MDWEB/pages/118129166

Release Limitations

  • Do not login to the same agent on different browsers or different machines.

  • It is mandatory to have at least 1 custom reason code for Not Ready and 1 custom reasons code for Logout.

  • Agent extension length is 6 digits on Login page.

  • If the user refreshes the browser at any time while login on to CTI Connector, Once the browser, comes back after refresh it will reconnect and resume the current state of the call. 

  • VPN connection/WebEx/TeamViewer is required to connect to the customer’s environment.

  • Remote access via RDP or similar is required to do installation and configuration of EF Server.

  • Administrative access to server machines is required to install EF Connector.

  • Supervisor can only drop an agent from the Brage In call. He cannot drop a CTI Route Point, IVR Port, or a caller.

  • "disableEndCallBtn" configuration will always remain "false" for CTI toolbar.

  • In HA process it will take at least 3-4 minutes to connect CTI with the secondary server.

  • It is mandatory to have a Primary and a Secondary Node/servers for HA.

  • The agent state after fail-over becomes Not Ready - Connection failure.

  • Queue stats feature is only available for CCE/PCCE

  • Queue Stats update time must be 20s and above for HA.

  • Other HA related Limitations are available here.