I was advised to write here instead of email. Here is the problem. I insert call information into three tables, callque, calltrack, portstouse. The call is made, but the calltrack is not updated. Please help.
09 May 2015 - 04:25 AM
11 May 2015 - 02:46 PM
it looks like you are inserting the data into the voiceguide database directly, and are not using the Outgoing Call Loader or Data Files etc.
vgEngine shows that system is using the default SQLite database, which on this system is located at: C:\VoiceGuide\data\vgDb.db
Can you please post the vgDb.db file that has the inserted calltrack entry in it?
vgEngine trace shows that SQL commands to update calltrack were ran:
134957.307 12 db PerformWork_RunCoreSql ExecuteNonQuery call: UPDATE calltrack SET History='dialed@134957, ', TimeLastCall='2015-05-07 13:49:57', RetriesLeft=2 WHERE (QueID=1 OR QueGUID='1fa19d98-7c6f-44dc-b501-3b189d238996'); 134957.308 12 db PerformWork_RunCoreSql cmd_CoreSql.ExecuteNonQuery returned 135028.324 12 db PerformWork_RunCoreSql ExecuteNonQuery call: UPDATE calltrack SET Outcome='Answered_Machine', History='dialed@134957, Answered_Machine@135028, Answered_Machine@135028, ', TimeCallAnswered='2015-05-07 13:50:28', RetriesLeft=2 WHERE (QueID=1 OR QueGUID='1fa19d98-7c6f-44dc-b501-3b189d238996'); 135028.325 12 db PerformWork_RunCoreSql cmd_CoreSql.ExecuteNonQuery returned
so most likely no entry in calltrack table satisfied this:
WHERE (QueID=1 OR QueGUID='1fa19d98-7c6f-44dc-b501-3b189d238996')
This can be further confirmed by looking at the vgDb.db or the SQL that is used to insert entry into calltrack table.
Please .ZIP up the vgDb.db before posting.
Many problems that occur when inserting data directly into database can be resolved by comparing inserts with how the Outgoing Call Loader loads the data into the database.
An application to view SQLite database files' contents can be found here: http://sqlitebrowser.org/
12 May 2015 - 04:46 AM
13 May 2015 - 12:22 PM
Please update your system to this version of VoiceGuide:
[old link removed]
This version changes how updates to calltrack table are made.
Please let us know if you still encounter issues after the update.
To change from one release of VoiceGuide v7 to another:
1. Stop VoiceGuide service and exit all VoiceGuide programs. (eg Script Designer, Voicemail Manager, etc) and all other programs.
2. Run the VoiceGuide install and install into same directory as existing installation. (Do NOT uninstall the previous VoiceGuide installation).
3. Start VoiceGuide service.
Running a VoiceGuide install over the top of an existing install will NOT overwrite existing configuration or license files (Config.xml, ConfigLine.xml, VG.INI, VmBoxList.xml, userinfo.lic) and will not remove any of users script or sound files, and will not remove any log files etc.
Please note however that the local SQLite outdial database will be re-initialized. If you are using the local SQLite outdial database and have any queued outgoing calls that you would like to keep then this database should be backed up first.
14 May 2015 - 08:43 AM
This solved the problem. The calltrack table is updated by VG now. Thank you.