Skip to content

Commit 0c0351b

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into 304195
2 parents 441db21 + 618814b commit 0c0351b

26 files changed

+115
-110
lines changed

articles/communication-services/concepts/call-automation/call-automation.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -147,6 +147,7 @@ The Call Automation events are sent to the web hook callback URI specified when
147147
| ----------------- | ------------ |
148148
| CallConnected | The call has successfully started (when using Answer or Create action) or your application has successfully connected to an ongoing call (when using Connect action)|
149149
| CallDisconnected | Your application has been disconnected from the call |
150+
| CreateCallFailed (in preview)| The call that your application has initiated could not be created |
150151
| ConnectFailed | Your application failed to connect to a call (for connect call action only)|
151152
| CallTransferAccepted | Transfer action has successfully completed and the transferee is connected to the target participant |
152153
| CallTransferFailed | The transfer action has failed |

articles/communication-services/how-tos/call-automation/actions-for-call-control.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -166,6 +166,8 @@ The response provides you with CallConnection object that you can use to take fu
166166
2. `ParticipantsUpdated` event that contains the latest list of participants in the call.
167167
![Sequence diagram for placing an outbound call.](media/make-call-flow.png)
168168

169+
In the case where the call fails, you will receive a `CallDisconnected` and `CreateCallFailed` event with error codes for further troubleshooting.
170+
169171
## Connect to a call (in preview)
170172

171173
Connect action enables your service to establish a connection with an ongoing call and take actions on it. This is useful to manage a Rooms call or when client applications started a 1:1 or group call that Call automation isn't part of. Connection is established using the CallLocator property and can be of types: ServerCallLocator, GroupCallLocator, and RoomCallLocator. These IDs can be found when the call is originally established or a Room is created, and also published as part of [CallStarted](./../../../event-grid/communication-services-voice-video-events.md#microsoftcommunicationcallstarted) event.

articles/communication-services/how-tos/call-automation/handle-events-with-event-processor.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ CreateCallEventResult eventResult = await createCallResult.WaitForEventProcessor
6969
CallConnected returnedEvent = eventResult.SuccessResult;
7070
```
7171

72-
With EventProcessor, we can easily wait CallConnected event until the call is established. If the call was never established (that is, callee never picked up the phone), it throws Timeout Exception.
72+
With EventProcessor, we can easily wait CallConnected event until the call is established. If the call was never established (that is, callee never picked up the phone), it throws Timeout Exception. If the creation of the call otherwise fails, you will receive the `CallDisconnected` and `CreateCallFailed` events with error codes to further troubleshoot.
7373

7474
> [!NOTE]
7575
> If specific timeout was not given when waiting on EventProcessor, it will wait until its default timeout happens. The default timeout is 4 minutes.

articles/communication-services/resources/troubleshooting/voice-video-calling/includes/codes/call-automation-sdk.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,4 +28,5 @@ The following error codes are exposed by the Call Automation SDK.
2828
| | 500 | Internal server error | | Retry after a delay. If it persists, raise a support ticket. |
2929
| | 500 | Play Failed | | File a support request through the Azure portal. |
3030
| | 500 | Recognize Failed | | Check error message and confirm the audio file format is valid (WAV, 16 KHz, Mono). If the file format is valid, file a support request through Azure portal. |
31-
| | 502 | Bad gateway | | Retry after a delay with a fresh http client. |
31+
| | 502 | Bad gateway | | Retry after a delay with a fresh http client. |
32+
| | 503,504 | Communication Services infrastructure error. | | File a support request through the Azure portal. |

articles/load-balancer/ipv6-add-to-existing-vnet-cli.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Add IPv6 to an IPv4 application in Azure virtual network - Azure CLI
33
titlesuffix: Azure Load Balancer
4-
description: This article shows how to deploy IPv6 addresses to an existing application in Azure virtual network using Azure CLI.
4+
description: This article shows how to deploy IPv6 addresses to an existing application in an Azure virtual network for a Standard Load Balancer using Azure CLI.
55
author: mbender-ms
66
ms.service: azure-load-balancer
77
ms.topic: how-to

articles/network-watcher/vpn-troubleshoot-overview.md

Lines changed: 23 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: halkazwini
66
ms.author: halkazwini
77
ms.service: azure-network-watcher
88
ms.topic: concept-article
9-
ms.date: 02/22/2024
9+
ms.date: 09/12/2024
1010

1111
#CustomerIntent: As an Azure administrator, I want to learn about VPN troubleshoot so I can use it to troubleshoot my VPN virtual network gateways and their connections whenever resources in a virtual network can't communicate with on-premises machines over a VPN connection.
1212
---
@@ -162,28 +162,28 @@ The following example shows the contents of the Scrubbed-wfpdiag.txt file. In th
162162

163163
```
164164
...
165-
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|52.161.24.36|Deleted ICookie from the high priority thread pool list
166-
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|52.161.24.36|IKE diagnostic event:
167-
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|52.161.24.36|Event Header:
168-
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|52.161.24.36| Timestamp: 1601-01-01T00:00:00.000Z
169-
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|52.161.24.36| Flags: 0x00000106
170-
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|52.161.24.36| Local address field set
171-
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|52.161.24.36| Remote address field set
172-
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|52.161.24.36| IP version field set
173-
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|52.161.24.36| IP version: IPv4
174-
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|52.161.24.36| IP protocol: 0
175-
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|52.161.24.36| Local address: 13.78.238.92
176-
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|52.161.24.36| Remote address: 52.161.24.36
177-
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|52.161.24.36| Local Port: 0
178-
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|52.161.24.36| Remote Port: 0
179-
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|52.161.24.36| Application ID:
180-
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|52.161.24.36| User SID: <invalid>
181-
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|52.161.24.36|Failure type: IKE/Authip Main Mode Failure
182-
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|52.161.24.36|Type specific info:
183-
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|52.161.24.36| Failure error code:0x000035e9
184-
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|52.161.24.36| IKE authentication credentials are unacceptable
185-
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|52.161.24.36|
186-
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|52.161.24.36| Failure point: Remote
165+
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|203.0.113.36| Deleted ICookie from the high priority thread pool list
166+
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|203.0.113.36| IKE diagnostic event:
167+
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|203.0.113.36| Event Header:
168+
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|203.0.113.36| Timestamp: 1601-01-01T00:00:00.000Z
169+
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|203.0.113.36| Flags: 0x00000106
170+
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|203.0.113.36| Local address field set
171+
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|203.0.113.36| Remote address field set
172+
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|203.0.113.36| IP version field set
173+
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|203.0.113.36| IP version: IPv4
174+
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|203.0.113.36| IP protocol: 0
175+
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|203.0.113.36| Local address: 203.0.113.92
176+
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|203.0.113.36| Remote address: 203.0.113.36
177+
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|203.0.113.36| Local Port: 0
178+
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|203.0.113.36| Remote Port: 0
179+
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|203.0.113.36| Application ID:
180+
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|203.0.113.36| User SID: <invalid>
181+
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|203.0.113.36| Failure type: IKE/Authip Main Mode Failure
182+
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|203.0.113.36| Type specific info:
183+
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|203.0.113.36| Failure error code:0x000035e9
184+
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|203.0.113.36| IKE authentication credentials are unacceptable
185+
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|203.0.113.36|
186+
[0]0368.03A4::02/02/2017-17:36:01.496 [ikeext] 3038|203.0.113.36| Failure point: Remote
187187
...
188188
```
189189

articles/sap/monitor/about-azure-monitor-sap-solutions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.service: sap-on-azure
66
ms.subservice: sap-monitor
77
ms.topic: overview
88
ms.custom: subject-monitoring
9-
ms.date: 10/27/2022
9+
ms.date: 08/21/2024
1010
ms.author: jushiman
1111
#Customer intent: As a developer, I want to learn how to monitor my SAP resources on Azure so that I can better understand their availability, performance, and operation.
1212
---

articles/sap/monitor/data-reference.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.author: jushiman
77
ms.service: sap-on-azure
88
ms.subservice: sap-monitor
99
ms.custom: subject-monitoring
10-
ms.date: 10/27/2022
10+
ms.date: 08/21/2024
1111
---
1212

1313
# Data reference for Azure Monitor for SAP solutions
@@ -20,7 +20,7 @@ Azure Monitor for SAP solutions doesn't support metrics.
2020

2121
## Azure Monitor logs tables
2222

23-
This section refers to all of the Azure Monitor Logs Kusto tables relevant to Azure Monitor for SAP solutions and available for query by Log Analytics. Azure Monitor for SAP solutions uses custom logs. The schemas for some tables are defined by third-party providers, such as SAP. Here are the current custom logs for Azure Monitor for SAP solutions with links to sources for more information.
23+
This section refers to all of the Azure Monitor Logs Kusto tables relevant to Azure Monitor for SAP solutions and available for query by Log Analytics. Azure Monitor for SAP solutions uses custom logs. The schemas for some tables are defined by non-Microsoft providers, such as SAP. Here are the current custom logs for Azure Monitor for SAP solutions with links to sources for more information.
2424

2525
### SapHana_HostConfig_CL
2626

articles/sap/monitor/enable-sap-insights.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: akarshprabhu
55
ms.service: sap-on-azure
66
ms.subservice: sap-monitor
77
ms.topic: how-to
8-
ms.date: 05/10/2023
8+
ms.date: 08/21/2024
99
ms.author: akak
1010
#Customer intent: I am an SAP BASIS or cloud infrastructure team member, I want to enable SAP Insights on my Azure monitor for SAP Instance.
1111
---
@@ -14,7 +14,7 @@ ms.author: akak
1414

1515
[!INCLUDE [Azure Monitor for SAP solutions public preview notice](./includes/preview-sap-insights.md)]
1616

17-
The Insights capability in Azure Monitor for SAP Solutions helps you troubleshoot Availability and Performance issues on your SAP workloads. It helps you correlate key SAP components issues with SAP logs, Azure platform metrics and health events.
17+
The Insights capability in Azure Monitor for SAP Solutions helps you troubleshoot Availability and Performance issues on your SAP workloads. It helps you correlate key SAP components issues with SAP logs, Azure platform metrics, and health events.
1818
In this how-to-guide, learn to enable Insights in Azure Monitor for SAP solutions. You can use SAP Insights with only the latest version of the service, *Azure Monitor for SAP solutions* and not *Azure Monitor for SAP solutions (classic)*
1919

2020
> [!NOTE]
@@ -65,7 +65,7 @@ cd <script_path>
6565
```PowerShell
6666
$armId = "<AMS ARM ID>"
6767
```
68-
7. If the VMs belong to a different subscription than AMS, set the list of subscriptions in which VMs of the SAP system are present (use subscription IDs):
68+
7. If the virtual machines (VMs) belong to a different subscription than AMS, set the list of subscriptions in which VMs of the SAP system are present (use subscription IDs):
6969
```PowerShell
7070
$subscriptions = "<Subscription ID 1>","<Subscription ID 2>"
7171
```
@@ -98,7 +98,7 @@ This capability helps you get an overview regarding availability of your SAP sys
9898
#### Steps to use availability insights
9999
1. Open the AMS instance of your choice and visit the insights tab under Monitoring on the left navigation pane.
100100
:::image type="content" source="./media/enable-sap-insights/visit-insights-tab.png" alt-text="Screenshot that shows the landing page of Insights on AMS.":::
101-
1. If you completed all [the steps mentioned](#steps-to-enable-insights-in-azure-monitor-for-sap-solutions), you should see the above screen asking for context to be set up. You can set the Time range, SID and the provider (optional, All selected by default).
101+
1. If you completed all [the steps mentioned](#steps-to-enable-insights-in-azure-monitor-for-sap-solutions), you should see the screen shown in step 1 asking for context to be set up. You can set the Time range, SID, and the provider (optional, All selected by default).
102102
1. On the top, you're able to see all the fired alerts related to SAP system and instance availability on this screen.
103103
:::image type="content" source="./media/enable-sap-insights/availability-overview.png" alt-text="Screenshot of the overview page of availability insights.":::
104104
1. If you're able to see SAP system availability trend, categorized by VM - SAP process list. If you selected a fired alert in the previous step, you're able to see these trends in context with the fired alert. If not, these trends respect the time range you set on the main Time range filter.
@@ -108,7 +108,7 @@ This capability helps you get an overview regarding availability of your SAP sys
108108
It has two categories of insights:
109109
* Azure platform: VM health events filtered by the time range set, either by the workbook filter or the selected alert. This pane also consists of VM availability metric trend for the chosen VM.
110110
:::image type="content" source="./media/enable-sap-insights/availability-vm-health.png" alt-text="Screenshot of the VM health events of availability insights.":::
111-
* SAP Application: Process availability and contextual insights on the process like error messages (SM21), Lock entries (SM12) and Canceled jobs (SM37) which can help you find issues that might exist in parallel in the system, at the point in time.
111+
* SAP Application: Process availability and contextual insights on the process like error messages (SM21), Lock entries (SM12), and Canceled jobs (SM37) which can help you find issues that might exist in parallel in the system, at the point in time.
112112

113113
### Performance Insights
114114
This capability helps you get an overview regarding performance of your SAP system in one place. You can also correlate key SAP performance issues with related SAP application logs alongside Azure platform utilization metrics and SAP workload configuration drifts easing the overall root-causing process.
@@ -134,7 +134,7 @@ This capability helps you get an overview regarding performance of your SAP syst
134134

135135
#### Scope of the preview
136136
We have insights only for a limited set of issues as part of the preview. We extend this capability to most of the issues supported by AMS alerts before this capability is Generally Available(GA).
137-
* Availability insights let you detect and troubleshoot unavailability of Netweaver system, instance and HANA DB.
137+
* Availability insights let you detect and troubleshoot unavailability of Netweaver system, instance, and HANA DB.
138138
* Performance insights are provided for NetWeaver metrics - High response time(ST03) and Long running batch jobs.
139139

140140
## Next steps

articles/sap/monitor/enable-tls-azure-monitor-sap-solutions.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: sameeksha91
55
ms.service: sap-on-azure
66
ms.subservice: sap-monitor
77
ms.topic: how-to
8-
ms.date: 12/14/2022
8+
ms.date: 08/21/2024
99
ms.author: sakhare
1010
#Customer intent: As an SAP Basis or cloud infrastructure team member, I want to deploy Azure Monitor for SAP solutions with secure communication.
1111
---
@@ -26,7 +26,7 @@ To enable secure communication in Azure Monitor for SAP solutions, you can choos
2626

2727
We highly recommend that you use root certificates. For root certificates, Azure Monitor for SAP solutions supports only certificates from [certificate authorities (CAs) that participate in the Microsoft Trusted Root Program](/security/trusted-root/participants-list).
2828

29-
Certificates must be signed by a trusted root authority. Self-signed certificates are not supported.
29+
Certificates must be signed by a trusted root authority. Self-signed certificates aren't supported.
3030

3131
## How does it work?
3232

0 commit comments

Comments
 (0)