I've got a trial Advanced Edition licence on my VMPro at the moment as I'm trying out some VBScript stuff that we want to use shortly, but got an odd problem with it. Thought I'd ask here first before going to our reseller as it may be something in the code I can do as opposed to something else.
Basically, the VBScript actions don't always fire. If I let the call flow complete and disconnect me by itself, I can run it again fine, so I know my code's not necessarily incorrect. However, it appears that if the call is hung up during the VBScript being run, another VBScript action won't work until I restart the voicemail service. All other call flows not using VBScript continue to function fine without a service restart... unless I put a VBScript action in, and then it runs ok up to the VBScript and then halts, unless I restart the service.
I can re-write the call flow I want to do using the Database actions, but I'd rather use VBScript as it's easier from my point of view (says the VB6 Programmer!)
I'm using VMPro 7.0(28) on a Windows 2008 R2 x64 box, and I'll post the code if necessary later.
Basically, the VBScript actions don't always fire. If I let the call flow complete and disconnect me by itself, I can run it again fine, so I know my code's not necessarily incorrect. However, it appears that if the call is hung up during the VBScript being run, another VBScript action won't work until I restart the voicemail service. All other call flows not using VBScript continue to function fine without a service restart... unless I put a VBScript action in, and then it runs ok up to the VBScript and then halts, unless I restart the service.
I can re-write the call flow I want to do using the Database actions, but I'd rather use VBScript as it's easier from my point of view (says the VB6 Programmer!)
I'm using VMPro 7.0(28) on a Windows 2008 R2 x64 box, and I'll post the code if necessary later.