[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[],[],null,["# SBC configuration and validation\n\nThis page walks you through the process of configuring and validating the SBC.\n\nSupported vendors and firmware\n------------------------------\n\nBefore you begin the configuration, review the\ntable of\n[supported SBC vendors or models and firmware versions](/dialogflow/cx/docs/concept/integration/sip-trunk/concepts-troubleshooting#supported_sbc_vendors_or_models).\n\nSupported SBC signaling and media protocols\n-------------------------------------------\n\nThe supported signaling and media protocols are specified in the\n[SBC signaling and media protocols documentation](/dialogflow/cx/docs/concept/integration/sip-trunk/concepts-troubleshooting#supported_sbc_signaling_and_media_protocols).\nNote that `AES_CM_128_HMAC_SHA1_80` is the only SRTP cipher suite supported.\n\nSBC's TLS configuration\n-----------------------\n\nRequest a TLS certificate for the SBC from an approved certificate authority\nvendor. Wildcard certificates are not supported.\n\nWithin the TLS certificate, you must present the SBC's fully qualified domain\nname (FQDN) either in the common name (CN) attribute or in the subject\nalternative name (SAN) attribute. If you request one TLS certificate for\nmultiple SBCs, the certificate's SAN should include all SBC FQDNs.\n\nApproved certificate authority vendors\n\n- DigiCert\n- Entrust DataCard\n- GlobalSign\n- GoDaddy\n- Sectigo (Formerly known as Comodo)\n\n### Configure SBC TLS\n\n1. Install the requested TLS certificate along with the associated root CA certificate to the SBC's trust chain.\n2. Install Google's trusted root CA into SBC's trust chain. To get the Google\n Root certificate:\n\n 1. Download Google's [trusted root CAs](https://pki.goog/roots.pem).\n 2. Extract GTS Root R1 (GTSR1).\n 3. If required, extract the GlobalSign Root CA certificate.\n 4. Upload the root certificates to your SBC keystore.\n 5. Enable mutual authentication for the SBC.\n3. Configure supported TLS versions and cipher suites. TLS versions 1.2 or later\n are supported. Supported cipher suites:\n\n - `TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256`\n - `TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256`\n - `TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256`\n - `HTLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256`\n - `TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384`\n - `TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384`\n - `TLS_AES_256_GCM_SHA384`\n - `TLS_CHACHA20_POLY1305_SHA256`\n - `TLS_AES_128_GCM_SHA256`\n\nCreate a SIP trunk on GTP\n-------------------------\n\n1. Navigate to the [Unified Console](https://ccai.cloud.google.com/projects) and select your project.\n2. Navigate to the **SIP Trunks** tab, then click **Add a SIP Trunk**.\n3. Fill in all required fields.\n4. Click **Create**.\n\nReview telephony connectivity network requirements\n--------------------------------------------------\n\nSee the [concepts and troubleshooting page](/dialogflow/cx/docs/concept/integration/sip-trunk/concepts-troubleshooting#telephony_network_requirements)\nfor a table of network and connectivity requirements.\n\nConfigure SBC for SIP connection to GTP\n---------------------------------------\n\nIf your SBC is deployed with one of the supported and certified SBC vendors,\nsee the [SBC signaling and media protocols documentation](/dialogflow/cx/docs/concept/integration/sip-trunk/concepts-troubleshooting#supported_sbc_signaling_and_media_protocols)\nfor detailed instructions specific to that vendor.\n\nEnsure that the SIP profile is configured to use TLS over TCP port 5672\ntargeting specific regionalized GTP's SIP servers (for example,\n`us.telephony.goog`). SIP and SIPREC integration configuration:\n\n- For the use case of connecting to Dialogflow virtual agents, configure SIP integration on the SBC.\n- For the use case of Conversational AI Agent Assist or Insights, configure SIPREC integration on the SBC so copies of the media stream are forked to GTP. Note that using SIPREC with certain SBC vendors might be a separate licensed feature that you must purchase and activate.\n\nSIP connectivity test with SIP OPTIONS ping\n-------------------------------------------\n\nPerform a SIP OPTIONS ping test from customer SBC to GTP to ensure that your\nSBC receives a `SIP 200 OK` from GTP. If `SIP 200 OK` is not received, refer to\nthe SIP [troubleshooting section](/dialogflow/cx/docs/concept/integration/sip-trunk/concepts-troubleshooting#troubleshooting)\nfor more details.\n\nSIP header configuration for Conversational AI conversations\n------------------------------------------------------------\n\n1. Set Conversational AI's Conversation ID by configuring the SIP header (`Call-Info` or UUI) during SIP INVITE.\n2. Use the `Call-Info` SIP header. If that is not supported, you can use the User-to-User-Info (UUI) SIP header. Refer to [SIP headers](/dialogflow/cx/docs/concept/integration/sip-trunk/concepts-troubleshooting#sip_headers) for more details.\n3. (Optional) Configure participant roles (`END_USER` and `HUMAN_AGENT`) and media stream order. Refer to the [participant roles](/dialogflow/cx/docs/concept/integration/sip-trunk/concepts-troubleshooting#configure_participant_roles_and_media_stream_order) section for details.\n4. (Optional) To set additional parameters for a given conversation, call the `MatchIntentRequest` API. Refer to the [additional parameters section](/dialogflow/cx/docs/concept/integration/sip-trunk/concepts-troubleshooting#set_additional_parameters_on_a_given_conversation) for details.\n\nPerform test calls\n------------------\n\nConduct a test call and check to ensure SIP and media are traversing to GTP SIP\nservers (`74.125.88.128/25`) and RTP media servers (`74.125.39.0/24`). You\nshould get a `SIP 200 OK` response message.\n\nIf you receive a `SIP 400's` error response code it likely indicates that GTP\nrejected either the SIP header or SIP media SDP configuration. Refer to the\n[troubleshooting section](/dialogflow/cx/docs/concept/integration/sip-trunk/concepts-troubleshooting#troubleshooting)\nfor details. If you receive a `SIP 600's` error response code, it likely\nindicates a quota-related issue.\n\nReview Dialogflow conversation history\n--------------------------------------\n\nThis section applies only if you deploy a Dialogflow virtual agent.\n\nIf the previous test call resulted in a `SIP 200 OK` response, check the\nConversational AI Google Cloud project's Dialogflow\n[conversation history](/dialogflow/cx/docs/concept/conversation-history#browser)\nto make sure new conversations are being logged and include the conversation ID\nspecified in the call info header.\n\n(Optional) Review Google Cloud Logs Explorer\n--------------------------------------------\n\nCheck Dialogflow activity in the Conversational AI Google Cloud project's\nLogs Explorer \"incoming_call\" log.\n\n1. Use the following query to review Dialogflow's incoming call activities,\n then click \"Run query\":\n\n `logName=\"projects/$PROJECT_ID/logs/dialogflow.googleapis.com%2Fincoming_call`\n\n `$PROJECT_ID` = The Google Cloud project ID that you used to configure the\n telephony integration.\n2. Alternatively, you can navigate to the Logs Explorer's **All log names**\n drop down box and search for log name `incoming_call`. Select it and click\n **Apply**.\n\n3. Verify that Dialogflow created a conversation successfully in the\n Google Cloud project's Logs Explorer (this step only applies if audit\n logging is\n [enabled for the Dialogflow API](/dialogflow/cx/docs/concept/integration/sip-trunk/cloud-setup#audit-logging)).\n Use the following query to review Dialogflow's conversation creation\n events from a specific Google Cloud project and conversation profile, then\n click **Run query**.\n\n protoPayload.serviceName=~\"dialogflow\"\n protoPayload.methodName=~\"google.cloud.dialogflow.*.Conversations.CreateConversation\"\n protoPayload.request.conversation.conversationProfile=\"projects/$PROJECT_ID/locations/global/conversationProfiles/$CONVERSATION_PROFILE_ID\"\n\n - `$PROJECT_ID` = The Google Cloud project ID defined when you [configured the integration](/dialogflow/cx/docs/concept/integration/sip-trunk/cloud-setup#select-project).\n - `$CONVERSATION_PROFILE_ID` = The conversation profile ID you created when you [configured the integration](/dialogflow/cx/docs/concept/integration/sip-trunk/cloud-setup#configure-profile)."]]
