![]() ![]() Unlike UCCX, the BACD implementation has no way of recording prompts. A good listing of what to expect is provided here. ![]() au) you should see a healthy set of files that are associated with the various prompts that are presented by the BACD application. When you look at the files in flash (e.g. Whether you are running the embedded TCL scripts or loading them from flash, the prompts must be in flash. What you will have when you sit for the lab is anyone's guess. You can also load the TCL scripts from flash memory. The application scripts that provide the BACD functionality come built into the IOS. The Cisco Unified Basic Automatic Call Distribution (BACD) is exactly what its name implies: a basic (very basic) ACD tool. If you need to record a prompt longer than 10 seconds then modify accordingly. The default timeout for the recording step is 10 seconds.For optimal audio quality, use a phone that is associated with a Region that is permitted to use G.711 when communicating to the Region assigned to the UCCX telephony group.Associate a trigger that doesn't conflict with the dial plan the proctors have imposed on your lab. Create a custom application in UCCX to load your recording script.Pick the larger of the two, rename, and then upload to your prompt repository using the application administration web portal ( Once you upload the prompt to the repository, you can access it from other scripts as you would any other user prompt. Sometimes you will find two files created by your script in the temp folder. The full path will be: "C:\Program Files\wfavvid\Temp\". The folder that stores the temporary file is on the UCCX server. ![]() We just need to take advantage of the fact that w hen the Recording Step is encountered in a CRS script, a temporary audio file is stored locally on the UCCX server. We don't need all of that warm and fuzzy stuff to get a usable audio file. In a production recording script, you would have a prompt guiding the user, a way to review the prompt, possibly a way to re-record the prompt, and some post processing of the prompt. Using this "bare bones" script, we are sort of taking a shortcut. It is only needed to ensure the interpreter doesn't error out when encountering the Recording Step during script execution. We aren't going to use this variable per se. To use the Recording Step, create a variable of type Document. ![]()
0 Comments
Leave a Reply. |