VQConnector-VCC-1.7.2

Release Update:

- adding customerid and customerinfo in lineup:

Reason: on voxtron agent application customerid and customer info was needed to be shown
Requirement: show these values on agent application on voxtron side
Solution: use customer id and customer info coming from lineup in creating BO object
Ticket: https://virtualq.atlassian.net/browse/CON-144

VQConnector-VCC-1.7.1

Release Update:

- pass info from widget 2.0:

Reason: new widget 2.0 pass custome info
Requirement: this info should go to voxtron side via connector
Solution: add mapping for infomation coming from widget 2.0
Ticket: https://virtualq.atlassian.net/browse/CON-143

VQConnector-VCC-1.7.0

Release Update:

- 64 bit process:

Reason: 32 bit connectr faced issue with memory limit of 1.5 GB
Requirement: Connector should be able to use memory to handle high call volume
Solution: Add support for 64 bit process build
Ticket: https://virtualq.atlassian.net/browse/CON-113
Documentation: https://virtualq.atlassian.net/wiki/spaces/AE/pages/2383478785/Voxtron+Latest#OutOfMemory-Exception

- Duplicate and no callback issue:

Reason: there were some issues on last duplicate callback issue fix and it didn't worked for all cases
Requirement: fix all cases of duplicate and no callback issue
Solution: fixed duplicate and no callback issues for deferred calls. A new setting is added to count for correct deferred state update on virtualQ dashboard.
Ticket: https://virtualq.atlassian.net/browse/CON-69

- Release any stuck agents:

Reason: sometime due to memory exception agent that were on calls were stuck in that state.
Requirement: need to release stuck agents
Solution: all the last active calls are store in db and then pciked up at the start of next start and if there is any agent stuck on any of these calls its released. this was first release as patch but now its part of current build
Ticket: https://virtualq.atlassian.net/browse/CON-127

Patches added:

Followig are some patches given after 1.6.0 release time to time. all these are now part of latest build.
Increase max conenction to 200 for IVR TCP server: https://virtualq.atlassian.net/browse/CON-114
read autoupdate configurations from connector page instead of notes: https://virtualq.atlassian.net/browse/CON-130
stop EWT trasnmission back to virtualQ: https://virtualq.atlassian.net/browse/CON-132
remove delay from caller connected notification from vq to voxtron: https://virtualq.atlassian.net/browse/CON-112
make virtualQ api address configurable: https://virtualq.atlassian.net/browse/CON-53

VQConnector-VCC-1.6.0

Release Update:

- VCC19 Support:

Reason: Connector only supported vcc17 in production.
Requirement: VCC19 is now avaiable and connector should be able to work with it.
Solution: Add support for vcc19 in connector.
Ticket: https://virtualq.atlassian.net/browse/CON-39
Documentation: https://virtualq.atlassian.net/wiki/spaces/AE/pages/2019852289/How+to+connect+WDS+with+QConnect
Note: From now on WDS will be the standard way to connect voxtron. And Sspport for Monitoring SDK is removed from connector. So all old customer will also be moved to this new setup when doing upgrade.

- EWT and EUT communication to voxtron:

Reason: Whenever a caller linesup on virtualQ it is assigned an EWT. And it was not avaiable on voxtron side.
Requirement: The EWT assigned to caller by virtualQ is needed in voxtron for announcing customer the time when they will be contacted.
Solution: Send EWT and EUT to voxtron via connector. EWt and EUT is now sent in respone to verifycaller comand from voxtron IVR.
Docuementation: https://virtualq.atlassian.net/wiki/spaces/AE/pages/220495937/Voxtron+Connector+-+Technical+Documentation#VoxtronConnector-TechnicalDocumentation-2.VerifyCallerresponse
Ticket: https://virtualq.atlassian.net/browse/CON-77

VQConnector-VCC-1.5.9 patch release

Release Update:

VQConnector-VCC-1.5.9 is a patch release of release VQConnector-VCC-1.5.8. it can only be used where 1.5.8 is deloyed. This release is invalid for deployments updated to release 1.6.0.

- Stop EWT waiter update:

Reason: waiter EWT was being updated on virtualq side. this messed up with callback times
Requirement: stop the EWT update from connector
Solution: remvoed EWT update from virtualQ API update
Ticket: https://virtualq.atlassian.net/browse/CON-123

- EWT and EUT communication to voxtron:

Reason: Whenever a caller linesup on virtualQ it is assigned an EWT. And it was not avaiable on voxtron side.
Requirement: The EWT assigned to caller by virtualQ is needed in voxtron for announcing customer the time when they will be contacted.
Solution: Send EWT and EUT to voxtron via connector. EWt and EUT is now sent in respone to verifycaller comand from voxtron IVR.
Docuementation: https://virtualq.atlassian.net/wiki/spaces/AE/pages/220495937/Voxtron+Connector+-+Technical+Documentation#VoxtronConnector-TechnicalDocumentation-2.VerifyCallerresponse
Ticket: https://virtualq.atlassian.net/browse/CON-77

VQConnector-VCC-1.5.8

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-40

- Database disconnection on Azure:

Reason: Client is using Azure DB cluster and sometime connection drop with connector.
Requirement: Connection should not drop.
Solution: Connector will now be able to better communicate with Azure db cluster
Ticket: https://virtualq.atlassian.net/jira/software/projects/CON/boards/11?selectedIssue=CON-7

- Database instance goes null:

Reason: Sometimes database instance goes null in connector.
Requirement: find the casue of this and remove it.
Solution: Removed the issue and now db instance will not go null.
Ticket: https://virtualq.atlassian.net/jira/software/projects/CON/boards/11?selectedIssue=CON-37

- Duplicate callbacks:

Reason: Sometimes database has multiple callback entries from connector.
Requirement: find the casue of this and remove it. Although unable to reproduce in lab.
Solution: Removed the issue and now db will have only on callback per caller. Also added extra logging in case if issue sill persists.
Ticket: https://virtualq.atlassian.net/jira/software/projects/CON/boards/11?selectedIssue=CON-55

VQConnector-VCC-1.5.7

Release Update:

- AutoUpdate Feature:

Reason: QConnect had to be reinstalled for every new version update.
Requirement: QConnect should update itself whenever new version is avaiable.
Solution: QConnect will update itself whenever new version is published on GitHub repo: https://github.com/virtualq/QConnect-Release
Ticket: https://virtualq.atlassian.net/jira/software/projects/CON/boards/11?selectedIssue=CON-13

- Fixed Exception in UpdateContact event of vccMonitor:

Reason: a null contact is been added in queue on this event which was causing this issue
Requirement: handle this exception by adding correct contact data.
Solution: added correct contact in queue on UpdateContact event
Ticket: https://virtualq.atlassian.net/jira/software/projects/CON/boards/11?selectedIssue=CON-6

VQConnector-VCC-1.5.6

Release Update:

- Db Connection exception handling:

Reason: QConnect had an exception at the time of db communication.
Requirement: handle this exception and inform properly that QConnect needs a restart
Solution: on DB disconnection QConnect will now add logs to inform about disconnection and will suggest restart.
Ticket: https://trello.com/c/rkuqMAE4/112-db-connection-exception-handling-voxtron

- Add exception handling in call back events of vcc monitor sdk:

Reason: Production logs were indicating exceptions in monitoring sdk's callbacks
Requirement: handle exceptions in the callbacks of monitoring sdk so QConnect won't cause problem.
Solution: QConnect now handles exceptions in the callbacks of monitoring sdk. This will help us finding the exceptions cause.
Ticket: https://trello.com/c/UIlh76um/113-add-exception-handling-in-call-back-events-of-vcc-monitor-sdk-voxtron

- Use SHA256 for hashing phone numbers in Voxtron:

Reason: MD5 algorithm was used for phone number hashing
Requirement: client requirement was to use SHA256 instead of MD5
Solution: QConnect now use SHA256
Ticket: https://trello.com/c/Wlj5MXSS/104-use-sha256-for-hashing-phone-numbers-in-voxtron
Documentation: https://github.com/virtualq/QConnect-Release/wiki/Features#--hash-phone-number

VQConnector-VCC-1.5.5

Release Update:

- Uhandled Exception cause fixed:

Reason: QConnect had an exception which was handled but the cause was not known but when exception was caught in production it revealed its cause (key value pair generated duplicate pairs).
Requirement: resolve the cause making exception happen
Solution: cause was remove by adding custom equality operator.
Ticket: https://trello.com/c/BMA8EaaF/107-calculate-threads-unhandled-exception-caught-in-production

VQConnector-VCC-1.5.4

Release Update:

- Uhandled Exception:

Reason: QConect stopped transmitting agent stats to dashboard
Requirement: an unhandled exception was cause the problem.
Solution: Exception is now handled and will be logged properly
Ticket: https://trello.com/c/XfS3AriT/100-unhandled-exception-in-calculation-thread

- Merge NotifyCallDeferred and Transfer Failed

Reason: CallDeferred case was handled 2 time in QConnect on NotifyCallDeferred and TransfeFailed.
Requirement Merge both cases are handled together.
Solution: both cases are merged and to support old and new builds both name are kept but with single handling.
Ticket: https://trello.com/c/sfwSWCls/98-merge-notifycalldeferred-and-transferfailed-both-are-same