vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For cdr_logged events, the payload object contains data about a Call Detail Record (CDR) event that was handled by the phone integration. The structure of the payload object for a CDR event is as shown by this example:

{
"primary_phone_number": "+18005550123",
"global_session_id": "9caa8bad-aaa8-4a5a-a4b5-62bccc703d15",
"failure_occurred": false,
"transfer_occurred": false,
"active_calls": 0,
"warnings_and_errors": [
{
"code": "CWSMR0033W",
"message": "CWSMR0033W: The inbound RTP audio stream jitter of 43 ms exceeds the maximum jitter threshold of 30 ms."
},
{
"code": "CWSMR0070W",
The list items must match regular expression /^([0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}|default)$/. The maximum length is 201 items. The minimum length is 0 items.

--all-pages (bool)
: Invoke multiple requests to display all pages of the collection for secrets-locks.





 Example 

ibmcloud secrets-manager secrets-locks --offset=0 --limit=10 --search=example --groups=default





 Example output 

Example response for listing all Secrets and locks

{
"secrets_locks" : [ {
"secret_group_id" : "d8371728-95c8-4c12-b2af-1af98adb9e41",
"secret_id" : "0cf4addb-7a90-410b-a3a7-a15bbe2b7909",
"secret_type" : "imported_cert",
"secret_name" : "example-imported-certificate",
"versions" : {
"version_id" : "7bf3814d-58f8-4df8-9cbd-f6860e4ca973",
"version_alias" : "current",
"locks" : "lock-example-1", "lock-example-2" ]
} ]
} ],
"first" : {
"href" : "https://us-south.secrets-maanger.cloud.ibm.com/88b75b20-aa21-4174-85c9-1feb3cc93c9a/api/v2/secrets_locks?limit=50"
},
"previous" : {
"name": "my-volume"
},
"status": "failed",
"status_reasons":
{
"code": "source_volume_busy",
"message": "string",
"more_info": "https://cloud.ibm.com/docs/__TBD__"
}
],
"target_snapshot": {
"crn": "crn:v1:bluemix:public:is:us-south:a/123456::snapshot:f6bfa329-0e36-433f-a3bb-0df632e79263",
"deleted": {
"more_info": "https://cloud.ibm.com/apidocs/vpcdeleted-resources"
},
"href": "https://us-south.iaas.cloud.ibm.com/v1/snapshots/f6bfa329-0e36-433f-a3bb-0df632e79263",
"id": "f6bfa329-0e36-433f-a3bb-0df632e79263",
"name": "my-snapshot",
"resource_type": "snapshot"
}
}
] ! ! ,
"limit": 20,
"next": {
"href": "https://us-south.iaas.cloud.ibm.com/v1/backup_policies/7241e2a8-601f-11ea-8503-000c29475bed/jobss?start=9d5a91a3e2cbd233b5a5b33436855ed1&limit=20"
},
"total_count": 132
}
End Time 0001-01-01 00:00:00
Status In Progress

SNO Child Job Module ID Job Status Job ID
1 blueprint_delete job_in_progress us-east.JOB.Blueprint-Basic-Json.c64c45a1

Enter Job sequence number to get blueprint child job output summary(or enter no/n to ignore)> 1

Module ID
Status job_in_progress
Log Summary (last few lines)..........
2022/11/21 07:25:35 ----- New blueprint Action -----
2022/11/21 07:25:35 Request: blueprintId=blueprint_Basic.eaB.435a, account=1f7277194bb748cdb1d35fd8fb85a7cb, owner=test@in.ibm.com, requestID=a2a9922b-5a79-4700-88e3-efb2d3194fa9
2022/11/21 07:25:36 Related Job: jobID=us-east.JOB.Blueprint-Basic-Json.c64c45a1

Use ibmcloud schematics blueprint job logs --id us-east.JOB.Blueprint-Basic-Json.c64c45a1 to review the full job output
OK
Enter Job sequence number to get blueprint child job output summary(or enter no/n to ignore)> N





 ibmcloud schematics blueprint job list 

List all the Jobs for a blueprint.

Syntax

ibmcloud schematics blueprint job list --id BLUEPRINT_ID [--limit LIMIT] [--offset OFFSET] [--output OUTPUT]

Command options



Schematics blueprint job list flags

 Flag Required / Optional Description 

 --id or -i Required The ID of the blueprint. 
 --limit or -l Optional The maximum number of jobs to list. Ignored if a negative number is set. Maximum number to list is 200, the default is -1 
 --offset or -m Optional Offset in list.
The code extracts the fields of a United States phone number by using capturing groups:

create view Phone as
extract regex /(d{3})-(d{3}-d{4})/
on between 4 and 5 tokens in D.text
return
group 1 as areaCode
and group 2 as restOfNumber
and group 0 as fullNumber
from Document D;

Example 3: Applying multiple regex over input text

You can specify multiple regular expressions in the same extract regex statement by using the regexes syntax.

create view PhoneNum as
extract regexes
/(d{3})-(d{3}-d{4})/ and /[Xx]d{3,5}/
on between 1 and 5 tokens in D.text as num
from Document D;

Example 4: Misuse of grouping specification

The regular expression in this code sample does not contain group -1 or group 3000. This results in a compilation error.

create view ErrorExample as
extract regex /(d+)/
on D.text
return group -1 as wrongGroup and
group 3000 as nonExistentGroup
from Document D;







 Dictionaries 

Use the dictionary extraction specification to extract strings from input text that are contained in a dictionary of strings.



 Syntax 

dictionar[y|ies]
'<dictionary>'
[and '<dictionary>' and ... and '<dictionary>']
[with flags '<flags string>']





 Description 



* '<dictionary>'

References a dictionary that is created by using either the create dictionary statement, create external dictionary statement, or a dictionary file on the file system.
* [and '<dictionary>' and ... and '<dictionary>']

References additional dictionaries to be used for extraction.
* [with flags'<flags string>']

Controls dictionary matching. Currently, two options are supported:



* Exact

Provides exact, case-sensitive matching.
* IgnoreCase

Provides matching that is not case-sensitive.
"id": "r134-44e5e06b-9450-4f5f-a9be-96feebf770d8",
"length": 4096,
"name": "my-key1",
"public_key": "ssh-rsa AAAAB...n",
"resource_type": "key",
"type": "rsa"
}
]
}
Show more

If you have more than one SSH key, you can make a GET "http://169.254.169.254/metadata/v1/keys/{id}" call and provide the SSH key ID.





 Retrieve metadata about placement groups 

Make a GET "http://169.254.169.254/metadata/v1/placement_groups" call to retrieve information about placement groups configured for the instance. In the example, the return value of the cURL command is a list of placement groups, beginning with the first and up to 50. The output is parsed by jq.

curl -X GET "http://169.254.169.254/metadata/v1/placement_groups?version=2021-10-12" -H "Accept:application/json" -H "Authorization: Bearer $access_token" --data-urlencode "version=2021-10-12" -d '{
"start": "first",
"limit": 50
}' | jq -r

Example return:

{
"first": {
"href": "http://169.254.169.254/v1/placement_groups?limit=50"
},
"limit": 50,
"placement_groups": [
{
"created_at": "2021-10-12T19:55:00Z",
"crn": "crn:...]",
One way to prevent exceeding the connection limit and ensure that connections from your applications are being handled efficiently is through connection pooling. Connection pooling minimizes the number of active connections against your deployment. For more information, see [The Pooling of Connections in Redis ](https://medium.com/geekculture/the-pooling-of-connections-in-redis-e8188335bf64) and [Connection Pools.](https://medium.com/geekculture/the-pooling-of-connections-in-redis-e8188335bf64)





 Redis Allowlisting 

You can also use allowlisting to manage and/or limit connections to your Redis deployment. For more information, see [Allowlisting](https://cloud.ibm.com/docs/databases-for-redis?topic=databases-for-redis-allowlisting).
"rtype": "A",
"ttl": 300,
"name": "www.example.com",
"id": "A:fa57d5d0-7729-4770-af27-6d7f8dce860c",
"rdata": {
"ip": "9.4.6.7"
}
}







 Listing resource records 



 Request 

curl -X GET $DNSSVCS_ENDPOINT/v1/instances/$INSTANCE_ID/dnszones/$DNSZONE_ID/resource_records?limit=50&offset=0 -H "Authorization: $TOKEN"





 Response 

{
"offset": 0,
"limit": 50,
"total_count": 1,
"first": {
"href": "https://api.dns-svcs.cloud.ibm.com/v1/instances/ec0c4ee2-5d1f-4066-bcf2-dc9f3122c638/dnszones/example.com:4759caa4-d4fa-4fb9-7848-f463de19b392/resource_records?limit=50"
},
"resource_records": [
{
"created_on": "2019-08-30 04:10:25.092468565 +0000 UTC",
"modified_on": "2019-08-30 04:10:25.092468565 +0000 UTC",
"rtype": "A",
"ttl": 60,
"name": "www.example.com",
"id": "A:ec0c4ee2-5d1f-4066-bcf2-dc9f3122c639",
"rdata": {
"ip": "192.168.10.100"
}
}
]
}







 Updating a resource record 



 Request
System limits were reached 

  What’s happening 

Your function is not running properly and might result in a message like {"error":"signal: killed"}.

  Why it’s happening 

All functions have minimum and maximum [system limits](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-limits), such as memory usage maximum or a timeout.

  How to fix it 

Some limits can be increased if a business case can justify higher safety limit values. To increase the limit value, contact IBM support by opening a ticket directly from the IBM Cloud Functions web console.



1.  Select Support.
2.  Select Add Ticket from the drop-down menu.
3.  Select Technical for the ticket type.
4.  Select Functions for Technical area of support.
30.680738551593496,"wq17":30.71349017105434,"wq18":31.477300050648395,"wq19":32.770080232722506,"wq2":31.750878557300048,"wq20":31.17622390735678,"wq21":31.77096492775866,"wq22":31.28018420436051,"wq23":32.75850219945344,"wq24":31.5657009671141,"wq25":30.77038049714973,"wq26":30.51074908007705,"wq3":32.65164392241311,"wq4":31.158951304483924,"wq5":32.155248351901555,"wq6":31.334700799475687,"wq7":30.677429386020442,"wq8":31.532804418562414,"wq9":30.81365854722067}},"local":false,"max_experiments":300,"max_shots":100000,"meas_kernels":["hw_qmfk"],"meas_levels":[1,2],"meas_lo_range":[6.682176913,7.682176913],6.785029648,7.785029648],6.65665742,7.65665742],6.782378059,7.782378059],6.730041176,7.730041176],6.735190703,7.735190703],6.854339834
"crn": "crn:v1:bluemix:public:hs-crypto:us-south:a/f047b55a3362ac06afad8a3f2f5586ea:30372f20-d9f1-40b3-b486-a709e1932c9c:key:2291e4ae-a14c-4af9-88f0-27c0cb2739e2",
"createdBy": "...",
"creationDate": "2020-03-12T03:50:12Z",
"lastUpdateDate": "2020-03-12T03:50:12Z",
"algorithmMetadata": {
"bitLength": "256",
"mode": "CBC_PAD"
},
"extractable": true,
"imported": false,
"algorithmMode": "CBC_PAD",
"algorithmBitSize": 256,
"dualAuthDelete": {
"enabled": false
}
}
]
}

By default, GET api/v2/keys returns your first 200 keys, but you can adjust this limit by using the limit parameter at query time. To learn more about limit and offset, see [Retrieving a subset of keys](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-view-keysretrieve-subset-keys-api).

Not seeing the full list of keys? You might need to use limit and offset or check with your administrator to ensure you're assigned the correct level access to keys in your instance. To learn more, see [Unable to view or list keys](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-troubleshoot-unable-to-list-keys-api).







 Retrieving a subset of keys
Customer-managed encryption No No Yes <br><br>[4] No 
 Fine-grained access control Yes Yes Yes Yes 
 Activity tracker events No Yes Yes No 
 Monitoring Event Streams metrics by using IBM Cloud Monitoring Yes Yes Yes Yes 
 Cloud Service Endpoint support No No Yes Not applicable 
 Scale plan capacity No No Yes No 
 Maximum number of partitions 1 <br><br>[5] 100 3000 - 9000 scales with throughput <br><br>[6] 3000 
 Maximum retention limits 100 MB for the partition 1 GB per partition 2 TB - 12 TB of scalable usable storage <br><br>[7] 2 TB of usable storage 
 Maximum throughput 100 KB per second per partition 1 MB per second per partition (20 MB per service instance) 150 MB/s - 450 MB/s of scalable throughput <br><br>[8] 150 MB/s <br><br>[9] 
 Maximum message size 1 MB 1 MB 1 MB 1 MB 
 Maximum number of connected clients 5 500 10 000 10 000 
 Location (region) availability Dallas (us-south) Multizone location (MZR) <br>Dallas (us-south) <br>Washington (us-east) <br>London (eu-gb) <br>Sydney (au-syd) <br>Frankfurt (eu-de) <br>Tokyo (jp-tok) <br>Osaka (jp-osa) <br>Toronto (ca-tor) <br>Sao Paulo (br-sao) Multizone location (MZR) <br>Dallas (us-south) <br>Washington (us-east) <br>London (eu-gb) <br>Sydney (au-syd) <br>Frankfurt (eu-de) <br>Tokyo (jp-tok) <br>Osaka (jp-osa) <br>Toronto (ca-tor) <br>Sao Paulo (br-sao)<br><br>Single zone location (SZR) <br>Chennai (che01) Your Satellite location managed in <br>Dallas <br>Washington <br>London <br>Sydney <br>Frankfurt <br>Tokyo <br>Osaka <br>Toronto <br>Sao Paulo
* Updates the UBI to version 8.7-1085.
* Updates Go to version 1.19.6.
* Sets the default values for CPU limit & Memory limit to 500m & 500Mi respectively.







 Revision 19, released 20 February 2023 



* Resolves the following CVEs: [CVE-2022-47629](https://nvd.nist.gov/vuln/detail/CVE-2022-47629)
* Updates the UBI to version 8.7-1049.1675784874.
* Updates Go to version 1.18.9.









 Version 4.8 



 Revision 22, released 04 April 2023 



* Resolves the following CVEs: [CVE-2022-4304](https://nvd.nist.gov/vuln/detail/CVE-2022-4304)[CVE-2022-4450](https://nvd.nist.gov/vuln/detail/CVE-2022-4450)[CVE-2023-0215](https://nvd.nist.gov/vuln/detail/CVE-2023-0215)[CVE-2023-0286](https://nvd.nist.gov/vuln/detail/CVE-2023-0286)
* Updates the UBI to version 8.7-1085.1679482090.
* Updates Go to version 1.19.7.







 Revision 21, released 21 March 2023 



* Resolves the following CVEs: [CVE-2023-23916](https://nvd.nist.gov/vuln/detail/CVE-2023-23916)
* Updates the UBI to version 8.7-1085.
* Updates Go to version 1.19.6.







 Revision 20, released 06 March 2023
* Updates the UBI to version 8.7-1085.
* Updates Go to version 1.19.6.







 Revision 1, released 20 February 2023 



* Resolves the following CVEs: [CVE-2022-47629](https://nvd.nist.gov/vuln/detail/CVE-2022-47629)
* Updates the UBI to version 8.7-1049.1675784874.
* Updates Go to version 1.18.9.
* Initial release.









 Version 22.04 



 Revision 19, released 19 June 2023 



* Resolves the following CVEs: [CVE-2022-43552](https://nvd.nist.gov/vuln/detail/CVE-2022-43552)[CVE-2022-3204](https://nvd.nist.gov/vuln/detail/CVE-2022-3204)[CVE-2023-27535](https://nvd.nist.gov/vuln/detail/CVE-2023-27535)[CVE-2022-36227](https://nvd.nist.gov/vuln/detail/CVE-2022-36227)[CVE-2022-35252](https://nvd.nist.gov/vuln/detail/CVE-2022-35252)
* Updates the UBI to version 8.8-860.







 Revision 18, released 21 April 2023 



* Resolves the following CVEs: [CVE-2023-0361](https://nvd.nist.gov/vuln/detail/CVE-2023-0361)
* Updates the UBI to version 8.7-1107.
* Ignore aggregate usage limit if set to 0%







 Revision 17, released 4 April 2023
![Genesys create flow](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/phone-genesys-flow.png)



1. In the toolbox, click Task and drag it into Reusable Tasks.



![Genesys task](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/phone-genesys-task.png)



1. From your toolbox, under Data, drag a Set Participant Data widget into the first action. Click on the widget and specify an attribute named uuiData. For the value to assign, choose the Expression type and specify Call.UUIData.



![Genesys Set participant data widget](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/phone-genesys-set-participant-data-widget.png)



1. From your toolbox, under Transfer, drag the Transfer to ACD widget into the first action.



![Genesys transfer widget](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/phone-genesys-transfer-widget.png)



1. Select the queue you want to use.
2. In the toolbox, click the Disconnect widget and drag it into the action after Failure. (This disconnects the call if the transfer fails.)
3. Click the three dots under Reusable tasks and click Set this as the starting task.
Create a new queue and give it a descriptive name.
4. Add yourself as a member.
5. Click Save.



3. Create a simple call flow. Your business might already have something more complex for routing.



1. Click Admin.
2. Click Architect.
3. In the Flows: Inbound Call section, click + to create a new flow. Give it a descriptive name (for example, Escalate to Agent).



![Genesys create flow](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/phone-genesys-flow.png)



1. In the toolbox, click Task and drag it into Reusable Tasks.



![Genesys task](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/phone-genesys-task.png)



1. From your toolbox, under Transfer, drag the Transfer to ACD widget into the first action.



![Genesys transfer widget](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/phone-genesys-transfer-widget.png)



1. Select the queue you want to use.
2. In the toolbox, click the Disconnect widget and drag it into the action after Failure. (This disconnects the call if the transfer fails.)
3. Click the three dots under Reusable tasks and click Set this as the starting task. You can remove the Initial Greeting, because your assistant will speak before handing off the call.
4.
If You fail to do so, or fail to respond within five business days of IBM Cloud inquiring as to the validity of Your information, You will be in material breach of this Agreement.

You agree that for each domain name You register, the following information will be made publicly available in the Whois directory, and may be sold in bulk, as set forth by ICANN policy and the ICANN agreement:



* The domain name
* Your name and postal address
* The email address, postal address, voice and fax numbers for technical and administrative contacts
* The Internet protocol numbers for the primary and secondary name servers
* The corresponding names of the name servers
* The original date of registration and expiration date



You agree that, to the extent permitted by ICANN, IBM Cloud may make use of the publicly available information You provided during the registration process. If You engage in the reselling of domain names, You agree to obtain informed consent, and evidence of consent, from those individuals about the possible use of the personal information they provide, pursuant to ICANN policy.





 Transfer of Domain Names 

If You transfer any domain name, You agree to abide by the procedures and conditions set forth in this Agreement. Any domain registered with IBM Cloud or transferred to IBM Cloud will be placed on lock status. The domain must be placed in unlock status in order to modify any of the Whois information, including the name servers, or initiate a transfer of the domain name away from IBM Cloud to a new Registrar.

You agree that, prior to transferring ownership of a domain name to another person (the “Transferee”), You will require the Transferee to agree in writing to be bound by all the terms and conditions of this Agreement. If the Transferee does not do so, the transfer will be null and void. You explicitly authorize IBM Cloud and its agents to act as Designated Agent, as stipulated by ICANN Transfer Policy, to approve a change of registrant on Your behalf.





 Resale Practices 

If any customers of Yours acquire domain names through You using IBM Cloud’s registration services, You hereby agree as follows:



* You will obtain each of Your customer’s acceptance of IBM Cloud's then-current Domain Registration Agreement, and will retain evidence of their acceptance for at least a period of not less than three years.
When failures occur on the management components, you can restore the management components to a previous backup by using the Veeam console. For more information about restoring manually, see the [Veeam technical instructions](https://helpcenter.veeam.com/backup/vsphere/performing_full_recovery.html).





 Applying updates to Veeam 

You are responsible for maintaining the Veeam software to keep it updated to the most recent version.



 Applying updates to instances deployed as a VM with public and private network 

If the Veeam service is installed on an instance as a VM with public and private network, you can check for and download the updates by using the Veeam software itself.





 Applying updates to instances deployed as a bare metal server or VSI, or deployed as a VM with private network only 

If the Veeam service is installed on an instance as a bare metal server or VSI, or deployed as a VM with private network only, you cannot check for or download updates by using the Veeam software. The reason is because the Veeam VSI or VM is configured with no public network access. Instead, you must download updates from the Veeam website, transfer them to the Veeam VM, and then install them.





 Updating Veeam licenses for instances that are deployed with public and private network 

If the Veeam service is installed on an instance with public and private network, you can update your Veeam 9.5u4b license either automatically or manually. For Veeam, you must update your Veeam license automatically. You cannot update it manually. Follow the Veeam instructions at [Updating license](https://helpcenter.veeam.com/docs/backup/vsphere/license_update.html).





 Updating Veeam licenses for instances that are deployed as a bare metal server or VSI, or deployed as a VM with private network only 

If the Veeam service is deployed on an instance as a bare metal server or VSI, or is deployed as a VM with private network only, take note of the expiration date for your license.
AsperaTransaction asperaTransaction = asperaTransactionFuture.get();

while (!asperaTransaction.isDone()) {
TransferProgress transferProgress = asperaTransaction.getProgress();

System.out.println("Bytes transferred: " + transferProgress.getBytesTransferred());
System.out.println("Percent transferred: " + transferProgress.getPercentTransferred());

//pause for 3 seconds
Thread.sleep(1000 * 3);
}





 Pause/Resume/Cancel 

The SDK provides the ability to manage the progress of file/directory transfers through the following methods of the AsperaTransfer object:



* pause()
* resume()
* cancel()



There are no side-effects from calling either of the methods outlined above. Proper clean up and housekeeping is handled by the SDK.

The following example shows a possible use for these methods:

String bucketName = "<bucket-name>";
String directoryPath = "<absolute-path-to-directory>";
String directoryPrefix = "<virtual-directory-prefix>";
boolean includeSubDirectories = true;

AsperaTransferManager asperaTransferMgr = new AsperaTransferManagerBuilder(COS_API_KEY_ID, _cos)
.withTokenManager(TOKEN_MANAGER)
.build();

File outputDirectory = new File(directoryName);

System.out.println("Starting directory download...");

//download the directory from cloud storage
Future<AsperaTransaction> asperaTransactionFuture = asperaTransferMgr.downloadDirectory(bucketName, directoryPrefix, outputDirectory, includeSubDirectories);