Avaya-AACC-Multicast-1.2.0

Release Update

- Send AHT to virtualQ:

Reason: connector does not send AHT to virtualQ
Requirement: AHT needs to be fetched from AACC and sent to virtualQ
Solution: Get TalkTime, PostCallProcessingTime and CallsAnswered from AACC db and calculate AHT based on it
Ticket: https://virtualq.atlassian.net/browse/CON-81
Documentation: https://virtualq.atlassian.net/wiki/spaces/AE/pages/220561463/Avaya+AACC+Connector+-+Technical+Documentation

Avaya-AACC-Multicast-1.1.0

Release Update

- Update virtualQ.Net SDK:

Reason: virtualQ.Net SDK was not ablr to support latest 1.2 version of TLS for virtualQ communication.
Requirement: Ad support for TLS 1.2
Solution: Connector will now support TLS 1.2 with virtualQ.NET latest version: 1.1.1
Ticket: https://virtualq.atlassian.net/jira/software/projects/CON/boards/11?selectedIssue=CON-25

- Retain Old EWT:

Reason: Avaya Send 0 instead of actual EWT unless updated. so EWT quickly changed to 0
Requirement: Retain old value until a new value .ther than 0 is updated or after one hour change EWT to 0
Solution: Retain old value until a new value other than 0 is updated or after one hour change EWT to 0
Ticket: https://virtualq.atlassian.net/jira/software/projects/CON/boards/11?selectedIssue=CON-26

Avaya-AACC-Multicast-1.0.0

Release Update

- Multicast data reading from Avaya AACC:

Reason: Get data from Avaya AACC
Requirement: We needed to monitor Avaya AACC's multicast port to get CTI data.
Solution: Monitored all CTI data from multicast port for reporting purpose.

- Sending data to virtualQ:

Reason: Transmit data to virtualQ
Requirement: We needed to send CTI data to virtualQ from connector.
Solution: Sent data from Avaya-AACC-Multicast-Connector to virtualQ via VQ API.

- Sending Events to virtualQ:

Reason: Transmit events to virtualQ
Requirement: We needed to send CTI events to virtualQ from connector.
Solution: Sent CTI event for lineup and callOffered from Avaya-AACC-Multicast-Connector to virtualQ via VQ API.