Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »


Target release

3.0.6

Target release date

Status

COMPLETED

Epic

MCC-779 - Getting issue details... STATUS

Document status

COMPLETED

Document owner

Yulmas Gulzar

Developers

Sharjeel Akram

QA

Yulmas Gulzar

Release Summary

Feature

Description

We have fixed the Security Vulnerabilities

We have fixed the security vulnerabilities in JS CTI 3.0.6

Open Issues

key summary type status
Refresh

key summary type status
Refresh

Release Test Highlights

Tested with:

  • UCCX 12.5.1

  • Microsoft Dynamics CRM (cloud) CIF 1.0

  • Stand-alone CTI Toolbar

Testing Machine Hardware Specs:

CPU

RAM

Hard Disk

4

8GB

60GB

Operating System:

Windows 2012 R2 standard (x64) 

Compatibility Matrix

Browser Compatibility

Browser

Version

Compatibility

Firefox

Version 125.0.3 (64-bit)

COMPATIBLE

Google Chrome

Version 124.0.6367.91 (Official Build) (32-bit)

COMPATIBLE

Recommended Browser: 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. 

  • No labels