Skip to main content
Skip table of contents

Release Notes


Target release

3.0.4

Target release date

Status

COMPLETED

Epic

MCC-599

Document status

COMPLETED

Document owner

Haseeb Tahir

Developers

Jazeb Sheraz

QA

Haseeb Tahir

Release Summary

This release is compatible with the Channel Integration Framework 2.0 on Microsoft Dynamics CRM, a cloud-based solution.

Open Issues

Key Summary T Status
Authenticate to retrieve your issues

Key Summary T Status
Authenticate to retrieve your issues

Release Tested Highlights

Tested with:

  • UCCE 12.6, UCCX 12.5.1

  • Microsoft Dynamics  CRM (cloud) CIF 1.0 & 2.0

  • Stand-alone CTI Toolbar

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

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

122.0.1 (32-bit)

COMPATIBLE

Google Chrome

122.0.6261.95 (Official Build) (64-bit)

COMPATIBLE

Recommended Browser: FireFox

Microsoft Dynamics 365 CRM Compatibility

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

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.