Migration status
As of July 2024, the automatic migration has been completed for the following combination of settings that correspond to the second row in the migration table:
Current model identifier |
Current model_variant |
Current single_utterance setting * |
Model identifier that traffic is directed to |
|---|---|---|---|
phone_call |
Other than USE_STANDARD |
false |
telephony |
| Symbol | Description |
|---|---|
| * | If your Dialogflow CX agent has enabled advanced timeout-based end of speech sensitivity, then the model identifier is routed assuming single_utterance is false, even if the setting is set to true at runtime. |
For other combination of settings, the automatic migration will remain on hold until further notice (no ETA).
You can continue to use the phone_call model identifier but are encouraged to
opt in to use conformer-based speech models.
Migration overview
For certain language tag and speech
setting combinations, the Dialogflow CX and Dialogflow ES traffic with audio will
gradually route away from the classic Speech-to-Text model behind the
phone_call model identifier to the new conformer-based speech
models. As the redirection will be
internal only, the current model identifiers and code will remain valid and
continue to serve traffic.
The affected language tags are: en-au, en-gb, de, de-de, es, es-es,
es-us, fr, fr-ca, fr-fr, it, it-it, ja, pt-br.
The following table shows the routing of Speech-to-Text
phone_call model that will take place when the migration takes effect. If your
configuration matches the language tag and the first three columns in the table,
the new model identifier is listed in the fourth column.
Current model identifier |
Current model_variant |
Current single_utterance setting * |
Model identifier that traffic will be directed to |
|---|---|---|---|
phone_call |
USE_STANDARD |
false |
latest_long |
phone_call |
Other than USE_STANDARD |
false |
telephony |
phone_call |
any | true |
latest_short |
| Symbol | Description |
|---|---|
| * | If your Dialogflow CX agent has enabled advanced timeout-based end of speech sensitivity, then the model identifier is routed assuming single_utterance is false, even if the setting is set to true at runtime. |
Migration options
There are three migration options: early opt-in, automatic, and temporary opt-out.
Opt in and migrate earlier
To opt in proactively, change the speech model identifier that you have been using in the Dialogflow CX API and Dialogflow ES API with the updated one. For Dialogflow CX, you can also change the model identifier in the Advanced speech settings under Speech and IVR settings in the Dialogflow CX console.
Speech model specified in the API at runtime takes precedence over the speech model specified in the Dialogflow CX console, unless you enable the Override request-level speech model setting. Read more about precedence in speech models.
For partner telephony integrations, check with your telephony provider if the speech model is being set in the API. If you are using the Dialogflow CX Phone Gateway, review the speech model limitations.
Migrating your project proactively gives you time to test the models and take
advantage of the improved accuracy and robustness earlier. Most integrations
require single_utterance = true, so if you are not using advanced
timeout-based end of speech
sensitivity
you'll likely want to use latest_short.
If you experience issues with the new models, open a Google Cloud support case with issue details.
Migrate automatically
To be migrated automatically, no action is required on your part. The existing Speech-to-Text model identifiers are valid and we will shift traffic internally.
Opt out and migrate later
Due to the suspended migration status, new opt-out requests are not accepted. If your projects were opted out before July 2024, they will remain in this state until further announcement.