|
| 1 | +--- |
| 2 | +title: Azure Communication Services End of Call Survey overview |
| 3 | +titleSuffix: An Azure Communication Services concept document |
| 4 | +description: Learn about the End of Call Survey. |
| 5 | +author: amagginetti |
| 6 | +ms.author: amagginetti |
| 7 | +manager: mvivion |
| 8 | + |
| 9 | +services: azure-communication-services |
| 10 | +ms.date: 4/03/2023 |
| 11 | +ms.topic: conceptual |
| 12 | +ms.service: azure-communication-services |
| 13 | +ms.subservice: calling |
| 14 | +--- |
| 15 | + |
| 16 | +# Contents |
| 17 | + |
| 18 | +[1 Developing [1](#developing)](#developing) |
| 19 | + |
| 20 | +[1.1 Monitoring [1](#monitoring)](#monitoring) |
| 21 | + |
| 22 | +[1.2 table 1 [1](#table-1)](#table-1) |
| 23 | + |
| 24 | +[1.3 table 2 [1](#table-2)](#table-2) |
| 25 | + |
| 26 | +[1.3.1 3 sections in [2](#sections-in)](#sections-in) |
| 27 | + |
| 28 | +[Heading no number [2](#heading-no-number)](#heading-no-number) |
| 29 | + |
| 30 | +[Heading no number 2 levels |
| 31 | +[2](#heading-no-number-2-levels)](#heading-no-number-2-levels) |
| 32 | + |
| 33 | +# Developing |
| 34 | + |
| 35 | +This article |
| 36 | + |
| 37 | +- Phone - [Public |
| 38 | + concepts](https://learn.microsoft.com/en-us/azure/communication-services/concepts/telephony/telephony-concept) |
| 39 | + |
| 40 | +## Monitoring |
| 41 | + |
| 42 | +Before you |
| 43 | + |
| 44 | +- ***“Quoted bold italic”*** |
| 45 | + |
| 46 | +Call logs will show you important insights on individual calls and your |
| 47 | +overall quality. For more details refer to the [Call |
| 48 | +Logs](https://learn.microsoft.com/en-us/azure/communication-services/concepts/analytics/call-logs-azure-monitor). |
| 49 | + |
| 50 | +- **participant<span class="mark">EndReason</span>** |
| 51 | + |
| 52 | + - You can identify trends leading to unplanned call ends. See our |
| 53 | + > guidance on [error |
| 54 | + > codes](https://learn.microsoft.com/en-us/azure/communication-services/concepts/troubleshooting-info?tabs=csharp%2Cios%2Cdotnet#calling-sdk-error-codes). |
| 55 | +
|
| 56 | +## table 1 |
| 57 | + |
| 58 | +**table** |
| 59 | + |
| 60 | +| **Call Setup Failures reason** | **Typical cause** | |
| 61 | +|--------------------------------------------------|----------------------------------| |
| 62 | +| Missing FW Deep Packet Inspection Exemption Rule | Indicates that network equipment | |
| 63 | +| Missing FW IP Block Exception Rule | Indicates that network equ | |
| 64 | + |
| 65 | +table |
| 66 | + |
| 67 | +| Type | Area | Owner name | Sign-off | |
| 68 | +|------|----------|-----------------|----------| |
| 69 | +| PM | Business | Alex Magginetti | | |
| 70 | + |
| 71 | +Code |
| 72 | + |
| 73 | +/\*\* |
| 74 | + |
| 75 | + \* Feature for ACS Live Streaming |
| 76 | + |
| 77 | + \* @beta |
| 78 | + |
| 79 | + \*/ |
| 80 | + |
| 81 | +export interface CallSurveyFeature extends CallFeature { |
| 82 | + |
| 83 | + /\*\* |
| 84 | + |
| 85 | + \* Send the end of call survey |
| 86 | + |
| 87 | + \* @param survey - survey data |
| 88 | + |
| 89 | + \*/ |
| 90 | + |
| 91 | + submitSurvey(survey?: CallSurvey): void; |
| 92 | + |
| 93 | +} |
| 94 | + |
| 95 | +Code |
| 96 | + |
| 97 | +Sample JSON Object- |
| 98 | + |
| 99 | +{ |
| 100 | + |
| 101 | +"acsResourceId": "d71d19e6-f4e1-4abe-967a-e2a474a27582", |
| 102 | + |
| 103 | +} |
| 104 | + |
| 105 | +Table black highlight on first row |
| 106 | + |
| 107 | +| JSON Field Name | Data Type | Description | |
| 108 | +|-----------------|-----------|--------------------------------------------------------------------------------| |
| 109 | +| acsResourceId | String | The ACS resource ID uniquely identifies the ACS resource used to make the call | |
| 110 | + |
| 111 | +## table 2 |
| 112 | + |
| 113 | +**table** |
| 114 | + |
| 115 | +<table> |
| 116 | +<colgroup> |
| 117 | +<col style="width: 12%" /> |
| 118 | +<col style="width: 87%" /> |
| 119 | +</colgroup> |
| 120 | +<thead> |
| 121 | +<tr class="header"> |
| 122 | +<th><strong>Remediation</strong></th> |
| 123 | +<th><strong>Guidance</strong></th> |
| 124 | +</tr> |
| 125 | +</thead> |
| 126 | +<tbody> |
| 127 | +<tr class="odd"> |
| 128 | +<td><strong>Network/internet</strong></td> |
| 129 | +<td><p><strong>Congestion</strong>: Work included <a |
| 130 | +href="https://learn.microsoft.com/en-us/microsoftteams/quality-of-experience-review-guide#quality-investigations">Quality |
| 131 | +Poor Stream summary reports</a> to<br /> |
| 132 | +<br /> |
| 133 | +<strong>QoS</strong>: If increasing bandwidth is impractical or |
| 134 | +cost-prohibitive, consider implementing QoS. This tool is very effective |
| 135 | +at managing congested traffic and can guarantee that media packets on |
| 136 | +the managed network are prioritized above non-media traffic. |
| 137 | +Alternatively, if there's no clear evidence that bandwidth is the |
| 138 | +culprit, consider these solutions:</p> |
| 139 | +<ul> |
| 140 | +<li><p><a |
| 141 | +href="https://learn.microsoft.com/en-us/microsoftteams/qos-in-teams">Microsoft |
| 142 | +Teams QoS guidance</a></p></li> |
| 143 | +</ul> |
| 144 | +<p><strong>Perform a network readiness assessment</strong>: A network |
| 145 | +assessment provides details about expected bandwidth usage, how to cope |
| 146 | +with bandwidth and network changes, and recommended networking practices |
| 147 | +for Teams and Skype for Business. Using the preceding table as your |
| 148 | +source, you have a list of buildings or subnets that are excellent |
| 149 | +candidates for an assessment.</p> |
| 150 | +<ul> |
| 151 | +<li><p><a |
| 152 | +href="https://learn.microsoft.com/en-us/microsoftteams/prepare-network">Prepare |
| 153 | +your organization's network for Teams</a></p></li> |
| 154 | +</ul></td> |
| 155 | +</tr> |
| 156 | +</tbody> |
| 157 | +</table> |
| 158 | + |
| 159 | +### 3 sections in |
| 160 | + |
| 161 | +text |
| 162 | + |
| 163 | +#### 4 sections in |
| 164 | + |
| 165 | +text |
| 166 | + |
| 167 | +##### 5 sections in |
| 168 | + |
| 169 | +# Heading no number |
| 170 | + |
| 171 | +text |
| 172 | + |
| 173 | +## Heading no number 2 levels |
| 174 | + |
| 175 | +Text |
| 176 | + |
| 177 | +table |
| 178 | + |
| 179 | +| **Metric average** | **Description** | **User experience** | |
| 180 | +|--------------------|---------------------|---------------------| |
| 181 | +| Jitter \> | This is the average | The packe | |
| 182 | + |
| 183 | +Picture 1 and 2 |
| 184 | + |
| 185 | +<img src="media/image1.png" style="width:6.5in;height:1.12986in" |
| 186 | +alt="picture 1" /><img src="media/image2.png" style="width:6.5in;height:0.64236in" |
| 187 | +alt="picture 2" /> |
| 188 | + |
| 189 | +Picture 3 |
| 190 | + |
| 191 | +<img src="media/image3.png" style="width:5.35673in;height:2.91472in" |
| 192 | +alt="picture 3" /> |
| 193 | + |
| 194 | +Video – link to embedded Microsoft video: |
| 195 | +<https://www.microsoft.com/en-us/videoplayer/embed/RWGTqQ> |
| 196 | + |
| 197 | +Video – “Insert \> online videos” in word. Same vide as above |
| 198 | + |
| 199 | +Won’t work since not supported – needs to manually be added later. |
| 200 | + |
| 201 | +Video – link to youtube: |
| 202 | + |
| 203 | +[Join your calling app to a Microsoft Teams meeting with Azure |
| 204 | +Communication Services - |
| 205 | +YouTube](https://www.youtube.com/embed/FF1LS516Bjw) |
| 206 | + |
| 207 | +Video – “Insert \> online videos” in word. Same vide as above |
| 208 | + |
| 209 | +<img src="media/image4.jpg" style="width:5in;height:3.75in" |
| 210 | +alt="Video 1: Join your calling app to a Microsoft Teams meeting with Azure Communication Services" /> |
| 211 | + |
| 212 | +<table> |
| 213 | +<colgroup> |
| 214 | +<col style="width: 64%" /> |
| 215 | +<col style="width: 35%" /> |
| 216 | +</colgroup> |
| 217 | +<thead> |
| 218 | +<tr class="header"> |
| 219 | +<th><strong>API Rating Categories</strong></th> |
| 220 | +<th><strong>Question Goal</strong></th> |
| 221 | +</tr> |
| 222 | +</thead> |
| 223 | +<tbody> |
| 224 | +<tr class="odd"> |
| 225 | +<td><ol type="1"> |
| 226 | +<li><p>Overall Call</p></li> |
| 227 | +</ol></td> |
| 228 | +<td>Responses indicate how a call participant perceived their |
| 229 | +<strong>overall</strong> call quality.</td> |
| 230 | +</tr> |
| 231 | +</tbody> |
| 232 | +</table> |
| 233 | + |
| 234 | +| **API Rating Categories** | **Cutoff Value\*** | **Input Range** | **Comments** | |
| 235 | +|---------------------------|--------------------|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| |
| 236 | +| Overall Call | 2 | 1 - 5 | Survey’s a calling participant’s overall quality experience on a scale of 1-5 where 1 indicates an imperfect call experience and 5 indicates a perfect call. The cutoff value of 2 means that a customer response of 1 or 2 indicates a less than perfect call experience. | |
| 237 | + |
| 238 | +| **Rating Categories** | **Optional Tags** | |
| 239 | +|-----------------------|-----------------------------------------------------------------------------------------------------| |
| 240 | +| Overall Call | 'CallCannotJoin' \| 'CallCannotInvite' \| 'HadToRejoin' \| 'CallEndedUnexpectedly' \| 'OtherIssues' | |
0 commit comments