AWS S3
Last updated
Last updated
IMPORTANT: This is an advanced module. Some setup is required before use.
This module uses the supported third-party service AWS S3. The module allows you to integrate an S3 bucket into your application to upload audio recorded during a call.
You can select and use any S3 integration that has been added to your Fuse account.
Call recordings are uploaded in different formats depending on the source module:
.wav
.ulaw
To use this module, you must have an account with AWS (Amazon Web Services). You must also have a working Amazon S3 bucket added as an integration to your Fuse account.
Complete the following in order:
As shown in Figure 2, the following fields are available. Completing an active field enables the next:
Select Bucket: Select one of your AWS S3 integrations.
Select Path: Select the path in your S3 bucket where your recording will be uploaded.
Select Recording: Select the name of the recording module that will generate the recording to be uploaded.
File Name: Enter a filename for the recording as a string or variable.
Note: A timestamp will also be automatically appended to each filename before uploading.
Uploaded recordings will have the following, final syntax:
[filename]-[timestamp]
This allows users to set the maximum time, in seconds, that elapse before returning a timeout error. This applies to modules that fetch outside scripts, like the SOAP, REST, or subdialog modules. The default value for Timeout Length is 30 seconds. Acceptable number values range from 1 to 120.
The AWS S3 module is designed to work alongside the and modules. It can only handle the call recordings generated by those two modules. The AWS S3 module will not work for any other type of object storage.
Get an AWS account. ()
Set up a working bucket with Amazon S3. ()
Set up an IAM user with access keys and an IAM policy for S3. ()
Admin-only task: .
Once finished, the AWS S3 module can be used successfully.
Enable this setting to play audio while an end-user is on hold. To upload a file for hold music, go to Application Settings > Connection Settings > > Webservice fetch audio.
This setting controls the logging function of a module. Enabling the 'Private' setting instructs the module to not record, report, or retain the information input to that module for reporting or any other purposes. When enabled any information entered into a module during a call will be lost immediately when the call terminates. The 'Private' setting is critical for businesses that need to maintain PCI-DSS or HIPAA compliance. The module icon, in the upper left-hand corner, becomes grayed-out when this setting is enabled. See more details .
Enabling this setting overrides the default, global error options set in the Application Settings > . This allows users to establish custom error handling in order to act on errors in a specific way in that module. Instead of progressing to the next module in the call-flow, custom error handling allows users to re-prompt the same module, to provide a custom error message, to re-direct the call based on the error, or any other desired behavior. Adding multiple errors () to a module functions behave the same way as a counter. The first error follows the path for the first error listed, if a second error occurs in the same module it follows the second listed error, and so on until all errors are exhausted or an error directs the end-user away from that module. No Input occurs when the caller does not provide an input based on the timeout settings. This is based on the “Initial input timeout” in . No Match occurs when the caller input does not match the module's criteria for the input module.
