Avaya-Elite-3.9.4

MuipleConfig for Agent and Idle Reasons
Minor Fixes

Avaya-Elite-3.9.2

Release Updae

- WTU changes removed:

Reason: call connected notification was not correct when calls are first transferred to agents
Fix: remove all WTU change set from code.

Avaya-Elite-3.9.1

Release Updates

- BugFix1:

Issue: multiple cm variable values were not getting update
Fix: multiple variable can be updated

- BugFix2:

Issue: Agent count was not correct
Reason: some agent were missed while reading data from CM session
Fix: all data is read and Agent count is correct now.

Avaya-Elite-3.9

Bulk AES Updation
Data-fetch from CM in a single session
CM Session Delay Parameters Available in Config.

Versions on 3.8 Onwards can be updated by copying the contents of the Patch.3.9.zip file in the Program Folder

Avaya-Elite-3.8.3

Separated reason codes for Available and Idle agents

Avaya-Elite-3.8.2

Fixed IdleAgentCount
Fixed AHT

Avaya-Elite-3.8.1

Release Updates:

• add version number in service description as well. See documentation: https://github.com/virtualq/Avaya-Elite-Release/wiki/1.1-Product-Version-Information#--from-service-description
• correct VurtualQ log name to VirtualQ
• patch version update

Note: its a very minor change. So only creating patch release for this.

Avaya-Elite-3.8

Release Updates

- Product Version Information:

Now customer will be able to see AvayaConnector version.
for more on how to see version info see: https://github.com/virtualq/Avaya-Elite-Release/wiki/1.1-Product-Version-Information

- Nuget Packages update:

• updated VituralQAPi version reference
• updated hint path for packages
• uploaded packages folder to remove local dependencies

- Project Installer Update:

Project installer is updated to Microsoft Visual Studio 2017 Installer Projects due to following reasons:

• easy to update
• native integration
• no sign up or registration is required
• very small size extension

3.7

With Transfer Idle Count

3.6

Added NewCallAnswered