vania-janet/multiturn-rag-retrieval-data huggingface dataset:
From the IBM Cloud console menu bar, click the Help icon ![Help icon](https://cloud.ibm.com/icons/help.svg) > Support center. The options that are available to you depend on your support plan. For more information, see [Getting support](https://cloud.ibm.com/docs/get-support?topic=get-support-support-plans).

To contact support, you can use the following methods:



* If you have a valid Pay-As-You-Go or Subscription account, you can click Chat with IBM to connect with a support engineer.
* Pay-as-you-go or subscription accounts can also contact support by phone and can find the number in the [Support Center](https://cloud.ibm.com/unifiedsupport/supportcenter).
* Lite and Trial account support is limited to non-technical support issues that are related to account access and billing. Users with Lite or Trial accounts can view the [IBM Cloud documentation](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar), Chat with Watson, and use [Stack Overflow](https://stackoverflow.com/questions/tagged/ibm-cloud).



* How do I escalate support cases?

As an IBM Cloud customer, you can escalate support cases to surface critical issues. After a case is escalated, the IBM Cloud Support team reviews the information and responds with updates. For information about case severity, see [Case severity and initial response times](https://cloud.ibm.com/docs/get-support?topic=get-support-support-case-severity).

To escalate a case, complete the following steps:



1. Contact IBM Cloud Support by phone or chat:



* Pay-as-you-go or subscription accounts can contact support by phone and can find the number in the [Support Center](https://cloud.ibm.com/unifiedsupport/supportcenter).
If you do not take action, the same text response is displayed a second time to let users know they have returned to the node they digressed away from. You can make it clearer to users that they have returned to the original conversation thread by specifying a unique message to be displayed when they return.

For example, if the original text response for the node is, What's the order number?, then you might want to display a message like, Now let's get back to where we left off. What is the order number? when users return to the node.

To do so, use the following syntax to specify the node text response:

<? (returning_from_digression)? "post-digression message" : "first-time message" ?>

For example:

<? (returning_from_digression)? "Now, let's get back to where we left off.
What is the order number?" : "What's the order number?" ?>

You cannot include SpEL expressions or shorthand syntax in the text responses that you add. In fact, you cannot use shorthand syntax at all. Instead, you must build the message by concatenating the text strings and full SpEL expression syntax together to form the full response.

For example, use the following syntax to include a context variable in a text response that you would normally specify as, What can I do for you, $username?:

<? (returning_from_digression)? "Where were we, " +
context"username"] + "? Oh right, I was asking what can I do
for you today." : "What can I do for you today, " +
context"username"] + "?" ?>

For full SpEL expression syntax details, see Expression for accessing objects]] ! ! ! ! ! .
* Preventing returns: In some cases, you might want to prevent a return to the interrupted conversation flow based on a choice the user makes in the current dialog flow.
Getting help and support 

If you have problems or questions when using the IBM Cloud Security and Compliance Center Workload Protection service, you have several options to get help with determining the cause of the problem and finding a solution. If you're logged in, you can go directly to the [Support center](https://cloud.ibm.com/unifiedsupport/supportcenter) to review common FAQs, open a support case, or search community content.



 Using the Support Center search field 

You can use the Support Center search field to find answers to your questions from across the IBM Cloud documentation and Stack Overflow forum. You can also manage support cases from the Support Center. You can find links to both the Stack Overflow forum for technical questions and the developerWorks (IBM Developer Answers) forum for all other questions under the Forums section of the Support Center.

To access the Support Center, log in to the IBM Cloud console, and click Support from the menu bar.

If you have a basic, advanced, or premium [support plan](https://cloud.ibm.com/docs/get-support?topic=get-support-support-planssupport-plans), you can find call-in numbers and a chat option to get help.

The Support Center is the preferred method for getting support, but if you can't log in to IBM Cloud, you can use the [New support case](https://cloud.ibm.com/unifiedsupport/cases/add) page to submit a case.





 Searching forums 

You can search forums to find answers to your questions. The Stack Overflow forum, for technical questions, and the IBM Developer Answers forum, for general questions, both provide a wide variety of searchable answers to your IBM Cloud questions.

If you don't find an existing answer to a question, ask a new one.

You can access Stack Overflow and IBM Developer Answers from the Support Center, or use the following links:



* Go to [Stack Overflow](https://stackoverflow.com/questions/tagged/ibm-cloud) to ask technical questions about the IBM Cloud Security and Compliance Center Workload Protection service.
Table 2. Event Notifications severity to PagerDuty severity mapping

 Event Notifications severity PagerDuty severity 

 Critical Critical 
 High Error 
 Medium Warning 
 Low Info 
 Anything Else Info 







 PagerDuty retry policy 

When calling a webhook, issues such as network errors and application glitches can cause the requests to fail. A retry is used to provide resiliency to external requests. Attempt to retry the requests in such situations by using the following values:



* Limit = 60 seconds: total time that the service retries.
* Step = 5 seconds: after each failure, the service waits 5 seconds before retrying. This delay prevents bombarding of the external services (PagerDuty).



In addition, the following timeout conditions cause the PagerDuty call to fail:



* A connection timeout of 10 seconds
* A response timeout of 60 seconds



If a call to the PagerDuty URL fails even after retry attempts, the notification is lost.
For more information, see [Inactivity timeout](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-inputtimeouts-inactivity).



Table 11. The inactivity_timeout parameter

 Availability and usage Description 

 Previous-generation models Generally available for all languages. 
 Next-generation models Generally available for all languages. 
 WebSocket Parameter of JSON start message 
 Synchronous HTTP Query parameter of POST /v1/recognize method 
 Asynchronous HTTP Query parameter of POST /v1/recognitions method 







 interim_results 

An optional boolean that directs the service to return intermediate hypotheses that are likely to change before the final transcript. By default (false), interim results are not returned. Interim results are available only with the WebSocket interface. For more information, see [Interim results](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-interiminterim-results).



Table 12. The interim_results parameter

 Availability and usage Description 

 Previous-generation models Generally available for all languages. 
 Next-generation models Generally available for next-generation models that support low latency, but only if both the interim_results and low_latency parameters are set to true. For more information, see [Requesting interim results and low latency](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-interiminterim-low-latency). 
 WebSocket Parameter of JSON start message 
 Synchronous HTTP Not supported 
 Asynchronous HTTP Not supported 







 keywords 

An optional array of keyword strings that the service spots in the input audio. By default, keyword spotting is not performed. For more information, see [Keyword spotting](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-spottingkeyword-spotting).



Table 13. The keywords parameter

 Availability and usage Description
Go to Message > Response > output > MessageOutput > generic > RuntimeResponseTypeSearch in [Watson Assistant v2 API](https://cloud.ibm.com/apidocs/assistant-v2message-response) to view how response_type search renders when search_skill response is processed..





 Example 

This example uses the user input text to send a natural-language query to the search skill.

{
"output": {
"generic": [
{
"response_type": "search_skill",
"query": "",
"query_type": "natural_language"
}
]
}
}







 connect_to_agent 

Requests that the conversation be transferred to a service desk agent for help.



 Fields 



 Name Type Description Required? 

 response_type string connect_to_agent Y 
 message_to_human_agent string A message to display to the live agent to whom the conversation is being transferred. Y 
 agent_available string A message to display to the user when agents are available. Y 
 agent_unavailable string A message to display to the user when no agents are available. Y 
 transfer_info object Information used by the web chat service desk integrations for routing the transfer. N 
 transfer_info.target.zendesk.department string A valid department from your Zendesk account. N 
 transfer_info.target.salesforce.button_id string A valid button ID from your Salesforce deployment. N 







 Example 

This example requests a transfer to a live agent and specifies messages to be displayed both to the user and to the agent at the time of transfer.

{
"output": {
"generic": [
{
"response_type": "connect_to_agent",
"message_to_human_agent": "User asked to speak to an agent.",
"agent_available": {
"message": "Please wait while I connect you to an agent."
},
"agent_unavailable": {
Be sure to include the workspace ID and the append=true flag, as in this example:



curl -X POST -H "content-type: application/json" -H "accept: application/json" -u "apikey:{apikey}" -d@./skill.json "url/api/v1/workspaces/{workspace_id}?version=2019-02-28&append=true"
* The training process takes a long time and appears stuck

If the training process gets stuck, first check whether there is an outage for the service by going to the [Cloud status page](https://cloud.ibm.com/status). You can start a new training process to stop the current process and start over. To do so, add a new intent or entity, and then delete it. This action starts a new training process.
* Is there a range of IP addresses that are being used by a webhook?

Unfortunately, the IP address ranges from which Watson Assistant may call a webhook URL are subject to change, which in turn prevent using them in any static firewall configuration. Please use the https transport and specify an authorization header to control access to the webhook.
* How do I see my monthly active users in Watson Assistant?

To see your monthly active users (MAU) do the following:



1. Sign in to [https://cloud.ibm.com](https://cloud.ibm.com)
2. Click on the Manage menu, then choose Billing and usage.
3. Click on Usage.
4. For Watson Assistant, select View Plans.
5. Under Time Frame, select the month you need.
6. Select your Plus plans or Plus Trial plans to see monthly active users and the API calls.



* Error: New Off Topic not supported

You see the error New Off Topic not supported after editing the JSON file for a dialog skill and changing the skill language from English to another language.

To resolve this issue, modify the JSON file by setting off_topic to false.
Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2020E 

Message: The "{0}" resource doesn't exist.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2021E 

Message: The "{0}" starter directory doesn't exist.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2022E 

Message: The starters could not be copied.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2023E 

Message: The VCAP_SERVICES environment variable isn't defined.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2024E 

Message: Self registration for users isn't enabled.

Contact the account owner.





 BXNUI2025E 

Message: During an attempt to build an entity tag for web caching, an error occurred. IBM Cloud could not determine whether an icon was cached.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2026E 

Message: Another user already uses that name.

Try again with a different user name.





 BXNUI2027E 

Message: No user is logged in.

Log in and try again.





 BXNUI2028E 

Message: Cloud Foundry issued an unexpected exception with this message: "{0}"

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2029E 

Message: The cloud information could not be retrieved.
For more information, see [Processing metrics](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-metricsprocessing-metrics).



Table 20. The processing_metrics_interval parameter

 Availability and usage Description 

 Previous-generation models Generally available for all languages. 
 Next-generation models Not available. 
 WebSocket Parameter of JSON start message 
 Synchronous HTTP Not supported 
 Asynchronous HTTP Query parameter of POST /v1/recognitions method 







 profanity_filter 

An optional boolean that indicates whether the service censors profanity from a transcript. By default (true), profanity is filtered from the transcript. For more information, see [Profanity filtering](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-formattingprofanity-filtering).



Table 21. The profanity_filter parameter

 Availability and usage Description 

 Previous-generation models Generally available for US English and Japanese. 
 Next-generation models Generally available for US English and Japanese. 
 WebSocket Parameter of JSON start message 
 Synchronous HTTP Query parameter of POST /v1/recognize method 
 Asynchronous HTTP Query parameter of POST /v1/recognitions method 







 redaction 

An optional boolean that indicates whether the service redacts numeric data with three or more consecutive digits from a transcript. By default (false), numeric data is not redacted. If you set the redaction parameter to true, the service automatically forces the smart_formatting parameter to be true, and it disables the keywords, keywords_threshold, max_alternatives, and (for the WebSocket interface) interim_results parameters. For more information, see [Numeric redaction](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-formattingnumeric-redaction).



Table 22. The redaction parameter

 Availability and usage Description
* You can include search skill response types in dialog nodes that the phone integration will read. The introductory message (I searched my knowledge base and so on), and then the body of only the first search result is read.

The search skill 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 dialog response types, see [Rich responses](https://cloud.ibm.com/docs/assistant?topic=assistant-dialog-overviewdialog-overview-multimedia).

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

If you want to use the same dialog for an assistant that you deploy to many different platforms, you can add custom responses per integration type. Add a conditioned response that tells the assistant to show the response only when the phone integration is being used. For more information, see [Building integration-specific responses](https://cloud.ibm.com/docs/assistant?topic=assistant-dialog-integrationsdialog-integrations-condition-by-type).





 Setting up a SIP trunk 

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:



* [Create a Twilio SIP trunk](https://cloud.ibm.com/docs/assistant?topic=assistant-deploy-phonedeploy-phone-twilio-setup)
* [Use other third-party providers](https://cloud.ibm.com/docs/assistant?topic=assistant-deploy-phonedeploy-phone-request-setup)
If none of these leads to a resolution, attempt to gather the following information before contacting support:



* An MTR or traceroute from your origin web server to a CIS IP address that most commonly connected to your origin web server before the issue occurred Identify a connecting CIS IP recorded in the origin web server logs
* Any relevant details from the origin logs









 Error 523: origin is unreachable 

Error 523 occurs when CIS can't contact your origin web server. This occurs when a network device between CIS and the origin web server doesn’t have a route to the origin’s IP address.



 Error 523 resolution 

Check your origin web server error logs to eliminate these common causes at your origin web server:



* Confirm the correct origin IP address is listed for A or AAAA records
* Troubleshoot internet routing issues between your origin and CIS, or with the origin itself



If none of the previous tips leads to a resolution, request an MTR or traceroute from your origin web server to a CIS IP address that most commonly connected to your origin web server before the issue occurred. Identify a connecting CIS IP from the logs of the origin web server.







 Error 524: a timeout occurred 

Error 524 indicates that the connection to the origin web server was established successfully, but the origin did not provide an HTTP response before the connection timed out. The default timeout is 100 seconds.

Enterprise plans can increase the 524 timeout up to 600 seconds.



 Error 524 resolution 

Check your origin web server error logs to eliminate these common causes at your origin web server:



* A long-running process on the origin web server
* An overloaded origin web server



Logging request response time at your origin web server helps identify the cause of resource slowness.

If you regularly run HTTP requests that take over 100 seconds to complete (for example large data exports), move those processes behind a subdomain that is not proxied.







 Error 525: SSL handshake failed 

525 errors are often caused by a configuration issue on the origin web server. Error 525 occurs when these two conditions are true:



1. The SSL handshake fails between CIS and the origin web server
2.
Try again in a few minutes. If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 vpn_gateway_not_updated 

Message: The VPN gateway <vpn_gateway_id> could not be updated.

Try again in a few minutes. If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 vpn_gateway_subnet_not_found 

Message: Could not find the subnet <subnet_id> for the given VPN gateway.

You've referenced a subnet that does not exist. Review your request to ensure that you specified the proper subnet ID. Try again in a few minutes. If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 vpn_gateway_subnet_status_error 

Message: The VPN gateway could not be created due to subnet status.

Provide a subnet that is in available status. Try again in a few minutes. If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 vpn_gateways_quota_exceeded 

Message: The VPN Gateway cannot be created because your account and/or the region has reached the quota.

The quotas per resource are specified on the [Quotas](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-quotasvpn-quotas) page.

To view the current VPN gateways, use the GET /vpn_gateways API. Equivalent CLI command: ibmcloud is vpn-gateways
Getting help and support 

If you have problems or questions, you can get help by searching for information or by asking questions through one of the following forums. You can also create a case in the [IBM Cloud console](https://cloud.ibm.com/unifiedsupport/supportcenter).

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



*  If you have technical questions about virtual servers, post your question on [Stack Overflow](http://stackoverflow.com/search?q=virtual-servers+ibm-cloud) and tag your question with "ibm-cloud" and "virtual-servers".
*  For questions about the service and getting started instructions, use the [IBM Developer Answers](https://developer.ibm.com/answers/topics/virtual-servers.html) forum. Make sure to include the "virtual servers" and "ibm cloud" tags.
If you have correct authorization but you are still getting this error, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 not_found 

Message: Please check whether the resource you are requesting exists.

You referenced a resource that does not exist or one to which you do not have access. Review your request to ensure that you specified the proper IDs and references.

If the resource is an operating system, you can use the request, GET /v1/operating_systems to list valid options. For more information, see [Retrieves all operating systems](https://cloud.ibm.com/apidocs/vpcretrieves-all-operating-systems).

Refer to the [API documentation](https://cloud.ibm.com/apidocs/vpc-on-classic) for additional help. If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 not_implemented 

Message: None

The method is not implemented. Check your request to make sure you are calling a [valid API](https://cloud.ibm.com/apidocs/vpc-on-classic). [Contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support) if you expect this API to be implemented.





 not_in_address_prefix 

Message: The provided CIDR does not fit in any of the address prefixes in the provided zone.

This error occurs if a user is trying to create a subnet with a CIDR that does not fall into any address prefixes for the given zone.

Run GET /vpcs/{vpc_id}/address_prefixes to get the list of address prefixes for the VPC. If using the CLI, you can run ibmcloud is vpc-address-prefixes to list all address prefixes for your VPC.
User-to-User: dev::latest::212033::0a64c30d-c558-4055-85ad-ef75ad6cc29d::978f1fd7-4e24-47d8-adb0-24a8a6eff69e::b5ffd6c2-902f-4658-b586-e3fc170a6cf3::7ad616a350cc48078f17e3ee3df551de;encoding=ascii
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;encoding=hex;
X-Watson-Assistant-Session-History-Key: dev::latest::212033::0a64c30d-c558-4055-85ad-ef75ad6cc29d::978f1fd7-4e24-47d8-adb0-24a8a6eff69e::b5ffd6c2-902f-4658-b586-e3fc170a6cf3::7ad616a350cc48078f17e3ee3df551de