Guest miva Report post Posted 07/25/2017 06:53 AM I just put through a single test call and it generated 2 calls at the same time on lines 1 and 2. They are the very first calls in the log attached (search for 041). I believe this may have been happening in previous versions as we have had reports previously but had been unable to replicate it until now. The call in this instance was generated using an XML file, and I confirmed it was only 1 call meant to be going out. The two calls started 1 millisecond apart. If you require any additional information please just let me know. Regards, Ben 0725_1552_vgEngine.zip Share this post Link to post
SupportTeam Report post Posted 07/25/2017 08:32 AM VoiceGuide's vgEngine trace file shows that the system loaded the XML file, and then deleted it, and then, 1 second later, a file with the same name was present in "C:\Program Files\VoiceGuide\data" directory again: 155903.045 7 OutDial load from [C:\Program Files\VoiceGuide\data\OutDialWilsar.xml] 155903.081 7 OutDial input file : loaded 1 entries from C:\Program Files\VoiceGuide\data\OutDialWilsar.xml 155903.081 7 OutDial input file deleted : C:\Program Files\VoiceGuide\data\OutDialWilsar.xml 155903.111 10 5 1 state Dialing (auto) 0412611619 155904.105 15 OutDial load from [C:\Program Files\VoiceGuide\data\OutDialWilsar.xml] 155904.111 15 OutDial input file : loaded 1 entries from C:\Program Files\VoiceGuide\data\OutDialWilsar.xml 155904.111 15 OutDial input file deleted : C:\Program Files\VoiceGuide\data\OutDialWilsar.xml 155904.118 10 8 2 state Dialing (auto) 0412611619 and the two calls were made about 1 second apart... We can add some tracing to vgEngine logs to better confirm that file was deleted the first time as well, but most likely what is happening here is that whatever process is creating that file writes the file again, just after VoiceGuide has read it (and deleted it) the first time. Sounds like it only happens occasionally so looks like its timing-related. Recommend taking a second look at the process that creates this OutDial XML file. It is advisable to first create the file under a different name - that does not have the 'OutDial' prefix in its filename, and after the file writing/copying is completed then rename the file to the OutDial*.xml format. This would ensure that VoiceGuide would not attempt to open the file while it's contents are still being written to by another process Also, this is a different issue, so this question will be split into a separate support forum thread. Share this post Link to post