...
| Excerpt |
|---|
This release includes
|
...
Jira Legacy server project.expertflow.com JIRA columns key,summary,type,priority maximumIssues 50 jqlQuery project in (EMR) and "Epic Link" in (EMR-2779) AND issuetype in (Bug) AND resolution = Unresolved ORDER BY priority DESC serverId 131d473b-dd43-389a-9dac-6f501204581b
Failover/HA Issues
Jira Legacy server project.expertflow.com JIRA columns key,summary,type,priority maximumIssues 50 jqlQuery project in (EMR) and labels in (failover, Failover) AND issuetype in (Bug) AND resolution = Unresolved ORDER BY priority DESC serverId 131d473b-dd43-389a-9dac-6f501204581b
Other Issues
The following issues are still open in this release.
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Issue key
...
Summary
...
Priority
...
EMR-2659
...
Archived calls are visible on the VRS UI
...
Critical
...
EMR-2657
...
When a new EM ext is configured, restart the VRS Recorder app to capture its recording
...
Critical
...
EMR-2650
...
During the call, if failover happens then that call is not saved
...
Major
...
EMR-2661
...
When the primary machine is down no calls are being archived
...
Major
...
EMR-2556
...
When a call ends due to a network glitch or an unknown reason then that call is not recorded
...
Major
...
In the case of the Jabber phone Transfer call scenario, sometimes call legs get missed. This is an intermittent issue.
Has a frequency of about 2 times in 10 attempts
...
EMR-2669
...
The calls are not appearing as per the proper order of the conf call scenario
...
Minor
...
EMR-2668
...
The recording legs are being displayed under two separate legs instead of one
...
Minor
...
EMR-2520
...
On login of VRS with the right credentials, the error message appears on the screen but after a few seconds user login successfully.
...
Minor
...
EMR-2652
...
When a server goes down after a call, during the job then the recording is not saved
...
Minor
...
EMR-2660
...
There is no way on the front end to distinguish between archived and normal calls
...
Minor
...
EMR-2648
...
[failover] press F5 to get the searched results
...
Minor
...
EMR-2666
...
[EM extensions] In the case of Consult transfer call, the consult leg is not always recorded
...
Minor
...
EMR-2667
...
[Agent-2-Agent] Consult call leg is not always recorded in agent-2-agent calls
...
Minor
...
EMR-2670
...
The consult transfer part of the conf call is being grouped separately as part of the second calls
...
Minor
...
EMR-2671
...
Incorrect Agent ID is being displayed for the conf call leg
...
Minor
...
EMR-2618
...
[Agent-2-Agent] All call legs of an internal call are accumulated to the single call leg
...
Minor
...
EMR-2672
...
The conf call legs are shown twice for every conf call
...
Minor
...
EMR-2625
...
[Agent-2-Agent] Missed recording on Direct-Transfer on EM enabled extensions
...
Minor
...
EMR-2673
...
Sometimes some call legs are skipped in the case of a conference call. For example, if there should be 5 legs, only 4 legs are visible
...
Minor
...
EMR-2626
...
[Agent-2-Agent] In the case of EM, hard phone hold/resume is not working
...
Minor
...
EMR-2622
...
In the case of Agent to Agent, Direct Transfer call the agent info is missing for the second leg
...
Minor
...
EMR-2624
...
Agent to Agent Hold/resume is only saving a single call leg (for EM)
...
Minor
...
EMR-2553
...
The audio player continues to play the call even after logout
...
Minor
...
EMR-2573
...
There is a lot of noise when a call is done from Agent to Agent
...
Minor
...
EMR-2549
...
Need to remove AM/PM from the time selection drop-down as well
...
Minor
...
EMR-2557
...
Can't search recording based on the Agent Name
...
Minor
...
EMR-2560
...
After the call end, the call is taking some time to be displayed on VRS
...
Minor
...
EMR-2572
...
In the case of consult transfer scenario in UCCE sometimes an extra leg appears along with the call
...
Minor
...
EMR-2728
...
EMR-2733
...
Fixed Issues
| Issue | Summary |
|---|---|
| Consult Call Issue | It should be noted that Consult call Issue has been resolved for the Customer, Agent, and Agent. It Should be noted that this issue still exists for EM phones. It works fine for IP phones and Hard-phones. It is working for Inbound calls only. |
| Agent Masking | The number masking issue has been fixed. |
| Agent to Agent (Internal Call Support) | Now VRS supports Agent-to- Agent (internal calls). For now, it only supports simple agent to agent call No hold/resume, conference call, consult transfer, or Direct Transfer is supported. |
| Extension Mobility Support | Extension Mobility is now supported. Note that for Agent to Agent EM the above is valid as well. For Agent customer Inbound, supported
For Agent customer Inbound, not-supported
For OB call Agent-Agent supported
For OB call Agent-Agent not-supported
For OB call Agent-customer supported
For OB call Agent-customer not-supported
|
| Hard phones Support | Hard phones are now compatible as well. Hard phone details are mentioned in the compatibility guide. For Agent customer Inbound, supported
For Agent customer Inbound, not-supported
For OB call Agent-Agent supported
For OB call Agent-Agent not-supported
For OB call Agent-customer supported
For OB call Agent-customer not-supported
|
| UI issues |
|
| Finesse Gadget |
|
Consult/Conference Call Open Issues
Jira Legacy server project.expertflow.com JIRA columns key,summary,type,priority maximumIssues 50 jqlQuery project in (EMR) and "Epic Link" in (EMR-2779) AND issuetype in (Bug) AND resolution = Unresolved ORDER BY priority DESC serverId 131d473b-dd43-389a-9dac-6f501204581b
Failover/HA Issues
Jira Legacy server project.expertflow.com JIRA columns key,summary,type,priority maximumIssues 50 jqlQuery project in (EMR) and labels in (failover, Failover) AND issuetype in (Bug) AND resolution = Unresolved ORDER BY priority DESC serverId 131d473b-dd43-389a-9dac-6f501204581b
Other Issues
The following issues are still open in this release.
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|