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