vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Release notes for Speech to Text for IBM Cloud 

IBM Cloud

The following features and changes were included for each release and update of managed instances of IBM Watson® Speech to Text that are hosted on IBM Cloud or for instances that are hosted on [IBM Cloud Pak for Data as a Service](https://dataplatform.cloud.ibm.com/docs/content/wsj/landings/wstt.html). Unless otherwise noted, all changes are compatible with earlier releases and are automatically and transparently available to all new and existing applications.

For information about known limitations of the service, see [Known limitations](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-known-limitations).

For information about releases and updates of the service for IBM Cloud Pak for Data, see [Release notes for Speech to Text for IBM Cloud Pak for Data](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-release-notes-data).



 9 June 2023 

Defect fix: Creating and training a custom Language Model is now optimal for both standard and low-latency Next-Generation models
: Defect fix: When creating and training a custom Language Model with corpora text files and / or custom words using a Next-generation low-latency model, it is now performing the same way as with a standard model. Previously, it was not optimal only when using a Next-Generation low-latency model.

Defect fix: STT Websockets sessions no longer fail due to tensor error message
: Defect fix: When using STT websockets, sessions no longer fail due to an error message “STT returns the error: Sizes of tensors must match except in dimension 0”.





 19 May 2023 

Updates to English next-generation Medical telephony model
: The English next-generation Medical telephony model has been updated for improved speech recognition:



* en-WW_Medical_Telephony



Added support for French and German on new improved next-generation language model customization
: Language model customization for French and German next-generation models was recently added. This service update includes further internal improvements.
[Classic clusters: Why does enabling Ingress ALBs result in subnet errors?](https://cloud.ibm.com/docs/containers?topic=containers-cs_alb_subnetcs_alb_subnet)

[Why does a connection via WebSocket close after 60 seconds?](https://cloud.ibm.com/docs/containers?topic=containers-cs_ingress_websocketcs_ingress_websocket)

[Why does the Ingress status show an ERRSNF error?](https://cloud.ibm.com/docs/containers?topic=containers-ts-ingress-errsnfts-ingress-errsnf)

[Why does the Ingress status show an ERRADNF error?](https://cloud.ibm.com/docs/containers?topic=containers-ts-ingress-erradnfts-ingress-erradnf)

[Why does the Ingress status show an ERRAVUS error?](https://cloud.ibm.com/docs/containers?topic=containers-ts-ingress-erravusts-ingress-erravus)

[Why does the Ingress status show an ERRICCNF error?](https://cloud.ibm.com/docs/containers?topic=containers-ts-ingress-erriccnfts-ingress-erriccnf)

[Why does the Ingress status show an ERRSAM error?](https://cloud.ibm.com/docs/containers?topic=containers-ts-ingress-errsamts-ingress-errsam)

[Why does the Ingress status show an ERRAHCF error?](https://cloud.ibm.com/docs/containers?topic=containers-ts-ingress-errahcfts-ingress-errahcf)

[Why does the Ingress status show an ERRAHSNF error?]
web application (web app) 

An application that is accessible by a web browser and that provides some function beyond static display of information, for instance by allowing the user to query a database. Common components of a web application include HTML pages, JSP pages, and servlets. See also [app](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx4281528).





 web archive (WAR) 

A compressed file format, defined by the Java EE standard, for storing all the resources required to install and run a web application in a single file.





 workload 

A set of customer applications, services, or capabilities that consumes compute, network, storage, or other cloud resources.





 workspace 

A context that contains a collection of artifacts that a user with appropriate permission can modify.







 Z 



 zone 

An independent fault domain. A zone is an abstraction designed to assist with improved fault tolerance and decreased latency. See also [multizone region](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx9774820), [single-campus multizone region](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx10127487).
* Valid values for server_side_exclude are on, off.
* Valid values for tls_client_auth are on, off.
* Valid values for true_client_ip_header are on, off.
* Valid values for waf are on, off.
* Valid values for websockets are on, off.
* Valid values for proxy_read_timeout, 1-6000, default: 100.
* Valid values for ciphers are ECDHE-ECDSA-AES128-GCM-SHA256, ECDHE-ECDSA-CHACHA20-POLY1305, ECDHE-RSA-AES128-GCM-SHA256, ECDHE-RSA-CHACHA20-POLY1305, ECDHE-ECDSA-AES128-SHA256, ECDHE-ECDSA-AES128-SHA, ECDHE-RSA-AES128-SHA256, ECDHE-RSA-AES128-SHA, AES128-GCM-SHA256, AES128-SHA256, AES128-SHA, ECDHE-ECDSA-AES256-GCM-SHA384, ECDHE-ECDSA-AES256-SHA384, ECDHE-RSA-AES256-GCM-SHA384, ECDHE-RSA-AES256-SHA384, ECDHE-RSA-AES256-SHA, AES256-GCM-SHA384, AES256-SHA256, AES256-SHA, DES-CBC3-SHA, default. For example: -v AES256-SHA256,AES256-SHA, using -v default to reset configured cipher suites to default value.



-i, --instance
: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.

--output
: Specify output format, only JSON is supported.





 Examples
You can use API keys to [log in to the IBM Cloud command-line interface (CLI)](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_cliibmcloud_login) or to [generate IAM tokens](https://cloud.ibm.com/docs/account?topic=account-iamtoken_from_apikey). While it is not recommended for production use, you can also send API keys to IBM Cloud services.



 Passing an IBM Cloud IAM token to authenticate with a service's API 

To retrieve an IAM access token, the API client must first invoke an IBM Cloud IAM API to authenticate and retrieve that token. The preferred way for IBM Cloud service API clients is to use an IBM Cloud API key to get an IAM access token. The IAM access token, which was implemented as a [JSON Web Token](https://www.ibm.com/cloud/blog/json-web-tokens-as-building-blocks-for-cloud-security), can be used for multiple invocations of IBM Cloud services that accept IAM access tokens as an authentication method. As IAM access tokens are digitally signed with asymmetric keys, IBM Cloud services can validate an IAM access token without invoking any external service. This dramatically improves the performance of invoking an API.

Zoom

![Authenticating with a service API by using an access token](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/account/images/tokenauth.svg)

Figure 1. Retrieving a token from IAM by using an API key and passing the access token to target services to validate credentials

To authenticate with a service's API by using an access token, complete the following steps:



1.
Interfaces 

You can work with your database in the following ways:



* From the web console
* REST API
* Connect applications or your favorite tools from your local computer
* Use Db2 on Cloud as a data source for your IBM Cloud apps or services





 Web console 

The web console provides a graphical interface for everything that you need to use your database, including: load facilities, an SQL editor, driver downloads, and more.

You can access your web console in the following ways:



* From your IBM Cloud dashboard - You can open the web console from the Service Details page for your Db2 on Cloud service.
* Direct URL - You can bookmark the URL of the web console for your Db2 on Cloud service.







 REST API 

With Db2 on Cloud service plans, you can do tasks that are related to file management, loading data, and resource scaling by using one of the following REST APIs:



* [Database management API (Standard and Enterprise)](https://cloud.ibm.com/apidocs/db2-on-cloud/db2-on-cloud-v4)
* [Database resource scaling API](https://cloud.ibm.com/apidocs/db2-on-cloud/db2oc_scale_exp)







 Connect applications or your favorite tools from your local computer 

Configure your local environment to connect to your Db2 on Cloud database by completing the following steps:



1. Download the [driver package](https://cloud.ibm.com/docs/Db2onCloud/connecting?topic=Db2onCloud-drvr_pkg) from the Db2 on Cloud web console.
2. Install the driver package on the computer where your apps or tools are running:



* [Installing on Linux or PowerLinux](https://cloud.ibm.com/docs/Db2onCloud/connecting?topic=Db2onCloud-drvr_pkgdrvr_install_linux)
Use jsonpath to specify the path to an element of the JSON output. This value is optional.

--quiet, -q
: Specify this option to reduce the output of the command. This value is optional. The default value is false.





 Example 

The following command updates a Git access secret that is called github to use a new host.

ibmcloud ce repo update -n github --host NEW_HOST





 Example output 

Getting Git access secret 'github'...
Updating Git access secret 'github'...
OK









 Revision commands 

An application, or app, runs your code to serve HTTP requests. In addition to traditional HTTP requests, IBM Cloud® Code Engine also supports applications that use WebSockets as their communications protocol. An app contains one or more revisions. A revision represents an immutable version of the configuration properties of the app. Each update of an app configuration property creates a new revision of the app.

Use revision commands to manage application revisions.

You must be within the context of a [project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-project) before you use revision commands.

For more information about working with revisions for apps, see [Deploying applications](https://cloud.ibm.com/docs/codeengine?topic=codeengine-application-workloads).

You can use either revision or rev in your revision commands. To see CLI help for the revision commands, run ibmcloud ce revision -h.



 ibmcloud ce revision delete 

Delete an application revision.

ibmcloud ce revision delete --name REVISION_NAME [--force] [--ignore-not-found] [--quiet]



 Command Options 

--name, -n
: The name of the application revision. This value is required.

--force, -f
: Force deletion without confirmation. This value is optional. The default value is false.

--ignore-not-found, --inf
apic config:set catalog=apic-catalog://<region>.apiconnect.ibmcloud.com/orgs/<username_string>-dev/catalogs/<catalog>

where:

- <region> is the IBM Cloud region.

- <username_string> is your IBM Cloud org ID without any symbols. For example,
joe@mycompany.com would be joemycompanycom

- <catalog> is the name of your catalog

To create a LoopBack API by using the CLI, complete the following steps:



1. To create a project, open a command line and enter:



apic loopback



2. In the prompt that follows, you are asked to name your application. Type a name then press Enter.



? What's the name of your application? (<application name>)

The tool prompts you to enter the name of the directory in which to create the
project.

? Enter name of the directory to contain the project: (<project directory name>)




3. Press Enter to use the name you previously entered or type a new name then press Enter. The tool prompts you to select the kind of application to create:



? What kind of application do you have in mind? (Use arrow keys)
empty-server (An empty LoopBack API, without any configured models or datasources)
> hello-world (A project containing a basic working example, including a memory database)



4. Select the application that you want to use and press Enter. The tool displays a number of messages as it creates the project directory and adds a number of directories and files to it.It also runs npm install to install all the project dependencies, as specified in package.json. This process might take some time.
5. Before you can create a model, you need to make sure that your current working directory is the project top-level directory. To do this, enter the following command:

cd <project directory name>
6. To create a model, enter the following command:
From the web browser's location field, copy the URL starting with /projects. For example, projects/a8ce5fed-7f33-4405-aa4b-88ffba322712/deploy/beta. The ID that is specified after the /projects/ segment of the URL is your project ID.
6. Construct a request URL by using the IDs you copied.

For example, the following request lists the collections in the project:

curl -X {request_method} -u "apikey:{apikey}" "{url}/v2/projects/{project_id}/collections?version=2019-11-29 -k"



To get the {collection_id}, you can use the [List collections](https://cloud.ibm.com/apidocs/discovery-datalistcollections) API method. Alternatively, open the collection in the product user interface, and then copy the collection ID, which is displayed after the /collections/ segment of the page URL, from the web browser location field.





 Using the API from Cloud Pak for Data IBM Cloud Pak for Data 

This information applies to Discovery for Cloud Pak for Data only.

To use the API, you must construct the URL to use in your requests.



1. From the IBM Cloud Pak for Data web client main menu, expand Services, and then click Instances.
2. Find your instance, and then click it to open its summary page.
3. Scroll to the Access information section of the page, and then copy the URL. You will specify this value as the {url}.
4. Copy the bearer token also. You will need to pass the token when you make an API call.
5. From the launched application instance, go to the Integrate and Deploy > API Information page.
6. Copy the project ID. You will specify this value as the {project_id}.

If you're using a Content Mining project, stay on the Share Link page. From the web browser's location field, copy the URL starting with /projects.
Interfaces 

You can work with your warehouse database in the following ways:



* From the web console
* REST API
* Connect applications or your favorite tools from your local computer
* Use Db2 Warehouse on Cloud as a data source for your IBM Cloud apps or services





 Web console 

The web console provides a graphical interface for everything that you need to use your database, including: load facilities, an SQL editor, driver downloads, and more.

Zoom

![View of the web console dashboard page](https://cloud.ibm.com/docs-content/v1/content/68e10678b2f8b8694884ecb5442c326c9b60a3fb/Db2whc/images/uc.png)

Figure 1. View of the web console dashboard page

You can access your web console in the following ways:



* From your IBM Cloud dashboard - You can open the web console from the Service Details page for your Db2 Warehouse on Cloud service.
* Direct URL - You can bookmark the URL of the web console for your Db2 Warehouse on Cloud service.







 REST API 

With IBM® Db2® Warehouse on Cloud service plans, you can do tasks that are related to file management, loading data, and resource scaling using the database management [REST API](https://cloud.ibm.com/docs/Db2whc?topic=Db2whc-con_rest_api)





 Connect applications or your favorite tools from your local computer 

Configure your local environment to connect to your Db2 Warehouse on Cloud database by completing the following steps:



1. Download the [driver package](https://cloud.ibm.com/docs/Db2whc/connecting?topic=Db2whc-dr_pkg) from the Db2 Warehouse on Cloud web console.
2. Install the driver package on the computer where your apps or tools are running:



* [Installing on Linux or PowerLinux](https://cloud.ibm.com/docs/Db2whc/connecting?topic=Db2whc-dr_pkginstall_dr_pkg_linux)
curl -X POST "$vpc_api_endpoint/v1/instances/$instance_id/console_access_token?version=2020-01-26&generation=2" -H "Authorization: $token" -d '{
"console_type":"serial",
"force": true
}'

By specifying "force" to true, you can connect to the serial console even when the console is used by other users. The default value is false, which means the connection can't be established if the console is being used.
2. Save the value of "href" in the response.
3. Start your serial console program by using the URL.

If you use websocat, specify the --binary flag in your command. For example, websocat --binary "wss://us-south.iaas.cloud.ibm.com/v1/instances/<instance_id>/console?access_token=<access_token>&version=2020-12-06&generation=2"
4. Enter the credentials and follow the prompts to log in to your instances.









 Using CLI to connect to a console 

Make sure that you set up the CLI environment by following [CLI prerequisites](https://cloud.ibm.com/docs/vpc?topic=vpc-set-up-environmentcli-prerequisites-setup).



1. Run the following command to connect to a console:

ibmcloud is instance-console $instance_id [-q, --quiet]

This command opens a serial console by default. To open a VNC console, add the [--vnc] flag to the command to retrieve URL of the console.
2. Depending on what console that you are using, do one of the following steps:



* For VNC consoles, follow Step 2 to Step 7 in [Using API to connect to a VNC console](https://cloud.ibm.com/docs/vpc?topic=vpc-vsi_is_connecting_consolevsi_is_connecting_console_api_vnc).
For more information, see Building a high availability Certificate Authority]] .To use the APIs to deploy an HA CA, you need to provide the database connection file to the "db" section of the config override JSON string. For example, the API request below will deploy a CA with two replicas that connect to a database located on IBM Cloud. curl -X POST 
https://<API endpoint>/ak/api/v2/kubernetes/components/fabric-ca 
-H 'Content-Type: application/json' 
-H 'Authorization: Bearer <IAM_token>' 
-d '{
"display_name": "Sample CA",
"replicas": 2,
"configoverride": {
"ca": {
"db": {
"datasource": "host=test.databases.appdomain.cloud port=31941 user=ibm_cloud password=password dbname=ibmclouddb sslmode=verify-full",
"tls": {
"certfiles":
"<base64 encoded pem>"
],
"enabled": true
},
"type": "postgres"
}
},
"tlsca": {
"db": {
"datasource": "host=test.databases.appdomain.cloud port=31941 user=ibm_cloud password=password dbname=ibmclouddb sslmode=verify-full",
"tls": {
"certfiles":
"<base64 encoded pem>"
] ! ! ,
"enabled": true
},
"type": "postgres"
}
"registry": {
"maxenrollments": -1,
"identities":
{
"name": "admin",
"pass": "adminpw",
"type": "admin",
"affiliation": "",
Your ibmiot nodes will no longer be able to use the BluemixService authentication option so you need to select the API Key option instead.



1. Open the ibmiot node for editing.
2. Under node properties, select API Key.
3. For the API Key field, click the edit icon and then enter the API Key and Authentication Token that you saved from the previous step.
4. Save your changes and redeploy your Node-RED flow.







 Updating an application that doesn't use a Cloud Foundry binding 

Identify the location where your application stores the org ID, API Key and Authentication Token, and replace them with the values that you saved earlier.

If your application uses one of the Watson IoT Platform SDKs, these values are likely to be held in a Properties file.





 Updating an application that uses a Cloud Foundry binding 

IBM Cloud provides a mechanism to bind Cloud Foundry Applications to one or more Cloud Foundry services. Bindings can be established using the IBM Cloud CLI, or by creating a Connection between Application and Service in the IBM Cloud dashboard.

When an Application is bound to a service, the service API Key and Authentication Token credentials are copied into the VCAP_SERVICES environment variable from where the application can retrieve them.

Important: This binding mechanism cannot be used with the new Watson IoT Platform service. You must find the code in your application that is reading from VCAP_SERVICES and replace it with code that reads the values from a location where you now store the API Key and Authentication token. To complete the update you must rebuild and redeploy your application.
1. To open the API Designer user interface, open a command line and enter the following command:



apic edit

The API Designer opens in your default browser.



2. In the navigation list of the API Designer, click Products. The Products tab opens.
3. Click Add and then click New Product. The Add a new product window opens.
4. Complete the following fields:



* Title
* Name
* Version



5. Click Add. The Design tab for the new Product opens.
6. Optional: Enter description, contact, license, and terms of service information for the Product in the Info section.
7. In the Visibility section, specify the users that you want the Product to be visible to. You can choose Public, Authenticated users, or Custom. If you select Custom, use the Type to add field to search for the developer organizations or communities that you want the Plans in the Product to be visible to.

Note: To search for developer organizations or communities, the Product must be in the staged, published, or deprecated state. If the Catalog in which it is staged, published, or deprecated is not a sandbox Catalog, you cannot make other changes to the Product while it is in one of these states. For more information, see [Product lifecycle](https://cloud.ibm.com/docs/apiconnect?topic=apiconnect-managing_productsprod_lifecycle-managing_products).
8. Specify the users that can subscribe to the Product. You can choose Authenticated users or Custom. If you select Custom, use the Type to add field to search for the developer organizations or communities that you want to be able to subscribe to the Plans in the Product.
9. In the APIs section, specify the APIs that you want to include in the Product.



1. Click the Add API icon.
2. Select the APIs that you want to include, then click Apply. The selected APIs are listed.



10. To make an API available to application developers, you must include it in a Plan.
"pronunciation": ".ˈaɪ .ˈi .ˈi .ˈi"
}

The following example enters a sounds-like translation for the word IEEE and obtains the phonetic equivalent in IBM SPR format. Obtaining the phonetic pronunciation for a sounds-like translation is an especially interesting approach to composing a phonetic translation. The spaces of the word are URL-encoded in the example.

IBM Cloud

curl -X GET -u "apikey:{apikey}" "{url}/v1/pronunciation?text=i%20triple%20e&format=ibm"

IBM Cloud Pak for Data

curl -X GET --header "Authorization: Bearer {token}" "{url}/v1/pronunciation?text=i%20triple%20e&format=ibm"

The response shows the SPR symbols for the pronunciation:

{
"pronunciation": "1Y.tr1Ipxl.1i"
}





 Deleting a word from a custom model 

To delete a word from a custom model, use the DELETE /v1/customizations/{customization_id}/words/{word} method. You specify the word to be deleted in the URL of the method. You can delete individual words only; you cannot delete multiple words with a single method.

The following example deletes the word IEEE from the specified custom model:

IBM Cloud

curl -X DELETE -u "apikey:{apikey}" "{url}/v1/customizations/{customization_id}/words/IEEE"

IBM Cloud Pak for Data

curl -X DELETE --header "Authorization: Bearer {token}" "{url}/v1/customizations/{customization_id}/words/IEEE"
For more information, see [Deleting an audio resource from a custom acoustic model](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-manageAudiodeleteAudio).



* Set the strict parameter of the POST /v1/acoustic_customizations/{customization_id}/train method to false to exclude invalid audio resources from the training. The model must contain at least one valid audio resource for training to succeed. The strict parameter is useful for training a custom model that contains a mix of valid and invalid audio resources.