UCCX 8.0 Upload Recording problem

Question

Hello,
I haven't been able to get the upload recording function to work. When I use the Reactive Script debug it works through the authenticate step, but then jumps to the unsuccessful step of the upload recording. I've tried loading it to L[en_US] as ptMsgOne.wav as well as to a subfolder called PatrickTest\ptMsgOne.wav. I tried with the prompt already being there, with an old message, and without it being there. Same results. I've attached the script, but just as a .docx, since some of the repondants can't always access .aef files. Any help would be greatly appreciated.
Thanks,
Patrick

Answer 1

I cannot see the properties of your Upload Document step, and it's possible the error is in there somewhere.  If you pop it open and screenshot it, I'll take a look.
On the topic of XML documents and templates, you could do this in one of three ways:
Individual XML documents for each prompt, and individual templates for each XML document
Individual XML documents for each prompt, and a single shared template for all XML documents
A single XML document, with individual elements for each prompt, and a single template for the XML document
Option 1 uses extra documents when they're not needed, but gives you flexibility with the templates
Option 2 uses less documents but limits your flexibility with the templates
Option 3 uses the least amount of documents, but has the most complex scripting requirements
I personally would go with option 2.  It's a good balance between file counts, and ease of scripting.
Moving to another solution option, I didn't see if this was a requirement or not, but do you need the recording to go unmodified between uses, or would the recording be re-recorded between uses?
E.g., If you were using a holiday greeting specific to the holiday, you would need to re-record the recording for each holiday.  On the flip side of that coin, you might have a "high call volume" message playing at the beginning of the call, which doesn't change, but you need to toggle it on and off.
In the case of the holiday greeting, you could simply silence the recording by pressing the mute button on the phone when you go to record it, so no audio is recorded, and then quickly end the recording step by pressing the pound/hash (#) key.
In the case of the "high call volume" message, you would definitely need to control the playing of the recording with a file.
But if you didn't want to mess with XML, and just to keep things simple, you could just use a plain text document for each prompt, which contains either a 0 or a 1 (Off or On respectively).
Here's how that would look if you were to read the status from the text file
Reading a Plain Text Status Document Example
Prompt
Filename
PatrickTest/ptMsgOne.wav
Contents
...audio...
Document
Filename
PatrickTect/ptMsgOne.txt
Contents
0
Script
Variables
Prompt msgOnePrompt = P[PatrickTest/ptMsgOne.wav]Document msgOneStatusDoc = DOC[PatrickTest/ptMsgOne.txt]String msgOneStatusValue = ""
Steps
StartAccept (--Triggering Contact--)Set msgOneStatusValue = msgOneStatusDocIf (msgOneStatusValue == "1")  True    /* Only play the prompt if the value is exactly equal to "1" */    Play Prompt (--Triggering Contact--, msgOnePrompt)  False    /* If the value is anything other than a "1", E.g., "0" or even "2", don't play it */Terminate (--Triggering Contact--)End
You could use the above example in your status management IVR to tell the admin if the current setting is either On or Off.
Here's how updating the status document could look, sans a menu or anything fancy, just straight to the mechanics of it.
Writing a Plain Text Status Document Example
Document
Filename
PatrickTect/ptMsgOne.txt
Contents
0
Script
Variables
String msgOneStatusFilename = "PatrickTest/ptMsgOne.txt"Document msgOneStatusDoc = DOC[PatrickTest/ptMsgOne.txt]String msgOneStatusValue = ""User user = USER[avholloway]
Steps
StartAccept (--Triggering Contact--)/* Get the current value */Set msgOneStatusValue = msgOneStatusDoc/* Toggle the value */If (msgOneStatusValue == "1")  True    /* We're flipping the value from a "1" to a "0" */    Set msgOneStatusValue = "0"  False    /* We're flipping the value from any other value to a "1" */    Set msgOneStatusValue = "1"/* Write the new value */Authenticate User PIN (user, "12345")  Successful    /* Authentication worked like a charm, upload the document, overwriting the existing one */    Upload Document (TEXT[msgOneStatusValue] to L[en_US], msgOneStatusFilename)      Successful        /* We have updated the document! */      Unsuccessful        /* Something went wrong updating the document */  Unsuccessful    /* Something went wrong authenticating the user */Terminate (--Triggering Contact--)End
I hope that sheds some light on the subject.
EDIT: Corrected a typo I had in the Upload Document step.
Anthony Holloway
Please use the star ratings to help drive great content to the top of searches.