Release Notes
Target release | 3.0.5 |
|---|---|
Target release date |
|
Status | COMPLETED |
Epic | MCC-695 |
Document status | COMPLETED |
Document owner | Haseeb Tahir |
Developers | Jazeb Sheraz |
QA | Haseeb Tahir |
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. |
Open Issues
Release Test Highlights
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:
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.96 (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.