Skip to content

VQConnector-VCC-1.6.0
Compare
Choose a tag to compare
@zeeshanalikhan15 zeeshanalikhan15 released this 04 Oct 12:27
v1.6.0
01e6caa
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

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

Assets 5
Loading