vania-janet/multiturn-rag-retrieval-data huggingface dataset:
When search results are returned, the phone integration reads the introductory message (for example, I found this information that might be helpful), and then the body of only the first search result.

The entire search response (meaning the introductory message plus the body of the first search result) must be less than 5,000 characters long or the response will not be read at all. Be sure to test the search results that are returned and curate the data collection that you use as necessary.



For more information about using the search integration, see [Leveraging existing help content](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-search-add).

For more information about how to implement common actions from your dialog, see [Handling phone interactions](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-phone-actions).





 Setting up a SIP trunk 

If you do not use the option to generate a free phone number, you are responsible for setting up the SIP trunk that will be used by the phone integration. Find a provider and create a SIP trunk account. Your account will be charged for the phone integration's use of the SIP trunk.

You can set up a SIP trunk in the following ways:



* [Creating a Twilio SIP trunk](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-deploy-phone-configdeploy-phone-config-twilio-setup)
* [Use other third-party providers](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-deploy-phone-configdeploy-phone-config-request-setup)
* [Bring your own SIP trunk](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-deploy-phone-configdeploy-phone-config-byost)
Getting help and support 

Depending on the level of help you need, use the following information to sign up for Slack communication or open an IBM support case.



  Slack channel 

We actively monitor our Slack channel for questions about VPC infrastructure services. Join a community of customers and IBM employees where you can ask questions or discuss IBM Cloud VPC releases.

To sign up, complete the following steps.



1.  Request to [join the public Slack channel](https://cloud.ibm.com/kubernetes/slack).
2.  Next, [sign in to Slack](https://ibm-cloud-success.slack.com).
3.  Finally, join our virtual-private-cloud channel.







  Support cases 

For more information about opening an IBM support cases, or about support levels and case severities, see [Contacting support](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar).

If you need to open a support case, collect as much information as possible to help Support analyze and diagnose your problem.

For UI issues:



*  Provide error codes and reference IDs.
*  Save the full URL of the console when the problem occurred, for example: https://cloud.ibm.com/vpc-ext/provision/vs
*  Include steps to reproduce the issue, along with your inputs and expected outputs.
*  Note the approximate time that the error occurred.
*  Provide the code version and error details:



1.  Right-click the console page and select the Inspect or Inspect Element option.
2.  Click the Console tab and copy the version information at the beginning of the output (Project, Version, Build Time, and so on).
3.  Scroll to the end of the output and copy any errors or stack traces.



*  Provide the network response:



1.  While you inspect the page, click the Network tab.
2.  Refresh the page and reproduce the problem.
3.  Filter all requests by the word "graph".
4.  Starting at the end of the list, click each request and view the Preview tab. If the request has an "errors" node, expand that node to show the full error.
5.  Click the Response tab and include the full response string and the URL that generated the response.
Call-ID: 898234234@agenta.atlanta.example.com
CSeq: 23 REFER
Max-Forwards: 70
Refer-To: sip:user@domain.com?User-to-User=637573746f6d2d757365722d746f2d75736572%3Bencoding%3Dhex
Contact: sip:a@atlanta.example.com
Content-Length: 0

If a custom User-to-User header is specified, then the session history key is set in the X-Watson-Assistant-Session-History-Key header.

REFER sip:b@atlanta.example.com SIP/2.0
Via: SIP/2.0/UDP agenta.atlanta.example.com;branch=z9hG4bK2293940223
To: <sip:b@atlanta.example.com>
From: <sip:a@atlanta.example.com>;tag=193402342
Call-ID: 898234234@agenta.atlanta.example.com
CSeq: 93809823 REFER
Max-Forwards: 70
Refer-To: sip:user@domain.com?User-to-User=637573746f6d2d757365722d746f2d75736572%3Bencoding%3Dhex&X-Watson-Assistant-Session-History-Key=dev::latest::893499::dff9c274-adc4-4f63-93de-781166760bf8::978f1fd7-4e24-47d8-adb0-24a8a6eff69e::b5ffd6c2-902f-4658-b586-e3fc170a6cf3::7ad616a350cc48078f17e3ee3df551de
Contact: sip:a@atlanta.example.com
Content-Length: 0

For Twilio Flex, the User-to-User header will use encoding=ascii.
* Something is wrong with the site's configuration. Usually, this happens when accounts have been signed up with a partner organization (for example, a hosting provider) and the provider's DNS fails.



Error 1023 is returned via a HTTP 409 response code.



 Resolution 

Contact Support with the following details:



* Your domain name
* A screenshot of the 1023 error including the RayID mentioned in the error message
* The time and timezone the 1023 error occurred









 Error 1025: Please check back later 

A common cause of error 1025 is when a request is not serviced because the domain has reached plan limits for Edge functions.



 Resolution 

Contact Support to adjust the limits for Edge functions.







 Error 1035: Invalid request rewrite (invalid URI path) 

Common causes of error 1035 are when the value or expression of your rewritten URI path is not valid, and when the destination of the URL rewrite is a path under /cdn-cgi/.



 Resolution 

Make sure that the rewritten URI path is not empty and that it starts with a / (slash) character.

For example, the following URI path rewrite expression is not valid:

concat(lower(ip.geoip.country), http.request.uri.path)

To fix the expression, add a / prefix:

concat("/", lower(ip.geoip.country), http.request.uri.path)







 Error 1036: Invalid request rewrite (maximum length exceeded) 

A common cause of error 1036 is when the value or expression of your rewritten URI path or query string is too long.



 Resolution 

Use a shorter value or expression for the new URI path/query string value.







 Error 1037: Invalid rewrite rule (failed to evaluate expression) 

A common cause of error 1037 is when the expression of the rewrite rule could not be evaluated. There are several causes for this error, but it can mean that one expression element contained an undefined value when it was evaluated.

For example, you get a 1037 error when using the following URL rewrite dynamic expression and the X-Source header is not included in the request:
If you see this message again, go to the [IBM Cloud status page](https://cloud.ibm.com/status?selected=status) to check whether a service or component has an issue. If the problem continues, go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI0060E 

Message: A certificate for the '{0}' domain wasn't uploaded because a problem occurred contacting IBM DataPower Gateway.

Try again later. If you see this message again, go to the [IBM Cloud status page](https://cloud.ibm.com/status?selected=status) to check whether a service or component has an issue. If the problem continues, go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI0061E 

Message: The user, '{0}', wasn't added to the account because a problem occurred contacting the business support system.

Try again later. If you see this message again, go to the [IBM Cloud status page](https://cloud.ibm.com/status?selected=status) to check whether a service or component has an issue. If the problem continues, go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI0062E 

Message: Your session expired, and you must log in again.





 BXNUI0063E 

Message: The operation timed out.

Try again later.





 BXNUI0064E 

Message: The browser that you are using is not supported by IBMIBM Cloud.

The following browsers are supported. Ensure that you use the latest version for your operating system.



* Google Chrome
* Mozilla Firefox
* Internet Explorer
* Safari



For information, see [What are the IBM Cloud prerequisites?](https://cloud.ibm.com/docs/overview?topic=overview-prereqs-platform)
[Shows the Search results dialog](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/search-result-by-field.png)

Figure 1. Search results dialog
4. Click Apply.









 Conversational Search 

A single search field is displayed that mimics the user interface of a virtual assistant.



1. Submit a phrase or keyword.



The query results are returned as passages by default. You can [configure the search to return a specific field](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-query-resultsimprove-search-result) instead.

If you want to investigate the results a bit more, you might want to use a different project type. For more information, see [Improving results for a chatbot](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-chat-choose-project).





 Document Retrieval for Contracts 

Contract-related elements that are recognized in your collection are displayed.



1. Do one of the following things:



* Filter the documents by one of the highlighted elements or by entities that are recognized in your documents (based on the Entities enrichment that is applied to the project by default).
* To view the contract elements in more detail, click a document result to open it. Open the Contract Data tab.





For more information about the elements, see [Understanding contracts](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-contracts-schema).





 Content Mining 

Facets based on the Part of Speech enrichment are shown.



1. To analyze your data, open the Content Mining application. Click Launch application.



For more information, see [Analyzing your data](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-contentminerapp).





 What to do next
"source": "waf",
"userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.163 Safari/537.36"
},
{
"action": "log",
"clientAsn": "5089",
"clientCountryName": "GB",
"clientIP": "203.0.113.69",
"clientRequestPath": "/%3Cscript%3Ealert()%3C/script%3E",
"clientRequestQuery": "",
"datetime": "2020-04-24T10:11:24Z",
"source": "waf",
"userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.163 Safari/537.36"
},
{
"action": "log",
"clientAsn": "5089",
"clientCountryName": "GB",
"clientIP": "203.0.113.69",
"clientRequestPath": "/%3Cscript%3Ealert()%3C/script%3E",
"clientRequestQuery": "",
"datetime": "2020-04-24T10:11:24Z",
"source": "waf",
"userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.163 Safari/537.36"
},
{
"action": "log",
If this time is exceeded, the phone integration tries again to contact Watson Assistant. If the service still can't be reached, the call fails. N/A 
 cdr_custom_data object Any JSON key/value pairs to collect and store with the CDR record at the end of the phone call. Each time this object is received, it is merged with any previously received cdr_custom_data context. N/A 





 Example 

{
"output": {
"generic": [
{
"response_type": "text",
"text": "Hello"
}
]
},
"context": {
"integrations": {
"voice_telephony": {
"post_response_timeout_count": 10000,
"turn_settings": {
"timeout_count": 5000
},
"cdr_custom_data": {
"key1": "value1",
"key2": "value2"
}
}
}
}
}
Show more







 Context variables that are set by the phone channel 



Context variables set by the phone channel

 Name Type Description 

 sip_call_id string The SIP call ID associated with the Watson Assistant session. 
 sip_custom_invite_headers object A JSON object containing key/value pairs defining SIP headers that are pulled from the initial SIP INVITE request and passed to the Watson Assistant service (for example, {"Custom-Header1": "123"}). 
 private.sip_from_uri string The SIP From URI associated with the Watson Assistant service. 
 private.sip_request_uri string The SIP request URI that started the conversation session. 
 private.sip_to_uri string The SIP To URI associated with the conversation session. 
 private.user_phone_number string The phone number that the call was received from. 
 assistant_phone_number string The phone number associated with the Watson Assistant side that received the phone call. 







 Input parameters that are set by the phone channel 

The following input parameters are only valid for the current conversation turn.
If you create a chatbot in IBM Watson™ Assistant, you can route complex customer inquiries to Discovery using a search skill. When a customer asks a question that the dialog is not designed to answer, your assistant can search for relevant information from Discovery, extract the information, and return it as the response. See [Creating a search skill](https://cloud.ibm.com/docs/services/assistant?topic=assistant-skill-search-add) for details. (This feature is available only to Watson Assistant Plus or Premium plan users.)
* What does the "Only one free environment is allowed per resource group" error message mean?

If you have recently deleted a Lite instance and then receive a 400 - Only one free environment is allowed per resource group error message when creating a new environment in a new Lite instance, you need to finish deleting the original Lite instance. See [ibmcloud resource reclamations](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_reclamations) and follow the reclamation-delete instructions.
* Is there size limitation on the length of Natural Language Queries (NLQ)?

The maximum query string length for a natural language query is 2048. For more information, see [Natural language query](https://cloud.ibm.com/docs/discovery?topic=discovery-query-parametersnlq).
* How do you improve query results?

The relevance of natural language query results can be improved in IBM Watson Discovery with training. You can train your private collections using either the Discovery tooling, or the Discovery APIs. For information, see [Improving result relevance with the tooling](https://cloud.ibm.com/docs/discovery?topic=discovery-improving-result-relevance-with-the-tooling).
* How do you know that relevancy training is complete?

For answers to common questions about training a collection and explanations of common error and warning messages, see [Relevancy training tips](https://cloud.ibm.com/docs/discovery?topic=discovery-relevancy-tips).
!]<-- </ol> -->After you finish testing, remove any SpEL expressions that you appended to node responses, or add back any original responses that you replaced with expressions, and repopulate any name or external node name fields from which you removed text.<-- </section "id="section-dialog-runtime-disambig-test" "> --><-- </section "id="section-dialog-runtime-disambiguation" "> --><-- <section "id="section-dialog-runtime-digressions" "> --> Digressions A digression occurs when a user is in the middle of a dialog flow that is designed to address one goal, and abruptly switches topics to initiate a dialog flow that is designed to address a different goal. The dialog has always supported the user's ability to change subjects. If none of the nodes in the dialog branch that is being processed match the goal of the user's latest input, the conversation goes back out to the tree to check the root node conditions for an appropriate match. The digression settings that are available per node give you the ability to tailor this behavior even more.With digression settings, you can allow the conversation to return to the dialog flow that was interrupted when the digression occurred. For example, the user might be ordering a new phone, but switches topics to ask about tablets. Your dialog can answer the question about tablets, and then bring the user back to where they left off in the process of ordering a phone. Allowing digressions to occur and return gives your users more control over the flow of the conversation at run time. They can change topics, follow a dialog flow about the unrelated topic to its end, and then return to where they were before. The result is a dialog flow that more closely simulates a human-to-human conversation.<-- <ul> --> * Before you begin]] * Customizing digressions]] * Digression usage tips]] * Disabling digressions into a root node]] * Digression tutorial]] * Design considerations]] ! ! ! !!!! ! !
Why are my console actions failing in my Chrome browser Version 77.0.3865.90 (Official Build) (64-bit)? 

 What’s happening 

The console has been working successfully, but requests have started to fail. For example, after I create an ordering service and open it I see the error: Unable to get system channel. If you associated an identity without administrative privilege on the ordering service node, you will not be able to view or manage ordering service details.

 Why it’s happening 

This problem can be caused by a [bug](https://bugs.chromium.org/p/chromium/issues/detail?id=1006243) introduced by the Chrome browser Version 77.0.3865.90 (Official Build) (64-bit) that causes actions from the browser to fail.

 How to fix it 

To resolve this problem, open the console in a new browser tab in Chrome. Any identities that you saved in your console wallet will persist in the new browser tab. To avoid this problem you can upgrade your Chrome browser version. Ensure you have downloaded all of your wallet identities to your local machine before closing your browser.





 When I hover over my node, the status is Status unavailable or Status unknown, what does this mean? 

 What’s happening 

A CA, peer, or ordering node has a gray status box, meaning the status of the node is not available. Ideally, when you hover over any node, the node status should be Running.

 Why it’s happening 

This problem can occur if the node is newly created and the deployment process has not completed. If the node is a CA and the status has been gray for more than a few minutes, then it is likely that the deployment process has failed. Peers and ordering nodes take longer to deploy, but this condition can also occur when the health checker that runs against the peer or ordering nodes cannot contact the node. The request for status can fail with a timeout error because the node did not respond within a specific time period, the node could be down, or network connectivity is down.

 How to fix it 

If this is a new node, wait a few more minutes for the deployment to complete.
Getting help and support 

If you have problems with IBM® WebSphere® Application Server or questions about it, you can go directly to the [IBM Cloud® Support page](https://cloud.ibm.com/unifiedsupport/supportcenter) to review featured FAQs, view cloud status, or post questions on Stack Overflow. You can also open a support case.



*  You can check the status of the IBM Cloud platform and resources by going to the [Status page](https://cloud.ibm.com/status).





*  You can review [Stack Overflow](https://stackoverflow.com/search?q=ibm-cloud) to see whether other users ran into the same problem. When you use the forum to ask a question, tag your question with "ibm-cloud" so that it is seen by the IBM Cloud development teams.
*  If you still can't resolve the problem, you can open a support case. For information about opening a support case, or about case severities and response times, see [Working with support cases](https://cloud.ibm.com/docs/get-support?topic=get-support-open-case) or [Escalating support cases](https://cloud.ibm.com/docs/get-support?topic=get-support-escalation).



To get IBM software support updates, [subscribe to My Notifications and other communications](https://www.ibm.com/support/pages/node/718119).

Join the [IBM WebSphere, Liberty & DevOps Community](https://community.ibm.com/community/user/wasdevops/communities/websphere-home) or [other communities](https://community.ibm.com/community/user/sitemap) to collaborate and share knowledge via forums and blogs.
Then, similar to above, answer with Think when prompted for an event name.



Zoom

![Slack with the eventbot](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution19/Slackbot_event.png)

Slack with the eventbot





 Step 7: Remove resources 

To clean up the resources for this tutorial, go to the [IBM Cloud Resource List](https://cloud.ibm.com/resources). Locate the service instances of Watson Assistant and Db2 on Cloud and delete them. Similarly, locate the Code Engine project and delete it.

Depending on the resource it might not be deleted immediately, but retained (by default for 7 days). You can reclaim the resource by deleting it permanently or restore it within the retention period. See this document on how to [use resource reclamation](https://cloud.ibm.com/docs/account?topic=account-resource-reclamation).





 Related content 

Here are additional resources on the topics covered in this tutorial.



* [Build Great Chatbots, Fast](https://www.ibm.com/cloud/blog/build-great-chatbots-fast)
* [Tips and Tricks for Using the IBM Cloud CLI](https://www.ibm.com/cloud/blog/tips-and-tricks-for-using-the-ibm-cloud-cli)
If you migrated your cluster Ingress: You need to [refresh your blockchain console](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-manage-consoleibp-console-refresh).





 Why am I getting the error Unable to get system channel when I open my ordering service? 

 What’s happening 

After you create an ordering service, the status is Running. But when you open the ordering service you see the error:

Unable to get system channel. If you associated an identity without administrative privilege on the ordering service node,
you will not be able to view or manage ordering service details.

 Why it’s happening 

This problem can occur when the console has lost contact with your Kubernetes cluster on IBM Cloud. This can happen if your console has not recently communicated with your cluster, or if you have made changes to your cluster that have overridden the settings used by the IBM Blockchain platform.

 How to fix it 

You can renew the communication between your console and the IBM Kubernetes service cluster on IBM Cloud by clicking on the service instance of your console in your Resource list and clicking the Refresh cluster button. When the link between your cluster and your console has been refreshed, click the Launch the IBM Blockchain Platform button.





 Why did my smart contract installation, instantiation or upgrade fail? 

 What’s happening 

It is possible you may experience an error when installing, instantiating or upgrading a smart contract. For example, when you try to install a smart contract on a peer, it fails with the error An error occurred when installing smart contract on peer.

 Why it’s happening 

You may receive this error if this version of the smart contract already exists on the peer, or if your peer is out of resources.

 How to fix it 



* Open your Kubernetes dashboard and ensure the peer status is Running.
* Open the peer node and ensure the smart contract version does not already exist on the peer and try again with the proper version.
Getting help and support 

If you have problems or questions about using VLANs, you can get help by searching for information or by asking questions through a forum. You can also open an IBM Support case by opening the [IBM Cloud console](https://cloud.ibm.com/unifiedsupport/cases/add) and logging in to your account.

If you use the forum to ask a question, tag your question so that it is seen by the IBM Cloud development teams.

For more information about opening an IBM Support case, or about support levels and case severities, see [Contacting support](https://cloud.ibm.com/docs/get-support).