Avaya-Elite-4.2.0

Release Update:

- Extend DMCC protocol version support till 10.1.0.2:

Reason: Avaya has new version of AES with latest protocol versions
Requirement: update dmcc protocol to support version 10.1.0.2
Solution: updated dmcc service protocol
Ticket: https://virtualq.atlassian.net/browse/CON-142
Documentation: https://github.com/virtualq/Avaya-Elite-Release/wiki/4.1-AES-Configuration-Setup#supported-versions

- Updated .Net Framework version 4.5.2 -> 4.8:

Reason: Avaya has new version of AES with latest protocol versions with compiled dlls in 4.8
Requirement: in order to use latest dlls of avaya connector needed to move to .net framework 4.8
Solution: updated connector to .net framework 4.8
Ticket: https://virtualq.atlassian.net/browse/CON-142
Documentation: https://github.com/virtualq/Avaya-Elite-Release/wiki/2.-Prerequisites

- Adding patch CON-92 in latest release:

Reason: Had issue with agent count with last 4.1.1 release
Requirement: count agents from the labeles mentioned in agentreasons tag only
Solution: connector now count total agents based on the tags mentioned in agentreasons tag.
Ticket: https://virtualq.atlassian.net/browse/CON-92
Note: This patch is already running on clients. just including in latest here. no action needed.

Avaya-Elite-4.1.1

Release Update:

- EWT Parsing issue:

Reason: EWT and OWC values were getting merged
Requirement: extract EWT from merged value
Solution: pixk first 4 digits of merged value
Ticket: https://virtualq.atlassian.net/browse/CON-86
Documentation: https://github.com/virtualq/Avaya-Elite-Release/wiki/8.-How-to-Uninstall-Connector-Service

Avaya-Elite-4.1.0.0

Release Update:

- Avaya 8 Support:

Reason: Connector only supported uptill Avaya version 7.
Requirement: Add support for Avaya 8
Solution: Updated DMCC sdk in connector to version 8
Ticket: https://virtualq.atlassian.net/browse/CON-83
Documentation: https://github.com/virtualq/Avaya-Elite-Release/wiki/8.-How-to-Uninstall-Connector-Service

Avaya-Elite-4.0.0

Release Update:

- virtualQ.Net latest update:

Reason: A new version of virtualQ.Net was release.
Requirement: Integrate new latest virtualQ.Net to support TLS1.2
Solution: Now Connector has laest virtualQ.Net and supports TLS1.2.
Ticket: https://virtualq.atlassian.net/browse/CON-22?atlOrigin=eyJpIjoiNTg3NDEzNjc0NzMzNDUxNTg2ZjA1NDdlZmM5YTcwM2UiLCJwIjoiaiJ9

- Single Call for Lines States:

Reason: connector was making multiple calls to virtualQ to check multiple lines state.
Requirement: connector should make only one request at a time to check all lines state.
Solution: Connector now will only make one request to get all lines state.
Ticket: https://virtualq.atlassian.net/browse/CON-1?atlOrigin=eyJpIjoiMWY5ODMzM2U1MWY3NGE5OTkxZjAwMDU2YTBiYjk4YmIiLCJwIjoiaiJ9

- Separate the variable update from CM data read:

Reason: CM data read and variable update we combined.
Requirement: Separate the variable update from CM data read so both can be managed separately
Solution: now both CM data read and variable updates can be managed separately.
Configuration: https://github.com/virtualq/Avaya-Elite-Release/wiki/4.-Configuration#cm-configuration
Ticket: https://virtualq.atlassian.net/browse/CON-28?atlOrigin=eyJpIjoiZWY3NTAzMDkzZjA4NDFkYWIzZjIxYWZmNzVmMTI1ZmMiLCJwIjoiaiJ9

Avaya-Elite-3.9.9

Release Update:

- Change agents count reading from CM:

Reason: CM reading was not working with multiple pages.
Requirement: Read all CM skill data from first page
Solution: Now Connector will read CM skill agents data from first page only
Ticket: https://trello.com/c/cOo20pqm/120-change-agents-count-reading-from-cm

Avaya-Elite-3.9.8

Release Update:

- Call Volume when IsUCIDEnable is true:

Reason: callOffered was only sent on high vdn when isUCIDEnable is true
Requirement: callOffered should be sent on for all vdns on IsUCIDEnable is true
Solution: callOffered event will be sent for all vdns Normal+High on IsUCIDEnable is true
Ticket: https://trello.com/c/bsqUXTaT/115-call-volume-when-isucidenable-is-true

Avaya-Elite-3.9.7

Release Update:

- Monitor All Vdns:

Reason: Only high vdns were monitored but we need to monitor all vdns i.e, Normal+High
Requirement: Monitor all vdns configured in config.xml
Solution: Monitored all vdns configured in config.xml via DMCC protocol
Ticket: https://trello.com/c/5HofE3rD/103-monitor-all-vdns-with-dmcc

Avaya-Elite-3.9.6

Release Update:

- Connector Version Format Update:

Reason: needed the version number in new format
Requirement: Send version number in following format to virtualQ: "Avaya- QConnect v[version]"
Solution: Connector Version will be now as following format: "Avaya - QConnect v[version]"
Ticket: https://trello.com/c/27aHG55r/73-send-connector-version-to-virtualq
Docuementation: https://github.com/virtualq/Avaya-Elite-Release/wiki/1.1-Product-Version-Information#--from-virtualq-dashborad

Avaya-Elite-3.9.5

Release Updae

- Removed AgentList Transmission:

Reason: ServiceAgentsCount was needed to be sent instead of ServiceAgentList
Ticket: https://trello.com/c/dl1FmILG/88-sent-agent-count-instead-of-agent-list
Fix: Connector won't send ServiceAgentList to VirtualQ anymore.

Avaya-Elite-3.9.5

Removed Agent Name from being published to VQ API