[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-18。"],[[["\u003cp\u003eAs of July 2024, automatic migration to new speech models is complete for configurations where the current model is \u003ccode\u003ephone_call\u003c/code\u003e, the \u003ccode\u003emodel_variant\u003c/code\u003e is other than \u003ccode\u003eUSE_STANDARD\u003c/code\u003e, and \u003ccode\u003esingle_utterance\u003c/code\u003e is \u003ccode\u003efalse\u003c/code\u003e, directing traffic to the \u003ccode\u003etelephony\u003c/code\u003e model.\u003c/p\u003e\n"],["\u003cp\u003eAutomatic migration for other speech model settings is currently on hold with no estimated time of resumption.\u003c/p\u003e\n"],["\u003cp\u003eUsers can proactively opt in to migrate earlier by changing the speech model identifier in the Conversational Agents (Dialogflow CX) or Dialogflow ES API to take advantage of the improved accuracy.\u003c/p\u003e\n"],["\u003cp\u003eThe migration affects specific language tags, including \u003ccode\u003een-au\u003c/code\u003e, \u003ccode\u003een-gb\u003c/code\u003e, \u003ccode\u003ede\u003c/code\u003e, \u003ccode\u003ees\u003c/code\u003e, \u003ccode\u003efr\u003c/code\u003e, \u003ccode\u003eit\u003c/code\u003e, \u003ccode\u003eja\u003c/code\u003e, and \u003ccode\u003ept-br\u003c/code\u003e, redirecting traffic from the \u003ccode\u003ephone_call\u003c/code\u003e model to new conformer-based speech models.\u003c/p\u003e\n"],["\u003cp\u003eIf the advanced timeout-based end of speech sensitivity is enabled in a Dialogflow CX agent, the model identifier is routed assuming \u003ccode\u003esingle_utterance\u003c/code\u003e is \u003ccode\u003efalse\u003c/code\u003e, regardless of the actual setting.\u003c/p\u003e\n"]]],[],null,["# Speech model migration for phone_call in Q2 2024\n\nMigration status\n----------------\n\nAs of July 2024, the [automatic migration](#automatic) has been completed for\nthe following combination of settings that correspond to the second row in the\n[migration table](#overview):\n\nFor other combination of settings, the automatic migration will remain on hold\nuntil further notice (no ETA).\n\nYou can continue to use the `phone_call` model identifier but are encouraged to\n[opt in](#opt-in) to use conformer-based speech models.\n\nMigration overview\n------------------\n\nFor certain [language tag](/dialogflow/cx/docs/reference/language) and speech\nsetting combinations, the Conversational Agents (Dialogflow CX) and Dialogflow ES traffic with audio will\ngradually route away from the classic Speech-to-Text model behind the\n`phone_call` model identifier to the new conformer-based [speech\nmodels](/speech-to-text/docs/transcription-model). As the redirection will be\ninternal only, the current model identifiers and code will remain valid and\ncontinue to serve traffic.\n\nThe affected language tags are: `en-au`, `en-gb`, `de`, `de-de`, `es`, `es-es`,\n`es-us`, `fr`, `fr-ca`, `fr-fr`, `it`, `it-it`, `ja`, `pt-br`.\n\nThe following table shows the routing of Speech-to-Text\n`phone_call` model that will take place when the migration takes effect. If your\nconfiguration matches the language tag and the first three columns in the table,\nthe new model identifier is listed in the fourth column.\n\nMigration options\n-----------------\n\nThere are three migration options: early opt-in, automatic, and temporary\nopt-out.\n\n### Opt in and migrate earlier\n\nTo opt in proactively, change the speech model identifier that you have been\nusing in the [Conversational Agents (Dialogflow CX)\nAPI](/dialogflow/cx/docs/reference/rest/v3/ConversationTurn#inputaudioconfig)\nand [Dialogflow ES\nAPI](/dialogflow/es/docs/reference/rpc/google.cloud.dialogflow.v2#inputaudioconfig)\nwith the updated one. For Conversational Agents (Dialogflow CX), you can also change the [model\nidentifier](/dialogflow/cx/docs/concept/agent#stt-model-selection) in the\n**Advanced speech settings** under **Speech and IVR settings** in the\nConversational Agents (Dialogflow CX) console.\n\nSpeech model specified in the API at runtime takes precedence over the speech\nmodel specified in the Conversational Agents (Dialogflow CX) console, unless you enable the [**Override\nrequest-level speech\nmodel**](/dialogflow/cx/docs/concept/agent#stt-model-selection) setting. Read\nmore about precedence in [speech\nmodels](/dialogflow/cx/docs/concept/speech-models).\n\nFor partner telephony integrations, check with your telephony provider if the\nspeech model is being set in the API. If you are using the Conversational Agents (Dialogflow CX) Phone\nGateway, review the speech model\n[limitations](/dialogflow/cx/docs/concept/integration/phone-gateway#limits).\n\nMigrating your project proactively gives you time to test the models and take\nadvantage of the improved accuracy and robustness earlier. Most integrations\nrequire `single_utterance = true`, so if you are not using [advanced\ntimeout-based end of speech\nsensitivity](/dialogflow/cx/docs/concept/agent#advanced-end-of-speech-sensitivity)\nyou'll likely want to use `latest_short`.\n\nIf you experience issues with the new models, [open a Google Cloud support\ncase](/support/docs/customer-care-procedures) with issue details.\n\n### Migrate automatically\n\n| **Note:** See [migration status](#status).\n\nTo be migrated automatically, no action is required on your part. The existing\nSpeech-to-Text model identifiers are valid and we will shift traffic\ninternally.\n\n### Opt out and migrate later\n\nDue to the suspended [migration status](#status), new opt-out requests are not\naccepted. If your projects were opted out before July 2024, they will remain in\nthis state until further announcement."]]
