This can be reproduced if you, as a user, pick up the phone to answer an outbound call then hang up immediately,
Looks like no script was even started on those calls.
If no script is ran on the call then it's corresponding 'onHangup' script will also not be ran.
The 'onNotAnswered' and 'onRetriesExhausted' event handlers will be started in such cases.
Attached traces capture 9 calls between 14:55 and 16:15 :
3 of these were never answered - running the 'onNotAnswered' was attempted.
5 were hung up less the half a second after answering - running the 'onNotAnswered' was not attempted.
(and 1 was answered, script was ran, and then the 'after hangup' was ran)
To fix the issue that affected the calls that were 'hung up less the half a second after answering' please update system to this version of VoiceGuide:
NB. Probably better to just use a VBScript file (.vbs) or .exe for handlers of these events, instead of using a VoiceGuide script.
[old link removed]
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, etc) and will not remove any of users script or sound files, and will not remove any log files etc