Target release | 3.0.61 | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Target release date | 10 May | ||||||||||||
Status |
| ||||||||||||
Epic |
| ||||||||||||
Document status |
| ||||||||||||
Document owner | Yulmas Gulzar | ||||||||||||
Developers | Sharjeel AkramJazeb Sheraz | ||||||||||||
QA | Yulmas Gulzar |
Release Summary
...
Release Test Highlights
| Info |
|---|
Tested with:
|
Testing Machine Hardware Specs:
...
/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.