When you upload audio data for quality inspection using an API, you must provide a recording URL. You can use this page to configure authentication information that is automatically appended to your recording URLs.
When you upload audio data for quality inspection by calling an API, you must provide a recording URL. After your request is received, the service downloads the recording file. The quality inspection application must be able to access this URL. You can secure your recordings in several ways:
1. Store the recording in OSS and generate a URL with a validity period. This method is not recommended because the recording cannot be played back for review after the URL expires.
2. Store the recording on your own server and provide a recording URL that includes authentication information when you upload the audio data. This method is not recommended. If the authentication information is leaked and you later change it, historical recordings cannot be played back for review.
3. Store the recording on your own server. You can configure the authentication information in the Smart Conversation Analysis console. When you upload audio data, provide only the standard recording URL. When the service downloads the recording, it automatically appends the configured authentication information. This method reduces the risk of information leaks compared to the second option. If the information is leaked, you can change it immediately without affecting the playback of historical recordings during review.
This document describes the third method, which is the recommended approach.
Create a configuration
Click Create Configuration above the list. On the page that appears, enter the required information. The URL parameters serve as the authentication information. You can set multiple parameters. The following figure shows an example in which two parameters are added. For example, if you provide the recording URL http://XXXXXXXX.com/a.wav when you call the API, the service accesses the full URL http://XXXXXXXX.com/a.wav?caller=aliyun&secretKey=XXXX to download the recording. You are responsible for parsing the authentication information to verify its validity.
Generate a test link
Click Generate test link to create a test link. Then, click the Test button to verify that the authentication information is configured correctly.